< draft-zhang-bier-te-yang-05.txt   draft-zhang-bier-te-yang-06.txt >
BIER WG Zheng. Zhang BIER WG Zheng. Zhang
Internet-Draft Cui. Wang Internet-Draft Cui. Wang
Intended status: Standards Track Ran. Chen Intended status: Standards Track Ran. Chen
Expires: June 2, 2019 Fangwei. Hu Expires: September 12, 2019 Fangwei. Hu
ZTE Corporation ZTE Corporation
Mahesh. Sivakumar Mahesh. Sivakumar
Cisco Systems, Inc. Cisco Systems, Inc.
Huanan. Chen Huanan. Chen
China Telecom China Telecom
November 29, 2018 March 11, 2019
BIER TE YANG module BIER TE YANG model
draft-zhang-bier-te-yang-05 draft-zhang-bier-te-yang-06
Abstract Abstract
This document defines a YANG data model for BIER TE configuration and This document defines a YANG data model for BIER TE configuration and
operation. operation.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 2, 2019. This Internet-Draft will expire on September 12, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Design of the Data Model . . . . . . . . . . . . . . . . . . 2 2. Design of the Data Model . . . . . . . . . . . . . . . . . . 2
3. BIER-TE configuration . . . . . . . . . . . . . . . . . . . . 4 3. BIER-TE configuration . . . . . . . . . . . . . . . . . . . . 3
4. Notifications . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Notifications . . . . . . . . . . . . . . . . . . . . . . . . 4
5. RPCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. RPCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
6. BIER TE YANG module . . . . . . . . . . . . . . . . . . . . . 4 6. BIER TE YANG model . . . . . . . . . . . . . . . . . . . . . 4
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
8. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 12 8. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 14
9. Normative References . . . . . . . . . . . . . . . . . . . . 12 9. Normative References . . . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
[I-D.ietf-bier-te-arch] introduces an architecture for BIER-TE: [I-D.ietf-bier-te-arch] introduces an architecture for BIER-TE:
Traffic Engineering for Bit Index Explicit Replication (BIER). This Traffic Engineering for Bit Index Explicit Replication (BIER). This
document defines a YANG data model for BIER TE. The content is in document defines a YANG data model for BIER TE. The content is in
keeping with the TE architecture draft. In addition, this YANG data keeping with the TE architecture draft. In addition, this YANG data
model contains BIER TE frr items of [I-D.eckert-bier-te-frr]. model contains BIER TE frr items of [I-D.eckert-bier-te-frr].
2. Design of the Data Model 2. Design of the Data Model
Because BIER-TE technology can be used independently, the common The BIER TE YANG model includes BIER TE adjancency configuration and
elements reference from BIER YANG ( [I-D.ietf-bier-bier-yang] ) is forwarding items configuration. Some features can also be used to
not suitable, such as subdomain-id, bitstringlength, set identifier, enhance BIER TE function, like ECMP and FRR.
and so on. These common elements should be defined in general BIER
YANG model or in each YANG model respectively. The BIER TE YANG
model includes BIER TE forwarding items configuration. Some features
can also be used to enhance BIER TE function, like ECMP and FRR.
module: ietf-bier-te module: ietf-bier-te
augment /rt:routing: augment /rt:routing:
+--rw bier-te +--rw bier-te
+--rw subdomain* [subdomain-id] +--rw subdomain* [subdomain-id]
+--rw subdomain-id uint16 +--rw subdomain-id uint16
+--rw te-adj-id
| +--rw si* [si]
| +--rw si uint16
| +--rw adj* [adj-id]
| +--rw adj-id uint16
| +--rw adj-if if:interface-ref
| +--rw bp-type? enumeration
+--rw te-bift-id
| +--rw type? enumeration
| +--rw value rt-types:mpls-label
+--rw bsl* [fwd-bsl] +--rw bsl* [fwd-bsl]
| +--rw fwd-bsl uint16 | +--rw fwd-bsl uint16
| +--rw si* [si] | +--rw si* [si]
| +--rw si uint16 | +--rw si uint16
| +--rw te-bift-id | +--rw te-bift-id
| | +--rw type? enumeration | | +--rw type? enumeration
| | +--rw value rt-types:mpls-label | | +--rw value rt-types:mpls-label
| +--rw fwd-items* [te-bp] | +--rw fwd-items* [te-bp]
| +--rw te-bp uint16 | +--rw te-bp uint16
| +--rw bp-type? enumeration | +--rw bp-type? enumeration
| +--rw (fwd-type) | +--rw (fwd-type)
| | +--:(connected) | | +--:(connected)
| | +--:(routed) | | +--:(routed)
| | +--:(local-decap) | | +--:(local-decap)
| | +--:(other) | | +--:(other)
| +--rw dnr-flag? boolean
| +--rw out-info | +--rw out-info
| | +--rw fwd-intf if:interface-ref | | +--rw fwd-intf if:interface-ref
| | +--rw te-out-bift-id | | +--rw te-out-bift-id
| | +--rw type? enumeration | | +--rw type? enumeration
| | +--rw value rt-types:mpls-label | | +--rw value rt-types:mpls-label
| +--rw te-frr {bier-te-frr}? | +--rw te-frr {bier-te-frr}?
| | +--rw frr-index? uint16 | | +--rw frr-index? uint16
| | +--rw resetbitmask* [bitmask] | | +--rw resetbitmask* [bitmask]
| | +--rw bitmask bit-string | | +--rw bitmask bit-string
| +--rw te-ecmp* [out-if] {bier-te-ecmp}? | +--rw te-ecmp* [out-if] {bier-te-ecmp}?
skipping to change at page 4, line 8 skipping to change at page 3, line 49
notifications: notifications:
+---n bier-te-notification +---n bier-te-notification
+--ro bp-is-zero* [if-index] +--ro bp-is-zero* [if-index]
+--ro if-index if:interface-ref +--ro if-index if:interface-ref
+--ro bp-type? enumeration +--ro bp-type? enumeration
3. BIER-TE configuration 3. BIER-TE configuration
The BIER-TE forwarding item is indexed by the combination of sub- The BIER-TE forwarding item is indexed by the combination of sub-
domain-id, BitStringLength and set identifier. Maybe there are some domain-id, BitStringLength and set identifier.
global BIER-TE configurations, they can be added in later version.
One interface can be used in different sub-domain, so the BIER TE One interface can be used in different sub-domain, so the BIER TE
adjacency information is managed by BIER TE function other than by adjacency information is managed by BIER TE function other than by
interface itself. interface itself.
Because the BIER-TE is controlled by controller now, the information Because the BIER-TE is controlled by controller now, the information
about IGP is not defined. If in the future the IGP is used to carry about IGP is not defined. If in the future the IGP is used to carry
the information about BIER-TE, the IGP extension will be added in the information about BIER-TE, the IGP extension will be added in
this document. this document.
4. Notifications 4. Notifications
If the adjacency id of one adjacency is set to zero, the value is If the adjacency id of one adjacency is set to zero, the value is
invalid. The notification should be sent to controller and network invalid. The notification should be sent to controller and network
manager. manager.
5. RPCs 5. RPCs
TBD. TBD.
6. BIER TE YANG module 6. BIER TE YANG model
<CODE BEGINS> file "ietf-bier-te.yang" <CODE BEGINS> file "ietf-bier-te.yang"
module ietf-bier-te { module ietf-bier-te {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-bier-te"; namespace "urn:ietf:params:xml:ns:yang:ietf-bier-te";
prefix bier-te; prefix bier-te;
skipping to change at page 5, line 8 skipping to change at page 4, line 51
import ietf-interfaces { import ietf-interfaces {
prefix "if"; prefix "if";
reference "RFC7223"; reference "RFC7223";
} }
import ietf-routing-types { import ietf-routing-types {
prefix "rt-types"; prefix "rt-types";
reference "RFC8294"; reference "RFC8294";
} }
organization " IETF BIER(Bit Indexed Explicit Replication ) Working Group"; organization " IETF BIER(Bit Indexed Explicit Replication)
Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/bier/> "WG Web: <http://tools.ietf.org/wg/bier/>
WG List: <mailto:bier@ietf.org> WG List: <mailto:bier@ietf.org>
Editor: Zheng Zhang Editor: Zheng Zhang
<mailto:zhang.zheng@zte.com.cn> <mailto:zhang.zheng@zte.com.cn>
Editor: Cui Wang Editor: Cui Wang
<mailto:wang.cui1@zte.com.cn> <mailto:wang.cui1@zte.com.cn>
Editor: Ran Chen Editor: Ran Chen
<mailto:chen.ran@zte.com.cn> <mailto:chen.ran@zte.com.cn>
skipping to change at page 5, line 40 skipping to change at page 5, line 36
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC 3618; see This version of this YANG module is part of RFC 3618; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
revision 2018-11-30 { revision 2019-03-11 {
description description
"Initial revision."; "Initial revision.";
reference reference
"draft-ietf-bier-te-arch-01: Traffic Engineering for Bit Index Explicit Replication (BIER-TE)"; "draft-ietf-bier-te-arch: Traffic Engineering for Bit Index
Explicit Replication (BIER-TE)";
} }
/* /*
* Features * Features
*/ */
feature bier-te-frr { feature bier-te-frr {
description description
"Support Fast Re-route feature in BIER TE."; "Support Fast Re-route feature in BIER TE.";
} }
feature bier-te-ecmp { feature bier-te-ecmp {
skipping to change at page 6, line 20 skipping to change at page 6, line 16
typedef bit-string { typedef bit-string {
type uint16; type uint16;
description "The bit mask of one bit-string."; description "The bit mask of one bit-string.";
} }
grouping te-frr { grouping te-frr {
description "The TE fast re-route information."; description "The TE fast re-route information.";
list btaft { list btaft {
key "frr-index"; key "frr-index";
description "The index of the frr paths. This item can be used for multiple links protection in different SI."; description "The index of the frr paths. This item can be
used for multiple links protection in
different SI.";
leaf frr-index { leaf frr-index {
type uint16; type uint16;
mandatory true; mandatory true;
description "The frr item index."; description "The frr item index.";
} }
leaf frr-si{ leaf frr-si{
type uint16; type uint16;
mandatory true; mandatory true;
description "The set identifier of this forwarding item."; description "The set identifier of this forwarding
item.";
} }
leaf frr-bsl { leaf frr-bsl {
type uint16; type uint16;
mandatory true; mandatory true;
description "The value of bitstringlength."; description "The value of bitstringlength.";
} }
list addbitmask { list addbitmask {
key "bitmask"; key "bitmask";
description "The adding bitmask of the forwarding item."; description "The adding bitmask of the forwarding
item.";
leaf bitmask { leaf bitmask {
type bit-string; type bit-string;
description "The adding bitmask of the forwarding item. This item should be merged into the packet's bit-string."; description "The adding bitmask of the forwarding
item. This item should be merged
into the packet's bit-string.";
} }
} }
} }
} }
grouping fwd-type { grouping fwd-type {
description "The collection of all possible forwarding type."; description "The collection of all possible forwarding types.";
choice fwd-type { choice fwd-type {
mandatory true; mandatory true;
case connected { case connected {
description "The forwarding type is connected. Mostly connected interfaces."; description "The forwarding type is connected.
Mostly connected interfaces.";
} }
case routed { case routed {
description "The forwarding type is routed. Mostly not connected interfaces."; description "The forwarding type is routed.
Mostly not connected interfaces.";
} }
case local-decap { case local-decap {
description "Means that the packet should be decapsulated and forward out BIER domain."; description "Means that the packet should be
decapsulated and forward out
of BIER domain.";
} }
/*case ecmp {
description "There is more than one path in the forwarding items with equal cost.";
}*/
case other { case other {
description "Means that the packet should be discarded."; description "Means that the packet should be
discarded.";
} }
description "The collection of all possible forwarding type."; description "The collection of all possible forwarding
types.";
} }
} }
grouping bp-type { grouping bp-type {
description "The collection of all possible adjacency type."; description "The collection of all possible adjacency type.";
leaf bp-type { leaf bp-type {
type enumeration { type enumeration {
enum p2p { enum p2p {
description "Describes p2p adjacency."; description "Describes p2p adjacency.";
} }
enum bfer { enum bfer {
description "Describes bfer adjacency."; description "Describes bfer adjacency.";
} }
enum leaf-bfer { enum leaf-bfer {
description "Describes leaf-bfer adjacency. There is no next BFR that the packet should be forwarded."; description "Describes leaf-bfer adjacency.
There is no next BFR that the packet
should be forwarded.";
} }
enum lan { enum lan {
description "Describes lan adjacency.."; description "Describes lan adjacency.";
} }
enum spoke { enum spoke {
description "Describes spoke adjacency of hub-and-spoke."; description "Describes spoke adjacency of
hub-and-spoke.";
} }
enum ring-clockwise { enum ring-clockwise {
description "Describes clockwise adjacency in ring."; description "Describes clockwise adjacency in
ring.";
} }
enum ring-counterclockwise { enum ring-counterclockwise {
description "Describes counterclockwise adjacency in ring."; description "Describes counterclockwise adjacency in
ring.";
} }
enum ecmp { enum ecmp {
description "Describes ecmp adjacency. When the type is set to ecmp, description "Describes ecmp adjacency.
the corresponding ecmp entry should be used to balance the load."; When the type is set to ecmp,
the corresponding ecmp entry
should be used to balance the load.";
} }
enum virtual-link { enum virtual-link {
description "Describes virtual adjacency between two indirect connect nodes."; description "Describes virtual adjacency
between two indirect connect
nodes.";
} }
enum other { enum other {
description "Describes other id type of adjacency."; description "Describes other id type of
adjacency.";
} }
} }
description "The collection of all possible adjacency type."; description "The collection of all possible adjacency
type.";
} }
} }
grouping te-bift-id { grouping te-bift-id {
description "The index of BIER forwarding items. It usually represents the combination of [SD, BSL, SI]."; description "The index of BIER forwarding items. It usually
represents the combination of [SD, BSL, SI].";
leaf type { leaf type {
type enumeration { type enumeration {
enum mpls { enum mpls {
description "The bift-id value is represent the BIER TE mpls forwarding plane. It is a mpls label."; description "The bift-id value is represent the
BIER TE mpls forwarding plane. It
is a mpls label.";
} }
enum eth { enum eth {
description "The bift-id value is represent the BIER TE ethernet forwarding plane. description "The bift-id value is represent the
It is an index of ethernet encapsulation."; BIER TE ethernet forwarding plane.
It is an index of ethernet
encapsulation.";
} }
enum other { enum other {
description "Describes other type of te-bift-id."; description "Describes other type of te-bift-id.";
} }
} }
description "The types of BIER TE bift-id. If this type is not set, mpls is default type."; description "The types of BIER TE bift-id. If this type
is not set, mpls is default type.";
} }
leaf value { leaf value {
type rt-types:mpls-label; type rt-types:mpls-label;
mandatory true; mandatory true;
description "The bift-id value of the forwarding item. It can be a mpls label or an index of ethernet encapsulation description "The bift-id value of the forwarding
which is used to represent specific combination of [SD, BSL, SI]. The ethernet index value is item. It can be a mpls label or an
the same range (20bits) as mpls label."; index of ethernet encapsulation which
is used to represent specific
combination of [SD, BSL, SI]. The
ethernet index value is the same range
(20bits) as mpls label.";
} }
} }
grouping te-items { grouping te-items {
description "The BIER TE forwarding items collection."; description "The BIER TE forwarding items collection.";
uses fwd-type; uses fwd-type;
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 out-info { container out-info {
description "The information of out forwarding packets. Includes the out interface and the bift-id of next hop."; description "The information of out forwarding
packets. Includes the outbound interface
and the bift-id of next hop.";
leaf fwd-intf { leaf fwd-intf {
type if:interface-ref; type if:interface-ref;
mandatory true; mandatory true;
description "The out interface of this forwarding item."; description "The out interface of this
forwarding item.";
} }
container te-out-bift-id { container te-out-bift-id {
description "The bift-id information corresponding to a specific out interface."; description "The bift-id information
corresponding to a specific
outbound interface.";
uses te-bift-id; uses te-bift-id;
} }
} }
container te-frr { container te-frr {
if-feature bier-te-frr; if-feature bier-te-frr;
leaf frr-index { leaf frr-index {
type uint16; type uint16;
description "The index of this frr path."; description "The index of this frr path.";
} }
list resetbitmask { list resetbitmask {
key "bitmask"; key "bitmask";
description "The deleting bitmask of the forwarding item."; description "The deleting bitmask of the
forwarding item.";
leaf bitmask { leaf bitmask {
type bit-string; type bit-string;
description "The deleting bitmask of the forwarding item."; description "The deleting bitmask of the
forwarding item.";
} }
} }
description "If this link is protected, frr items can be used to forward flows when this link is down."; description "If this link is protected, frr items can
be used to forward flows when this link
is down.";
} }
} }
grouping fwd-items { grouping fwd-items {
list si { list si {
key "si"; key "si";
description "The forwarding items of one set identifier."; description "The forwarding items of one set identifier.";
leaf si{ leaf si{
type uint16; type uint16;
mandatory true; mandatory true;
description "The set identifier of this forwarding item."; description "The set identifier of this forwarding
item.";
} }
container te-bift-id { container te-bift-id {
description "The bift-id which is used to locate the specific forwarding item."; description "The bift-id which is used to locate the
specific forwarding item.";
uses te-bift-id; uses te-bift-id;
} }
list fwd-items { list fwd-items {
key "te-bp"; key "te-bp";
description "The forwarding information of one BIER TE item."; description "The forwarding information of one BIER TE
item.";
leaf te-bp { leaf te-bp {
type uint16; type uint16;
mandatory true; mandatory true;
description "The bit index of a BIER TE forwarding item."; description "The bit index of a BIER TE forwarding
item.";
} }
uses bp-type; uses bp-type;
uses te-items; uses te-items;
list te-ecmp { list te-ecmp {
if-feature bier-te-ecmp; if-feature bier-te-ecmp;
key "out-if"; key "out-if";
leaf out-if { leaf out-if {
type if:interface-ref; type if:interface-ref;
description "The outgoing interface."; description "The outgoing interface.";
} }
container te-out-bift-id { container te-out-bift-id {
description "The bift-id info for a specific out interface."; description "The bift-id info for a specific
outbound interface.";
uses te-bift-id; uses te-bift-id;
} }
description "The list of the ecmp paths. When the type of BP is set to ecmp, this interface ecmp list description "The list of the ecmp paths. When the
should be used to balance the load on each interface."; type of BP is set to ecmp, this
interface ecmp list should be used to
balance the load on each interface.";
} }
} }
} }
description "The forwarding items in one combination of SD, BSL and SI."; description "The forwarding items in one combination of
SD, BSL and SI.";
} }
grouping te-info { grouping te-info {
description "The BIER TE forwarding information."; description "The BIER TE forwarding information.";
list subdomain { list subdomain {
key "subdomain-id"; key "subdomain-id";
description "The forwarding items of one sub-domain."; description "The forwarding items of one sub-domain.";
leaf subdomain-id { leaf subdomain-id {
type uint16; type uint16;
description "The sub-domain-id of this sub-domain."; description "The sub-domain-id of this sub-domain.";
} }
container te-adj-id {
list si {
key "si";
description "The forwarding items of a set
identifier.";
leaf si{
type uint16;
mandatory true;
description "The set identifier of this
forwarding item.";
}
list adj {
key "adj-id";
description "The ID of an adjacency.";
leaf adj-id {
type uint16;
mandatory true;
description "The adjacency id.";
}
leaf adj-if {
type if:interface-ref;
mandatory true;
description "The corresponding interface
of this adjacency.";
}
uses bp-type;
}
}
description "This adjacency ID information for BIER TE
in a SI.";
}
container te-bift-id {
description "The bift-id which is used to locate
the specific forwarding item.";
uses te-bift-id;
}
list bsl { list bsl {
key "fwd-bsl"; key "fwd-bsl";
description "The forwarding items in one bitstringlength."; description "The forwarding items in one BSL.";
leaf fwd-bsl { leaf fwd-bsl {
type uint16; type uint16;
description "The value of bitstringlength."; description "The value of bitstringlength.";
} }
uses fwd-items; uses fwd-items;
} }
container te-frr-items { container te-frr-items {
if-feature bier-te-frr; if-feature bier-te-frr;
uses te-frr; uses te-frr;
description "The TE fast re-route items for protective forwarding."; description "The TE protective fast re-route items.";
} }
} }
} }
/* /*
* data nodes * data nodes
*/ */
augment "/rt:routing" { augment "/rt:routing" {
description "The BIER TE information."; description "The BIER TE information.";
container bier-te { container bier-te {
description "The BIER TE information container."; description "The BIER TE information container.";
uses te-info; uses te-info;
} }
} }
skipping to change at page 11, line 20 skipping to change at page 13, line 16
description "The BIER TE information container."; description "The BIER TE information container.";
uses te-info; uses te-info;
} }
} }
/* /*
* Notifications * Notifications
*/ */
notification bier-te-notification { notification bier-te-notification {
description description
"This notification is sent when a condition changes in BIER TE."; "The notification is sent when a condition changes.";
list bp-is-zero { list bp-is-zero {
key "if-index"; key "if-index";
description "The adjacency id is zero. Zero is invalid for BIER TE."; description "The adjacency id is zero. It is invalid.";
leaf if-index { leaf if-index {
type if:interface-ref; type if:interface-ref;
description "The adjacency id of this interface is zero."; description "The adjacency id is zero.";
} }
uses bp-type; uses bp-type;
} }
} }
} }
<CODE ENDS> <CODE ENDS>
7. IANA Considerations 7. IANA Considerations
The IANA is requested to assign two new URIs from the IETF XML The IANA is requested to assign two new URIs from the IETF XML
skipping to change at page 13, line 11 skipping to change at page 15, line 5
[RFC7223] Bjorklund, M., "A YANG Data Model for Interface [RFC7223] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 7223, DOI 10.17487/RFC7223, May 2014, Management", RFC 7223, DOI 10.17487/RFC7223, May 2014,
<https://www.rfc-editor.org/info/rfc7223>. <https://www.rfc-editor.org/info/rfc7223>.
[RFC8279] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., [RFC8279] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A.,
Przygienda, T., and S. Aldrin, "Multicast Using Bit Index Przygienda, T., and S. Aldrin, "Multicast Using Bit Index
Explicit Replication (BIER)", RFC 8279, Explicit Replication (BIER)", RFC 8279,
DOI 10.17487/RFC8279, November 2017, DOI 10.17487/RFC8279, November 2017,
<https://www.rfc-editor.org/info/rfc8279>. <https://www.rfc-editor.org/info/rfc8279>.
[RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for
Routing Management (NMDA Version)", RFC 8349,
DOI 10.17487/RFC8349, March 2018,
<https://www.rfc-editor.org/info/rfc8349>.
Authors' Addresses Authors' Addresses
Zheng(Sandy) Zhang Zheng(Sandy) Zhang
ZTE Corporation ZTE Corporation
No. 50 Software Ave, Yuhuatai Distinct No. 50 Software Ave, Yuhuatai Distinct
Nanjing Nanjing
China China
Email: zhang.zheng@zte.com.cn Email: zhang.zheng@zte.com.cn
 End of changes. 62 change blocks. 
75 lines changed or deleted 185 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/