<?xml version="1.0" encoding="iso-8859-1" ?>
<!--<!DOCTYPE rfc SYSTEM "rfc4748.dtd"> -->
    <!DOCTYPE rfc SYSTEM 'rfc2629.dtd' [ 
    <!ENTITY rfc2629 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2629.xml'> 
	<!ENTITY rfc2119 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml'> 
    <!ENTITY rfc8174 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8174.xml'> 
	<!ENTITY rfc8407 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8407.xml'>
	<!ENTITY rfc6991 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.6991.xml'>
	<!ENTITY rfc8343 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8343.xml'>
	<!ENTITY rfc7277 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.7277.xml'>
	<!ENTITY rfc8022 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8022.xml'>
	<!ENTITY rfc8177 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8177.xml'>
    <!ENTITY rfc6241 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.6241.xml'>
    <!ENTITY rfc8040 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8040.xml'>
    <!ENTITY rfc6242 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.6242.xml'>
    <!ENTITY rfc5246 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5246.xml'>
    <!ENTITY rfc6536 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.6536.xml'>
    <!ENTITY rfc6020 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.6020.xml'> 
    <!ENTITY rfc3688 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3688.xml'> 
    <!ENTITY rfc8279 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8279.xml'> 
    <!ENTITY rfc8296 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8296.xml'> 
    <!ENTITY rfc8349 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8349.xml'> 
    <!ENTITY rfc8446 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.8446.xml'> 
    <!ENTITY rfc9262 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.9262.xml'> 
    <!ENTITY I-D.ietf-bier-bier-yang PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-bier-bier-yang.xml'>
    <!ENTITY I-D.eckert-bier-rbs PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml3/reference.I-D.eckert-bier-rbs.xml'>
    <!ENTITY I-D.eckert-bier-te-frr PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml3/reference.I-D.eckert-bier-te-frr.xml'>
		]>

<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>		

<?rfc toc="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc disable-output-escaping="yes"?>

<rfc category="std"  docName="draft-ietf-bier-te-yang-08"
     ipr="trust200902">
  <!-- ***** FRONT MATTER ***** -->
  <front>
    <title abbrev="BIER TE YANG Module">A YANG data model for Tree Engineering for Bit Index Explicit Replication (BIER-TE)</title>
	
	<author fullname="Zheng(Sandy) Zhang" initials="Z" surname="Zhang">
      <organization>ZTE Corporation</organization>

      <address>
        <postal>
          <street></street>
          
          <city>Nanjing</city>
          
          <region></region>
  
          <code></code>

          <country>China</country>
        </postal>

        <email>zhang.zheng@zte.com.cn</email>
      </address>
    </author>
	
	 <author fullname="Cui(Linda) Wang" initials="C" surname="Wang">
      <organization>Individual</organization>

      <address>
        <postal>
          <street></street>
          
          <city></city>
          
          <region></region>
  
          <code></code>

          <country></country>
        </postal>

        <email>lindawangjoy@gmail.com</email>
      </address>
    </author>

    <author fullname="Ran Chen" initials="R" surname="Chen">
      <organization>ZTE Corporation</organization>

      <address>
        <postal>
          <street></street>
          
          <city>Nanjing</city>
          
          <region></region>
  
          <code></code>

          <country>China</country>
        </postal>

        <email>chen.ran@zte.com.cn</email>
      </address>
    </author>

	 <author fullname="Fangwei Hu" initials="F" surname="Hu">
      <organization>Individual</organization>

      <address>
        <postal>
          <street></street>
          
          <city>Shanghai</city>
          
          <region></region>
  
          <code></code>

          <country>China</country>
        </postal>

        <email>hufwei@gmail.com</email>
      </address>
    </author>

	 <author fullname="Mahesh Sivakumar" initials="M" surname="Sivakumar">
      <organization>Juniper networks</organization>

      <address>
        <postal>
          <street>1133 Innovation Way</street>
          
          <city>Sunnyvale, CALIFORNIA 94089   </city>
          
          <region></region>
  
          <code></code>

          <country>United States</country>
        </postal>

        <email>sivakumar.mahesh@gmail.com</email>
      </address>
    </author>
	
	 <author fullname="Huanan Chen" initials="H" surname="Chen">
      <organization>China Telecom</organization>

      <address>
        <postal>
          <street></street>
          
          <city></city>
          
          <region></region>
  
          <code></code>

          <country>China</country>
        </postal>

        <phone></phone>
        <email>chenhuanan@189.cn</email>
      </address>
    </author>

	<date year="2025"/>	
    <area>Routing</area>
    <workgroup>BIER WG</workgroup>
    <keyword>TE, BIER, YANG</keyword>
    <abstract>
     <t>This document defines a YANG data module for Tree Engineering for Bit Index Explicit Replication (BIER-TE) configuration and operation.
     </t>
    </abstract>
  </front>

  <!-- ***** MIDDLE MATTER ***** -->

  <middle>
    <section title="Introduction">
      <t><xref target="RFC9262"/> introduces an architecture for 
    BIER-TE: Tree Engineering for Bit Index Explicit Replication (BIER). This 
    document defines a YANG data module for BIER TE. 
	The content is consistent with the TE architecture draft. 
	This YANG data module also contains BIER TE FRR items. 
	For BIER TE FRR usage, please refer to <xref target="I-D.eckert-bier-te-frr"/>. 
	Therefore, this YANG data module is also applicable to <xref target="I-D.eckert-bier-rbs"/>.</t> 
	  </section>
  
    <section title="Conventions Used in This Document">
	  <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> 
   when, and only when, they appear in all capitals, as shown here.</t>
	  </section>
	 
	<section title="Design of the Data Model"> 
	 <t>The BIER TE YANG model includes BIER TE adjacency configuration and forwarding item configuration. 
	 Some features can also be used to enhance BIER TE functionality, such as ECMP and FRR. </t>

     <figure  align="center">
            <artwork align="center"><![CDATA[			
module: ietf-bier-te
  augment /rt:routing/rt:control-plane-protocols
            /rt:control-plane-protocol:
    +--rw bier-te
       +--rw te-adj
       |  +--rw adj-if* [name]
       |     +--rw name         if:interface-ref
       |     +--rw subdomain* [subdomain-id]
       |     |  +--rw subdomain-id    uint16
       |     |  +--rw si* [si]
       |     |     +--rw si        uint16
       |     |     +--rw adj-id*   uint16
       |     +--rw adj-type?    enumeration
       +--rw te-fwd
          +--rw subdomain* [subdomain-id]
             +--rw subdomain-id    uint16
             +--rw bsl* [fwd-bsl]
             |  +--rw fwd-bsl    uint16
             |  +--rw si* [si]
             |     +--rw si            uint16
             |     +--rw te-bift-id
             |     |  +--rw encap-type?   encapsulation-type
             |     |  +--rw value         rt-types:mpls-label
             |     +--rw fwd-items* [te-bp]
             |        +--rw te-bp           uint16
             |        +--rw fwd-next-hop* [next-hop]
             |        |  +--rw next-hop          inet:ip-address
             |        |  +--rw dnr-flag?         boolean
             |        |  +--rw fwd-type
             |        |  |  +--rw (fwd-type)
             |        |  |     +--:(connected)
             |        |  |     +--:(routed)
             |        |  |     +--:(local-decap)
             |        |  |     +--:(other)
             |        |  +--rw te-out-bift-id
             |        |  |  +--rw te-out-bift-id* [encap-type]
             |        |  |     +--rw encap-type    encapsulation-type
             |        |  |     +--rw value
             |        |  |             rt-types:mpls-label
             |        |  +--rw out-if-list* [fwd-intf]
             |        |     +--rw fwd-intf    if:interface-ref
             |        +--rw te-frr {bier-te-frr}?
             |           +--rw frr-index?      leafref
             |           +--rw resetbitmask
             |              +--rw bit-string* [index]
             |                 +--rw index      uint8
             |                 +--rw bitmask?   uint32
             +--rw te-frr-items {bier-te-frr}?
                +--rw btaft* [frr-index]
                   +--rw frr-index     uint16
                   +--rw frr-si        uint16
                   +--rw frr-bsl       uint16
                   +--rw addbitmask
                      +--rw bit-string* [index]
                         +--rw index      uint8
                         +--rw bitmask?   uint32

  notifications:
    +---n bier-te-notification
       +--ro bp-is-zero* [if-index]
          +--ro if-index    if:interface-ref
          +--ro adj-type?   enumeration
            ]]></artwork>
       <postamble></postamble>
      </figure>
    </section>

    <section title="BIER-TE configuration"> 
    <t>BIER-TE forwarding items are indexed by a combination of sub-domain-id, BitStringLength, and set identifier. </t>
    
    <t>An interface can be used in different subdomains, 
	so BIER TE adjacency information is managed by the BIER TE function rather than by the interface itself. </t>
    
    <t>BIER-TE key information notifications carried by IGP can also be implemented based on this module. </t>
    </section>

    <section title="Notifications"> 
    <t>If the adjacency ID of an adjacency is set to zero, the value is invalid. 
	Notification should be sent to the controller and network manager.</t>
    </section>

    <section title="RPCs"> 
    <t>TBD.</t>
    </section>

	<section title="BIER TE YANG model"> 
     <figure  align="center">
            <artwork align="center"><![CDATA[			
<CODE BEGINS> file "ietf-bier-te@2025-01-20.yang"
module ietf-bier-te {

  yang-version 1.1;

  namespace "urn:ietf:params:xml:ns:yang:ietf-bier-te";

  prefix bier-te;

  import ietf-inet-types {
    prefix "inet";
    reference 
      "RFC 6991: Common YANG Data Types";
  }
  
  import ietf-routing {
    prefix "rt";
    reference 
      "RFC 8349: A YANG Data Model for Routing Management 
                 (NMDA Version)";
  }

  import ietf-interfaces {
    prefix "if";
    reference 
      "RFC 8343: A YANG Data Model for Interface Management";
  }

  import ietf-routing-types {
    prefix "rt-types";
    reference 
      "RFC 8294: Common YANG Data Types for the Routing Area";
  }

  organization " IETF BIER (Bit Indexed Explicit Replication) 
                 Working Group";
  contact
    "WG Web:   <http://tools.ietf.org/wg/bier/>
     WG List:  <mailto:bier@ietf.org>

     Editor:   Zheng Zhang
               <mailto:zhang.zheng@zte.com.cn>
     Editor:   Cui Wang
               <mailto:lindawangjoy@gmail.com>
     Editor:   Ran Chen
               <mailto:chen.ran@zte.com.cn>
     Editor:   Fangwei Hu
               <mailto:hufwei@gmail.com>
     Editor:   Mahesh Sivakumar
               <mailto:sivakumar.mahesh@gmail.com>
     Editor:   Huanan Chen
               <mailto:chenhuanan@189.cn>
    ";

  description
    "The module defines the YANG definitions for Traffic 
     Engineering for Bit Index Explicit Replication (BIER-TE).

     Copyright (c) 2020 IETF Trust and the persons identified as
     authors of the code.  All rights reserved.

     Redistribution and use in source and binary forms, with or
     without modification, is permitted pursuant to, and subject 
     to the license terms contained in, the Simplified BSD 
     License set forth in Section 4.c of the IETF Trust's Legal 
     Provisions Relating to IETF Documents
     (https://trustee.ietf.org/license-info).

     This version of this YANG module is part of RFC XXXX
     (https://www.rfc-editor.org/info/rfcXXXX); see the RFC 
     itself for full legal notices.

     The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 
     'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 
     'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document 
     are to be interpreted as described in BCP 14 (RFC 2119) 
     (RFC 8174) when, and only when, they appear in all 
     capitals, as shown here.";

  revision 2025-01-20 {
    description
    "Initial revision.";
    reference 
      "RFC9262: Tree Engineering for Bit Index 
       Explicit Replication (BIER-TE)";
  }

  /*
  * Features
  */
  feature bier-te-frr {
    description
      "Support Fast Re-route feature in BIER TE.";
    reference
      "I-D.eckert-bier-te-frr: Protection Methods for BIER-TE";
  }

  /*
   * Identities
   */

  identity bier-te {
    base rt:control-plane-protocol;
    description 
      "Identity for the Tree Engineering for Bit Index Explicit 
       Replication (BIER-TE).";
    reference
      "RFC9262: Tree Engineering for Bit Index 
       Explicit Replication (BIER-TE)";
  }
  
  typedef encapsulation-type {
    type enumeration {
      enum MPLS {
        description 
          "The forwarding encapsulation is MPLS 
           described in RFC8296 section 2.1.";
      }
      enum Ethernet {
        description 
          "The forwarding encapsulation is Ethernet, 
           which is belonging to non-mpls part 
           described in RFC8296 section 2.2.";
      }
      enum IPv6 {
        description 
          "The forwarding encapsulation is IPv6,  
           which is belonging to non-mpls part 
           described in RFC8296 section 2.2.";
      }
    }
    description 
      "The encapsulation type of the BIER-TE packet. 
       If this type is not set, MPLS is the default type.";
  } // encapsulation-type
  
  grouping bit-string {
    description 
      "The bit string which each bit represents an adjacency.
       It is encapsulated in BIER header.";
    reference 
        "RFC9262: Tree Engineering for Bit Index 
         Explicit Replication (BIER-TE), section 3.3.
         RFC8279: Multicast Using Bit Index Explicit Replication 
         (BIER).
         RFC8296: Encapsulation for Bit Index Explicit Replication 
         (BIER) in MPLS and Non-MPLS Networks.";
         
    list bit-string {
      key "index";
      description 
        "As the definition in RFC 8279, the bit-string lengths are 
         64, 128, 256, 512, 1024, 2048, 4096 bits. The according 
         encapsulation is defined in RFC8296. BIER-TE uses the 
         similar function for bit string.";

      leaf index {
        type uint8 {
          range "2..128";
        }
        description 
          "The index of bit-mask. The minimum index value is 64 and 
           the corresponding bit string length is 64 bits. The 
           maximum index value is 128 and the corresponding 
           bit-string length is 4096 bits.";
      }
      leaf bitmask {
        type uint32;
        description "The bit-string in 4-octet units.";
      }
    }
  } // bit-string

  grouping adj-type {
    description "The collection of all possible adjacency type.";

    leaf adj-type {
      type enumeration {
        enum p2p {
          description "Describes p2p adjacency.";
        }
        enum bfer {
          description "Describes bfer adjacency.";
        }
        enum leaf-bfer {
          description 
            "Describes leaf-bfer adjacency. There is no next BFR that 
             the packet should be forwarded.";
        }
        enum lan {
          description "Describes lan adjacency.";
        }
        enum spoke {
          description "Describes spoke adjacency of hub-and-spoke.";
        }
        enum ring-clockwise {
          description "Describes clockwise adjacency in ring.";
        }
        enum ring-counterclockwise {
          description 
            "Describes counterclockwise adjacency in ring.";
        }
        enum ecmp {
          description 
            "Describes ecmp adjacency. When the type is set to ecmp, 
             the corresponding ecmp entry should be used to balance 
             the load.";
        }
        enum virtual-link {
          description 
            "Describes virtual adjacency between two indirect connect 
             nodes.";
        }
        enum other {
          description "Describes other id type of adjacency.";
        }
      }
      description "The collection of all possible adjacency type.";
    }
  } // adj-type

  grouping te-items {
    description "The BIER TE forwarding items collection.";

    list fwd-next-hop {
      key "next-hop";
      description
        "The next hop information for forwarding. 
         If ECMP function defined in section 3.2.3 is used, 
         multiple next hops may be existed. 
         If ECMP function is not enabled, 
         the next hop may be one only.";
          
      leaf next-hop {
        type inet:ip-address;
        mandatory true;
        description "Next hop address.";
      }
      leaf dnr-flag {
        type boolean;
        description
          "When the flag is set to 1, the BP of adjacency should not 
           be reset when packet copies are created. The flag makes 
           sense only when the forwarding type is 'connected'.";
      }
      container fwd-type {
        description 
          "The collection of all possible forwarding types.";
        choice fwd-type {
          mandatory true;
          case connected {
            description 
              "The forwarding type is connected. Mostly connected 
               interfaces.";
          }
          case routed {
            description 
              "The forwarding type is routed. Mostly not connected 
               interfaces.";
          }
          case local-decap {
            description 
              "Means that the packet should be decapsulated and 
               forward out of BIER domain.";
           }
          case other {
            description 
              "Means that the packet should be discarded.";
          }
          description 
            "The collection of all possible forwarding types.";
        }
      } // fwd-type
      
      container te-out-bift-id {
        description 
          "The bift-id information corresponding to a specific 
           outbound interface.";
        
        list te-out-bift-id {
          key "encap-type";
          leaf encap-type {
            type encapsulation-type;
            description
              "The encapsulation type of BIER-TE packet.";
          }
          leaf value {
            type rt-types:mpls-label;
            mandatory true;
            description 
              "The bift-id value of the forwarding item. 
               It can be a mpls label or an index for ethernet 
               or IPv6 encapsulation, which is used to represent 
               specific combination of [SD, BSL, SI]. 
               The ethernet or IPv6 index value is the same range 
               (20bits) as mpls label.
               This value MUST NOT be set to 0.";
          }
          description 
            "The bift-id value and the encapsulation type 
             for the BIER-TE packet.";
        }
      }
      
      list out-if-list {
        key "fwd-intf";
        description
          "The outbound interface information for forwarding.";
          
        leaf fwd-intf {
          type if:interface-ref;
          mandatory true;
          description 
            "The out interface of this forwarding item.";
        }
      }
    } // next-hop
  } // te-items

  /*
  * data nodes
  */
  augment "/rt:routing/rt:control-plane-protocols/"
       +"rt:control-plane-protocol" {
    description "The BIER TE information.";
    container bier-te {
      description "The BIER TE information container.";
      
      container te-adj {
        description "The BIER TE adjacency information.";
        list adj-if {
          key "name";
          description "List of BIER-TE interfaces.";
          leaf name {
            type if:interface-ref;
            description "Interface name reference.";
          }
          list subdomain {
            key "subdomain-id";
            description 
              "The sub-domain which the interface belongs to.
               One interface can belong to many subdomains.";
            
            leaf subdomain-id {
              type uint16;
              description "The sub-domain-id of this sub-domain.";
              reference 
                "RFC 8279: Multicast Using Bit Index Explicit 
                 Replication (BIER)";
            }
            list si {
              key "si";
              description "The set identifier value.";
                
              leaf si{
                type uint16;
                mandatory true;
                description 
                  "The set identifier of this forwarding item.";
              }
              leaf-list adj-id {
                type uint16;
                description "The ID of an adjacency.";
              }
            }
          }
          uses adj-type;
        }
      } // te-adj
      
      container te-fwd {
        description "The BIER TE forwarding information.";

        list subdomain {
          key "subdomain-id";
          description 
            "The sub-domain which the interface belongs to.
             One interface can belong to many subdomains.";

          leaf subdomain-id {
            type uint16;
            description "The sub-domain-id of this sub-domain.";
            reference 
              "RFC 8279: Multicast Using Bit Index Explicit 
               Replication (BIER)";
          }
          list bsl {
            key "fwd-bsl";
            description "The forwarding items in one BSL.";
            leaf fwd-bsl {
              type uint16;
              description "The value of bitstringlength.";
            }
              list si {
                key "si";
                description 
                  "The forwarding items in one combination of SD, 
                   BSL and SI.";
                leaf si{
                  type uint16;
                  mandatory true;
                  description 
                    "The set identifier of this forwarding item.";
                }
		            container te-bift-id {
                  description 
                    "The bift-id which is used to locate the specific 
                     forwarding item.";
                  leaf encap-type {
                    type encapsulation-type;
                    description 
                      "The encapsulation type for BIER-TE packet.";
                  }
                  
                  leaf value {
                    type rt-types:mpls-label;
                    mandatory true;
                    description 
                      "The bift-id value of the forwarding item. 
                       It can be a mpls label or an index for 
                       ethernet or IPv6 encapsulation, 
                       which is used to represent specific 
                       combination of [SD, BSL, SI]. 
                       The ethernet or IPv6 index value is the same 
                       range (20bits) as mpls label.";
                  }
                }

                list fwd-items {
                  key "te-bp";
                  description 
                    "The forwarding information of one BIER TE 
                    item.";
                  leaf te-bp {
                    type uint16;
                    mandatory true;
                    description 
                      "The bit index of a BIER TE forwarding item.";
                  }
                  uses te-items;
                
                  container te-frr {
                    if-feature bier-te-frr;
                    leaf frr-index {
                      type leafref {
                        path "../../../../../" + 
                             "te-frr-items/btaft/frr-index";
                      }
                      description "The index of this frr path.";
                    }
                    container resetbitmask {
                      description 
                        "The deleting bitmask of the forwarding 
                         item.";
                      uses bit-string;
                    }
                    description 
                      "If this link is protected, frr items can be 
                       used to forward flows when this link is 
                       down.";
                  } // te-frr
                } // fwd-items
              } // si
          } // bsl
          
          container te-frr-items {
            if-feature bier-te-frr;
            description "The TE fast re-route information.";
              list btaft {
              key "frr-index";
              description 
                "The index of the frr paths. This item can be used 
                 for multiple links protection in different SI.";
              leaf frr-index {
                type uint16;
                mandatory true;
                description "The frr item index.";
              }
              leaf frr-si{
                type uint16;
                mandatory true;
                description 
                  "The set identifier of this forwarding item.";
              }
              leaf frr-bsl {
                type uint16;
                mandatory true;
                description "The value of bitstringlength.";
              }
              container addbitmask {
                description 
                  "The adding bitmask of the forwarding item. 
                   This item should be merged into the packet's 
                   bit-string.";                 
                uses bit-string;
              }
            } // btaft
          } // te-frr-items
        } // subdomain
      } // te-fwd
    } // bier-te
  }

  /*
  * Notifications
  */
  notification bier-te-notification {
      description
        "The notification is sent when a condition changes.";
      list bp-is-zero {
          key "if-index";
          description "The adjacency id is zero. It is invalid.";
          leaf if-index {
              type if:interface-ref;
              description "The adjacency id is zero.";
          }
          uses adj-type;
      }
  }
}
<CODE ENDS>
            ]]></artwork>
       <postamble></postamble>
      </figure>
    </section>

  <section title="Security Considerations"> 
	<t>The YANG module specified in this document defines a schema for data
   that is designed to be accessed via network management protocols such
   as NETCONF <xref target="RFC6241"/> or RESTCONF <xref target="RFC8040"/>. 
   The lowest NETCONF layer is the secure transport layer, and the 
   mandatory-to-implement secure transport is Secure Shell (SSH) <xref target="RFC6242"/>. 
   The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure 
   transport is TLS <xref target="RFC8446"/>.</t>
	</section>
  
  <section title="IANA Considerations"> 
	<t> The IANA is requested to assign two new URIs from the IETF XML
   registry (<xref target="RFC3688"/>).  Authors are suggesting the following URI:</t>

       <t>URI: urn:ietf:params:xml:ns:yang:ietf-bier-te</t>
       <t>Registrant Contact: BIER WG</t>
       <t>XML: N/A, the requested URI is an XML namespace</t>

   <t>This document also requests one new YANG module name in the YANG
   Module Names registry (<xref target="RFC6020"/>) with the following suggestion:</t>

       <t>name: ietf-bier-te</t>
       <t>namespace: urn:ietf:params:xml:ns:yang:ietf-bier-te</t>
       <t>prefix: bier-te</t>
       <t>reference: RFC XXXX</t>
   </section>
	
	<section title="Acknowledgement"> 
	<t>The authors would like to thank Min Gu (gumin20181129@163.com) 
   for her testing, verification and valuable suggestion. 
   And the authors would like to thank Benjamin R and Benchong Xu for their valuable comments.</t>
	</section>	
	
  </middle>

  <!--  *****BACK MATTER ***** -->

  <back>
  
    <references title='Normative References'>
    &rfc8279;
    &rfc8296;
    &rfc2119;
    &rfc8174;
    &rfc6020;
    &rfc6241;
    &rfc6242;
    &rfc8040;
    &rfc8407;
    &rfc8343;
    &rfc8349;
    &rfc8446;
    &rfc9262;
    </references>
    
    <references title="Informative References">
    &rfc3688;
    &I-D.ietf-bier-bier-yang;
    &I-D.eckert-bier-te-frr;
    &I-D.eckert-bier-rbs;
    </references>

	</back>
</rfc>
