<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="std" docName="draft-ietf-detnet-topology-yang-00"
     ipr="trust200902">
  <front>
    <title abbrev="DetNet Model">Deterministic Networking (DetNet) Topology
    YANG Model</title>

    <author fullname="Xuesong Geng" initials="X." surname="Geng">
      <organization>Huawei Technologies</organization>

      <address>
        <postal>
          <street/>

          <city/>

          <code/>

          <country/>
        </postal>

        <email>gengxuesong@huawei.com</email>
      </address>
    </author>

    <author fullname="Mach(Guoyi) Chen" initials="M." surname="Chen">
      <organization>Huawei Technologies</organization>

      <address>
        <postal>
          <street/>

          <city/>

          <code/>

          <country/>
        </postal>

        <email>mach.chen@huawei.com</email>
      </address>
    </author>

    <author fullname="Zhenqiang Li" initials="Z." surname="Li">
      <organization>China Mobile</organization>

      <address>
        <postal>
          <street/>

          <city/>

          <code/>

          <country/>
        </postal>

        <email>lizhenqiang@chinamobile.com</email>
      </address>
    </author>

    <author fullname="Reshad Rahman" initials="R." surname="Rahman">
      <organization>Cisco Systems</organization>

      <address>
        <postal>
          <street/>

          <city/>

          <region/>

          <code/>

          <country/>
        </postal>

        <phone/>

        <facsimile/>

        <email>rrahman@cisco.com</email>

        <uri/>
      </address>
    </author>

    <date day="14" month="January" year="2019"/>

    <abstract>
      <t>This document defines a YANG data model for Deterministic Networking
      (DetNet) topology discovery and capability configuration.</t>

      <t>The YANG module defined in this document conforms to the Network
      Management Datastore Architecture (NMDA).</t>
    </abstract>

    <note title="Requirements Language">
      <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
      "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
      document are to be interpreted as described in <xref
      target="RFC2119">RFC 2119</xref>.</t>
    </note>
  </front>

  <middle>
    <section title="Introduction">
      <t>Deterministic Networking (DetNet) <xref
      target="I-D.ietf-detnet-architecture"/> is defined to provide
      high-quality network service with extremely low packet loss rate,
      bounded low latency and jitter.</t>

      <t>DetNet YANG <xref target="RFC7950"/> <xref target="RFC6991"/> models
      are used for DetNet service configuration, QoS configuration and
      topology discovery. DetNet service and QoS configuration models are
      defined in <xref target="I-D.ietf-detnet-yang"/>. This document defines
      DetNet topology model that can be used for DetNet topology/capability
      discovery and device configuration. DetNet topology model is an
      augmentation of the ietf-te-toplogy model <xref
      target="I-D.ietf-teas-yang-te-topo"/>.</t>
    </section>

    <section title="Terminologies">
      <t>This document uses the terminologies defined in <xref
      target="I-D.ietf-detnet-architecture"> </xref>.</t>
    </section>

    <section title="DetNet Topology Model">
      <t>A DetNet topology is composed of a set of DetNet nodes and DetNet
      links. DetNet nodes represent the network devices that can transport
      DetNet services, which are connected by DetNet links. A DetNet Link
      Terminate Point(LTP) is the connection point between a DetNet node and a
      DetNet link, which represents the port or interface of a DetNet node.
      The concept of DetNet node/link/LTP are similar as TE node/link/LTP
      which are defined in <xref target="I-D.ietf-teas-yang-te-topo"/>.</t>

      <t>Figure 1 shows a simple DetNet topology: A is a DetNet node, B is
      DetNet a LTP, and C is a DetNet link.</t>

      <t><figure>
          <artwork><![CDATA[                        +---+           +---+
                        | A |o(B)--(C)--|   |
                        +---+           +---+

                Figure 1. An example of DetNet Topology]]></artwork>
        </figure> DetNet topology model (ietf-detnet-topology) augments
      ietf-te-topology model <xref target="I-D.ietf-teas-yang-te-topo"/> to
      cover the following groups of attributes, which are necessary for
      supporting DetNet congestion protection and service protection:</t>

      <t><list style="symbols">
          <t>Bandwidth related attributes (e.g., bandwidth reserved for
          DetNet);</t>

          <t>Buffer/queue management related attributes (e.g., queue
          management parameters, etc.);</t>

          <t>PREOF (Packet Replication, Elimination and Ordering Function)
          capabilities and parameters (e.g., maximum out-of-order packets,
          etc.);</t>

          <t>Delay related attributes (e.g., node processing delay, queuing
          delay, link delay, etc.);</t>
        </list>The above attributes are categorized into three types: node
      attributes, link attributes and LTP attributes. The detailed
      descriptions and model definitions are specified in section 3.1, 3.2 and
      3.3, respectively.</t>

      <section title="DetNet Node Attributes">
        <t>Section 4.3 of <xref target="I-D.finn-detnet-bounded-latency"/>
        gives a DetNet time model, which defines that the delay within a node
        includes five parts: processing delay, regulation delay, queuing
        delay, output delay and preemption delay. The processing delay,
        queuing delay and regulation delay are variable in general, but for
        DetNet, these delays should be bounded, which is the basic assumption
        of deterministic networking. These bounded delay parameters are
        necessary to perform DetNet path computation. Among this delay
        attributes, processing delay and regulation delay are node relevant,
        and the queuing delay is LTP relevant. In addition, in order to
        simplify the model and implementation, the processing delay and
        regulation delay are combined as processing delay, and the preemption
        delay is included in queuing delay. [Editor notes: more comments and
        inputs need here].</t>

        <t>For the DetNet node attributes, the following variables are
        introduced:</t>

        <t><list style="symbols">
            <t hangText="">Maximum DetNet packet processing delay</t>

            <t hangText="">Minimum DetNet packet processing delay</t>

            <t hangText="">Maximum DetNet packet processing delay
            variation</t>
          </list>The modeling structure is shown below:</t>

        <figure>
          <artwork><![CDATA[augment /nw:networks/nw:network/nw:node/tet:te/tet:te-node-attributes:
   +--rw detnet-node-attributes
      +--rw minimum-packet-processing-delay?             uint32
      +--rw maximum-packet-processing-delay?             uint32
      +--rw maximum-packet-processing-delay-variation?   uint32]]></artwork>
        </figure>
      </section>

      <section title="DetNet Link Attributes">
        <t>DetNet link attributes include link delay and link bandwidth for
        DetNet. This document introduces the following link related
        attributes:</t>

        <t><list style="symbols">
            <t>Link delay: link delay is a constant that only depends on the
            physical connection. It has been defined in ietf-te-topology <xref
            target="I-D.ietf-teas-yang-te-topo"/>, and DetNet can reuse it
            directly.</t>

            <t>Maximum DetNet reservable bandwidth: the maximum reservable
            bandwidth that is allocated to DetNet. For a 10G link, if 50% of
            the bandwidth is allocated to DetNet, then the maximum DetNet
            reservable bandwidth is 5G. That means there are 5G bandwidth that
            can be used by DetNet flows.</t>

            <t>Reserved DetNet bandwidth: the bandwidth that has been reserved
            for DetNet flows.</t>

            <t>Available DetNet bandwidth: the bandwidth that is available for
            new DetNet flows.</t>
          </list>The DetNet link attributes are modeled within a link, and the
        YANG module structure is shown below:</t>

        <figure>
          <artwork><![CDATA[augment /nw:networks/nw:network/nt:link/tet:te/tet:te-link-attributes:
   +--rw detnet-link-attributes
      +--rw maximum-reservable-bandwidth
      |  +--rw te-bandwidth
      |     +--rw (technology)?
      |        +--:(generic)
      |           +--rw generic?   te-bandwidth
      +--rw reserved-detnet-bandwidth
      |  +--rw te-bandwidth
      |     +--rw (technology)?
      |        +--:(generic)
      |           +--rw generic?   te-bandwidth
      +--rw available-detnet-bandwidth
         +--rw te-bandwidth
            +--rw (technology)?
               +--:(generic)
                  +--rw generic?   te-bandwidth]]></artwork>
        </figure>
      </section>

      <section title="DetNet Link Terminate Point Attributes">
        <t>The concept of LTP is introduced in <xref
        target="I-D.ietf-teas-yang-te-topo"/>, and this section introduces
        attributes for DetNet LTP.</t>

        <t>PREOF (Packet Replication/Elimination/Ordering Function) is for
        DetNet service protection, which includes :</t>

        <t><list style="symbols">
            <t>In-order delivery function: defined in Section 3.2.2.1 of <xref
            target="I-D.ietf-detnet-architecture"/></t>

            <t>Packet replication function: defined in Section 3.2.2.2 of
            <xref target="I-D.ietf-detnet-architecture"/></t>

            <t>Packet elimination function: defined in Section 3.2.2.3 of
            <xref target="I-D.ietf-detnet-architecture"/></t>
          </list></t>

        <t>The above functions are modeled as a set of capabilities and
        relevant parameters, which are listed below:</t>

        <t><list style="symbols">
            <t>in-order-capability: indicates whether a LTP has the in-order
            delivery capability.</t>

            <t>maximum-number-of-out-of-order-packets: indicates the maximum
            number of out-of-order packets that an LTP can support, it depends
            on the reserved buffer size for packet reordering.</t>

            <t>replication-capability: indicates whether a LTP has the packet
            replication capability.</t>

            <t>elimination-capability: indicates whether a LTP has the packet
            elimination capability.</t>
          </list>In addition, DetNet LTP also includes queuing management
        algorithms and queuing delay attributes. In the context of DetNet, the
        delay of queuing is bounded, and the bound depends on what queuing
        management method is used and how many buffers are allocated. More
        information can be found in <xref
        target="I-D.finn-detnet-bounded-latency"/>. Queuing related attributes
        are listed below:</t>

        <t><list style="symbols">
            <t>queuing-algorithm-capabilities: it is modeled as a list that
            includes all queuing algorithms that a LTP supports.</t>

            <t>detnet-queues: it's modeled as a list that includes all queues
            of a DetNet LTP. For each queue, it has the following
            attributes:</t>

            <t>queue-identifier: an identifier of a queue. It could be an
            internal identifier that is only used within a node. Or it could
            be used by a centralized controller to specify in which specific
            queue a flow/packet is required to enter.</t>

            <t>queue-buffer-size: the size of a queue with unit of bytes.</t>

            <t>enabled-queuing-algorithm: indicates what queuing management
            algorithm is enabled.</t>

            <t>maximum-queuing-delay: the maximum queuing delay that a packet
            will undergo when transmitted through the queue.</t>

            <t>minimum-queuing-delay: the minimum queuing delay that a packet
            will undergo when transmitted through the queue.</t>

            <t>maximum-queuing-delay-variation: the maximum queuing delay
            variation that a packet will undergo when transmitted the
            queue.</t>
          </list>The DetNet LTP attributes are modeled within a LTP, the YANG
        module structure is shown below:</t>

        <figure>
          <artwork><![CDATA[augment /nw:networks/nw:network/nw:node/nt:termination-point/tet:te:
   +--rw detnet-terminate-point-attributes
      +--rw elimination-capability?           boolean
      +--rw replication-capability?           boolean
      +--rw in-ordering-capability
      |  +--rw in-ordering-capability?         boolean
      |  +--rw maximum-out-of-order-packets?   uint32
      +--rw queuing-algorithm-capabilities
      |  +--rw credit-based-shaping?            boolean
      |  +--rw time-aware-shaping?              boolean
      |  +--rw cyclic-queuing-and-forwarding?   boolean
      |  +--rw asynchronous-traffic-shaping?    boolean
      +--rw queues* [queue-identifier]
         +--rw queue-identifier                   uint32
         +--rw queue-buffer-size?                 uint32
         +--rw enabled-queuing-algorithm
         |  +--rw credit-based-shaping?            boolean
         |  +--rw time-aware-shaping?              boolean
         |  +--rw cyclic-queuing-and-forwarding?   boolean
         |  +--rw asynchronous-traffic-shaping?    boolean
         +--rw minimum-queuing-delay?             uint32
         +--rw maximum-queuing-delay?             uint32
         +--rw maximum-queuing-delay-variation?   uint32]]></artwork>
        </figure>
      </section>
    </section>

    <section title="DetNet Topology YANG Structure">
      <t/>

      <figure>
        <artwork><![CDATA[module: ietf-detnet-topology
augment /nw:networks/nw:network/nw:network-types/tet:te-topology:
   +--rw detnet-topology!
augment /nw:networks/nw:network/nw:node/tet:te/tet:te-node-attributes:
   +--rw detnet-node-attributes
      +--rw minimum-packet-processing-delay?             uint32
      +--rw maximum-packet-processing-delay?             uint32
      +--rw maximum-packet-processing-delay-variation?   uint32
augment /nw:networks/nw:network/nt:link/tet:te/tet:te-link-attributes:
   +--rw detnet-link-attributes
      +--rw maximum-reservable-bandwidth
      |  +--rw te-bandwidth
      |     +--rw (technology)?
      |        +--:(generic)
      |           +--rw generic?   te-bandwidth
      +--rw reserved-detnet-bandwidth
      |  +--rw te-bandwidth
      |     +--rw (technology)?
      |        +--:(generic)
      |           +--rw generic?   te-bandwidth
      +--rw available-detnet-bandwidth
         +--rw te-bandwidth
            +--rw (technology)?
               +--:(generic)
                  +--rw generic?   te-bandwidth
augment /nw:networks/nw:network/nw:node/nt:termination-point/tet:te:
   +--rw detnet-terminate-point-attributes
      +--rw elimination-capability?           boolean
      +--rw replication-capability?           boolean
      +--rw in-ordering-capability
      |  +--rw in-ordering-capability?         boolean
      |  +--rw maximum-out-of-order-packets?   uint32
      +--rw queuing-algorithm-capabilities
      |  +--rw credit-based-shaping?            boolean
      |  +--rw time-aware-shaping?              boolean
      |  +--rw cyclic-queuing-and-forwarding?   boolean
      |  +--rw asynchronous-traffic-shaping?    boolean
      +--rw queues* [queue-identifier]
         +--rw queue-identifier                   uint32
         +--rw queue-buffer-size?                 uint32
         +--rw enabled-queuing-algorithm
         |  +--rw credit-based-shaping?            boolean
         |  +--rw time-aware-shaping?              boolean
         |  +--rw cyclic-queuing-and-forwarding?   boolean
         |  +--rw asynchronous-traffic-shaping?    boolean
         +--rw minimum-queuing-delay?             uint32
         +--rw maximum-queuing-delay?             uint32
         +--rw maximum-queuing-delay-variation?   uint32
]]></artwork>
      </figure>
    </section>

    <section title="DetNet Topology YANG Model">
      <t/>

      <figure>
        <artwork><![CDATA[<CODE BEGINS> file "ietf-detnet-topology@20190114.yang"
  module ietf-detnet-topology {  
  yang-version 1.1;
  namespace "urn:ietf:params:xml:ns:yang:ietf-detnet-topology";
  prefix "detnet-topology";
   
  import ietf-te-types {
    prefix "te-types";
  }

  import ietf-te-topology {
    prefix "tet";
  }

  import ietf-network {
    prefix "nw";
  }
  
  import ietf-network-topology {
    prefix "nt";
  }

  organization 
    "IETF Deterministic Networking(DetNet)Working Group";

  contact
   "WG Web:   <http://tools.ietf.org/wg/detnet/>
    WG List:  <mailto:detnet@ietf.org>

    WG Chair: Lou Berger
              <mailto:lberger@labn.net>
      
              Janos Farkas
              <janos.farkas@ericsson.com>

    Editor:   Xuesong Geng
              <mailto:gengxuesong@huawei.com>

    Editor:   Mach Chen
              <mailto:mach.chen@huawei.com>
      
    Editor:   Zhenqiang Li
              <lizhenqiang@chinamobile.com>
      
    Editor:   Reshad Rahman
              <rrahman@cisco.com>";

  description
    "This YANG module augments the 'ietf-te-topology'
     module with DetNet related capabilities and 
     parameters.";
 
    revision "2018-09-10" {
      description "Initial revision";
      reference "RFC XXXX: draft-geng-detnet-config-yang-05";
    }


  grouping detnet-queuing-algorithms {
    description
      "Relationship with IEEE 802.1 TSN YANG models is TBD.";
  }

  grouping detnet-node-attributes{
    description 
      "DetNet node related attributes.";
    leaf minimum-packet-processing-delay{
      type uint32;
      description
        "Minimum packet processing delay
         in a node. The unit of the delay
         is microsecond(us)";
    }
    leaf maximum-packet-processing-delay{
      type uint32;
      description
        "Maximum packet processing delay
         in a node. The unit of the delay
         is microsecond(us)";
    }
    leaf maximum-packet-processing-delay-variation{
      type uint32;
      description
        "Maximum packet processing delay 
         variation in a node. The unit of
         the delay variation is microsecond(us)";
    }    
  }
  
  grouping detnet-link-attributes{
    description 
      "DetNet link related attributes.";
  
    container maximum-reservable-bandwidth{
      uses te-types:te-bandwidth; 
      description
        "This container specifies the maximum bandwidth 
         that is reserved for DetNet on this link.";
    }
    
    container reserved-detnet-bandwidth{
      uses te-types:te-bandwidth;
      description
        "This container specifies the bandwidth that has 
         been reserved for DetNet on this link.";
    }
    container available-detnet-bandwidth{
      uses te-types:te-bandwidth;
      description
        "This container specifies the bandwidth that is  
         available for new DetNet flows on this link.";
    }
  }
  
  grouping detnet-terminate-point-attributes{
    description 
      "DetNet terminate point related attributes.";
    
    leaf elimination-capability{
      type boolean;
      description 
        "Indicates whether a node is able to do packet 
         elimination.";
      reference
        "Section 3.2.2.3 of
         draft-ietf-detnet-architecture";
       
    }
    leaf replication-capability{
      type boolean;
      description 
        "Indicates whether a node is able to do packet 
         replication.";
      reference
        "Section 3.2.2.2 of
         draft-ietf-detnet-architecture";
    }
    container in-ordering-capability {
      description
        "Indicates the parameters needed for
         packet in-ordering.";
      reference
        "Section 3.2.2.1 of  
         draft-ietf-detnet-architecture";
      
      leaf in-ordering-capability {
        type boolean;
      description
        "Indicates whether a node is able to do packet 
         in-ordering.";
      }
      leaf maximum-out-of-order-packets {
      type uint32;
      description
        "The maximum number of out-of-order packets.";
      }
    }
    
    container queuing-algorithm-capabilities {
      description
        "All queuing algorithms that a LTP supports.";
      uses detnet-queuing-algorithms;
    }    
    
    list queues {
      key "queue-identifier";
      description
        "A list of DetNet queues.";     
      leaf queue-identifier {
        type uint32;
        description
          "The identifier of the queue.";
      }      
      leaf queue-buffer-size {
        type uint32;
        description
          "The size of the queue with unit of bytes.";
      }
      
      container enabled-queuing-algorithm {
        description
          "The queuing algorithms that are enabled on the queue.";
           uses detnet-queuing-algorithms;
      }
      
      leaf minimum-queuing-delay{
        type uint32;
        description
          "The minimum queuing delay of the queue.
           The unit of the delay is microsecond(us)";
      }
      leaf maximum-queuing-delay{
        type uint32;
        description
          "The maximum queuing delay of the queue.
           The unit of the delay is microsecond(us)";
      }
      leaf maximum-queuing-delay-variation{
        type uint32;
        description
          "The maximum queuing delay variation of the queue.
           The unit of the delay variation is microsecond(us)";
      }  
    }  
  }
    
   augment "/nw:networks/nw:network/nw:network-types/tet:te-topology"{
    description
      "Introduce new network type for TE topology.";
    container detnet-topology {
      presence "Indicates DetNet topology.";
      description
        "Its presence identifies the DetNet topology type";
    }
  }
  
  augment "/nw:networks/nw:network/nw:node/tet:te/"
          + "tet:te-node-attributes" {
      when "../../../nw:network-types/tet:te-topology/"
      + "detnet-topology:detnet-topology" {
        description
          "Augmentation parameters apply only for networks with
           DetNet topology type.";
      }
    description 
      "Augmentation parameters apply for DetNet node attributes.";
    container detnet-node-attributes {
      description 
        "Attributes for DetNet node.";
      uses detnet-node-attributes;     
    }
  }
  
  augment "/nw:networks/nw:network/nt:link/tet:te/"
            + "tet:te-link-attributes" {
    when "../../../nw:network-types/tet:te-topology/"
         + "detnet-topology:detnet-topology" {
      description
        "Augmentation parameters apply only for networks with
        DetNet topology type.";
    }
    description 
      "Augmentation parameters apply for DetNet link attributes.";
    container detnet-link-attributes {
      description 
        "Attributes for DetNet link.";
      uses detnet-link-attributes;
    }
  }
  
  augment "/nw:networks/nw:network/nw:node/nt:termination-point/"
             + "tet:te" {
      when "../../../nw:network-types/tet:te-topology/"
            + "detnet-topology:detnet-topology" {
        description
          "Augmentation parameters apply only for networks with
           DetNet topology type.";
      }
    description 
      "Augmentation parameters apply for DetNet
       link termination point.";
    container detnet-terminate-point-attributes {
      description 
        "Attributes for DetNet link terminate point.";
      uses detnet-terminate-point-attributes;  
    }
  }
 } //topology module


<CODE ENDS>
]]></artwork>
      </figure>
    </section>

    <section title="Open Issues">
      <t>There are some open issues that are still under discussion:</t>

      <t><list style="symbols">
          <t>The Relationship with 802.1 TSN YANG models is TBD. TSN YANG
          models include: P802.1Qcw, which defines TSN YANG for Qbv, Qbu, and
          Qci, and P802.1CBcv, which defines YANG for 802.1CB. The possible
          problem here is how to avoid possible overlap among yang models
          defined in IETF and IEEE. A common YANG model may be defined in the
          future to shared by both TSN and DetNet. More discussion are needed
          here.</t>

          <t>How to support DetNet OAM is TBD.</t>
        </list>These issues will be resolved in the following versions of the
      draft.</t>
    </section>

    <section anchor="IANA" title="IANA Considerations">
      <t>This document makes no request of IANA.</t>

      <t>Note to RFC Editor: this section may be removed on publication as an
      RFC.</t>
    </section>

    <section anchor="Security" title="Security Considerations">
      <t>&lt;TBD&gt;</t>
    </section>

    <section anchor="Acknowledgements" title="Acknowledgements">
      <t/>
    </section>
  </middle>

  <back>
    <references title="Normative References">
      <?rfc include="reference.RFC.2119"?>

      <?rfc include='reference.RFC.6991'?>

      <?rfc include='reference.RFC.7950'?>

      <?rfc include='reference.I-D.ietf-detnet-architecture'?>

      <?rfc include='reference.I-D.finn-detnet-bounded-latency'?>

      <?rfc include='reference.I-D.ietf-detnet-flow-information-model'?>

      <?rfc include='reference.I-D.ietf-detnet-dp-sol-ip'?>

      <?rfc include='reference.I-D.ietf-detnet-dp-sol-mpls'?>
    </references>

    <references title="Informative References">
      <?rfc include='reference.I-D.geng-detnet-info-distribution'?>

      <?rfc include='reference.I-D.ietf-teas-yang-te'?>

      <?rfc include='reference.I-D.ietf-teas-yang-te-topo'?>

      <?rfc include='reference.I-D.varga-detnet-service-model'?>

      <?rfc include='reference.I-D.ietf-detnet-use-cases'?>

      <?rfc include='reference.I-D.thubert-tsvwg-detnet-transport'?>

      <?rfc include='reference.RFC.3209'?>

      <?rfc include='reference.RFC.4875'?>

      <?rfc include='reference.RFC.8342'?>

      <?rfc include='reference.I-D.ietf-detnet-yang'?>

      <reference anchor="IEEE802.1Qcc">
        <front>
          <title>IEEE, "Stream Reservation Protocol (SRP) Enhancements and
          Performance Improvements (IEEE Draft P802.1Qcc)", 2017,
          &lt;http://www.ieee802.org/1/files/private/cc-drafts/&gt;.</title>

          <author fullname="IEEE" surname="">
            <organization/>
          </author>

          <date year=""/>
        </front>
      </reference>

      <reference anchor="IEEE802.1Qbv">
        <front>
          <title>IEEE, "IEEE Std 802.1Qbu Bridges and Bridged Networks -
          Amendment 25: Enhancements for Scheduled Traffic", 2015,
          &lt;http://ieeexplore.ieee.org/document/7572858/&gt;.</title>

          <author fullname="" surname="">
            <organization/>
          </author>

          <date year="2016"/>
        </front>
      </reference>

      <reference anchor="IEEE802.1Q-2014">
        <front>
          <title>IEEE, "IEEE Std 802.1Q Bridges and Bridged Networks", 2014,
          &lt;http://ieeexplore.ieee.org/document/6991462/&gt;.</title>

          <author fullname="">
            <organization/>
          </author>

          <date year="2014"/>
        </front>
      </reference>

      <reference anchor="IEEE802.1Qch">
        <front>
          <title>IEEE, "Cyclic Queuing and Forwarding (IEEE Draft P802.1Qch)",
          2017,
          &lt;http://www.ieee802.org/1/files/private/ch-drafts/&gt;.</title>

          <author fullname="IEEE" surname="">
            <organization/>
          </author>

          <date year="2016"/>
        </front>
      </reference>

      <reference anchor="IEEE802.1Qci">
        <front>
          <title>IEEE, "Per-Stream Filtering and Policing (IEEE Draft
          P802.1Qci)", 2016,
          &lt;http://www.ieee802.org/1/files/private/ci-drafts/&gt;.</title>

          <author fullname="IEEE" surname="">
            <organization/>
          </author>

          <date year="2016"/>
        </front>
      </reference>

      <reference anchor="IEEE802.1Qbu">
        <front>
          <title>IEEE, "IEEE Std 802.1Qbu Bridges and Bridged Networks -
          Amendment 26: Frame Preemption", 2016,
          &lt;http://ieeexplore.ieee.org/document/7553415/&gt;.</title>

          <author fullname="IEEE" surname="">
            <organization/>
          </author>

          <date year="2016"/>
        </front>
      </reference>

      <reference anchor="IEEE802.1CB">
        <front>
          <title>IEEE, "Frame Replication and Elimination for Reliability
          (IEEE Draft P802.1CB)", 2017,
          &lt;http://www.ieee802.org/1/files/private/cb-drafts/&gt;.</title>

          <author fullname="IEEE" surname="">
            <organization/>
          </author>

          <date year="2016"/>
        </front>
      </reference>
    </references>
  </back>
</rfc>
