< draft-ietf-pim-yang-12.txt   draft-ietf-pim-yang-13.txt >
PIM Working Group X. Liu PIM Working Group X. Liu
Internet-Draft Jabil Internet-Draft Jabil
Intended status: Standards Track P. McAllister Intended status: Standards Track P. McAllister
Expires: June 11, 2018 Metaswitch Networks Expires: July 14, 2018 Metaswitch Networks
A. Peter A. Peter
Individual Individual
M. Sivakumar M. Sivakumar
Cisco Systems Cisco Systems
Y. Liu Y. Liu
Huawei Technologies Huawei Technologies
F. Hu F. Hu
ZTE Corporation ZTE Corporation
December 8, 2017 January 10, 2018
A YANG data model for Protocol-Independent Multicast (PIM) A YANG data model for Protocol-Independent Multicast (PIM)
draft-ietf-pim-yang-12 draft-ietf-pim-yang-13
Abstract Abstract
This document defines a YANG data model that can be used to configure This document defines a YANG data model that can be used to configure
and manage Protocol Independent Multicast (PIM) devices. The model and manage Protocol Independent Multicast (PIM) devices. The model
covers the PIM protocol configuration, operational state, and event covers the PIM protocol configuration, operational state, and event
notifications data. notifications data.
Status of This Memo Status of This Memo
skipping to change at page 1, line 42 skipping to change at page 1, line 42
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 11, 2018. This Internet-Draft will expire on July 14, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2018 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Prefixes in Data Node Names . . . . . . . . . . . . . . . 4 1.2. Tree Diagrams Prefixes . . . . . . . . . . . . . . . . . 4
1.3. Prefixes in Data Node Names . . . . . . . . . . . . . . . 4
2. Design of Data Model . . . . . . . . . . . . . . . . . . . . 5 2. Design of Data Model . . . . . . . . . . . . . . . . . . . . 5
2.1. Scope of model . . . . . . . . . . . . . . . . . . . . . 5 2.1. Scope of model . . . . . . . . . . . . . . . . . . . . . 5
2.2. Optional capabilities . . . . . . . . . . . . . . . . . . 5 2.2. Optional capabilities . . . . . . . . . . . . . . . . . . 5
2.3. Datastore applicability . . . . . . . . . . . . . . . . . 6 2.3. Datastore applicability . . . . . . . . . . . . . . . . . 6
2.4. Top-level structure . . . . . . . . . . . . . . . . . . . 6 2.4. Top-level structure . . . . . . . . . . . . . . . . . . . 6
2.5. Position of address family in hierarchy . . . . . . . . . 7 2.5. Position of address family in hierarchy . . . . . . . . . 7
3. Module Structure . . . . . . . . . . . . . . . . . . . . . . 7 3. Module Structure . . . . . . . . . . . . . . . . . . . . . . 7
3.1. PIM base module . . . . . . . . . . . . . . . . . . . . . 7 3.1. PIM base module . . . . . . . . . . . . . . . . . . . . . 7
3.2. PIM RP module . . . . . . . . . . . . . . . . . . . . . . 11 3.2. PIM RP module . . . . . . . . . . . . . . . . . . . . . . 11
3.3. PIM-SM module . . . . . . . . . . . . . . . . . . . . . . 13 3.3. PIM-SM module . . . . . . . . . . . . . . . . . . . . . . 13
3.4. PIM-DM module . . . . . . . . . . . . . . . . . . . . . . 14 3.4. PIM-DM module . . . . . . . . . . . . . . . . . . . . . . 14
3.5. PIM-BIDIR module . . . . . . . . . . . . . . . . . . . . 15 3.5. PIM-BIDIR module . . . . . . . . . . . . . . . . . . . . 15
4. PIM YANG Modules . . . . . . . . . . . . . . . . . . . . . . 16 4. PIM YANG Modules . . . . . . . . . . . . . . . . . . . . . . 16
4.1. PIM base module . . . . . . . . . . . . . . . . . . . . . 16 4.1. PIM base module . . . . . . . . . . . . . . . . . . . . . 16
4.2. PIM RP module . . . . . . . . . . . . . . . . . . . . . . 34 4.2. PIM RP module . . . . . . . . . . . . . . . . . . . . . . 34
4.3. PIM-SM module . . . . . . . . . . . . . . . . . . . . . . 49 4.3. PIM-SM module . . . . . . . . . . . . . . . . . . . . . . 49
4.4. PIM-DM module . . . . . . . . . . . . . . . . . . . . . . 54 4.4. PIM-DM module . . . . . . . . . . . . . . . . . . . . . . 54
4.5. PIM-BIDIR module . . . . . . . . . . . . . . . . . . . . 56 4.5. PIM-BIDIR module . . . . . . . . . . . . . . . . . . . . 56
5. Implementation Status . . . . . . . . . . . . . . . . . . . . 63 5. Implementation Status . . . . . . . . . . . . . . . . . . . . 63
6. Security Considerations . . . . . . . . . . . . . . . . . . . 64 6. Security Considerations . . . . . . . . . . . . . . . . . . . 64
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 64 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 66
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 66 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 67
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 66 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 67
9.1. Normative References . . . . . . . . . . . . . . . . . . 66 9.1. Normative References . . . . . . . . . . . . . . . . . . 67
9.2. Informative References . . . . . . . . . . . . . . . . . 68 9.2. Informative References . . . . . . . . . . . . . . . . . 70
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 69 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 71
1. Introduction 1. Introduction
YANG [RFC6020] [RFC7950] is a data definition language that was YANG [RFC6020] [RFC7950] is a data definition language that was
introduced to model the configuration and running state of a device introduced to model the configuration and running state of a device
managed using network management protocols such as NETCONF [RFC6241]. managed using network management protocols such as NETCONF [RFC6241]
or RESTCONF [RFC8040]. YANG is now also being used as a component of
YANG is now also being used as a component of wider management wider management interfaces, such as CLIs.
interfaces, such as CLIs.
This document defines a YANG data model that can be used to configure This document defines a YANG data model that can be used to configure
and manage Protocol-Independent Multicast (PIM) devices. This model and manage Protocol-Independent Multicast (PIM) devices. This model
supports the core PIM protocol, as well as many other features supports the core PIM protocol, as well as many other features
described in Section 2.1. Non-core features are defined as optional described in Section 2.1. Non-core features are defined as optional
in the provided data model. in the provided data model.
1.1. Terminology 1.1. Terminology
The terminology for describing YANG data models is found in [RFC6020] The terminology for describing YANG data models is found in [RFC6020]
and [RFC7950]. and [RFC7950].
A simplified graphical representation of the data model is used in
this document. The meaning of the symbols in these diagrams is
defined in [I-D.ietf-netmod-yang-tree-diagrams].
The following abbreviations are used in this document and the defined The following abbreviations are used in this document and the defined
model: model:
ASM: ASM:
Any-Source Multicast service model [RFC3569] [RFC4607]. Any-Source Multicast service model [RFC3569] [RFC4607].
BFD: BFD:
Bidirectional Forwarding Detection [RFC5880]. Bidirectional Forwarding Detection [RFC5880].
BSR: BSR:
skipping to change at page 4, line 44 skipping to change at page 4, line 40
SPT: SPT:
Shortest Path Tree. [RFC7761]. Shortest Path Tree. [RFC7761].
SSM: SSM:
Source-Specific Multicast service model [RFC3569] [RFC4607]. Source-Specific Multicast service model [RFC3569] [RFC4607].
VRF: VRF:
Virtual Routing and Forwarding. Virtual Routing and Forwarding.
1.2. Prefixes in Data Node Names 1.2. Tree Diagrams Prefixes
Tree diagrams used in this document follow the notation defined in
[I-D.ietf-netmod-yang-tree-diagrams].
1.3. Prefixes in Data Node Names
In this document, names of data nodes, actions, and other data model In this document, names of data nodes, actions, and other data model
objects are often used without a prefix, as long as it is clear from objects are often used without a prefix, as long as it is clear from
the context in which YANG module each name is defined. Otherwise, the context in which YANG module each name is defined. Otherwise,
names are prefixed using the standard prefix associated with the names are prefixed using the standard prefix associated with the
corresponding YANG module, as shown in Table 1. corresponding YANG module, as shown in Table 1.
+-----------+--------------------+--------------------------------+ +-----------+--------------------+------------------------------+
| Prefix | YANG module | Reference | | Prefix | YANG module | Reference |
+-----------+--------------------+--------------------------------+ +-----------+--------------------+------------------------------+
| yang | ietf-yang-types | [RFC6991] | | yang | ietf-yang-types | [RFC6991] |
| inet | ietf-inet-types | [RFC6991] | | inet | ietf-inet-types | [RFC6991] |
| if | ietf-interfaces | [I-D.ietf-netmod-rfc7223bis] | | if | ietf-interfaces | [I-D.ietf-netmod-rfc7223bis] |
| rt | ietf-routing | [I-D.ietf-netmod-rfc8022bis] | | rt | ietf-routing | [I-D.ietf-netmod-rfc8022bis] |
| rt-types | ietf-routing-types | [I-D.ietf-rtgwg-routing-types] | | rt-types | ietf-routing-types | [RFC8294] |
| bfd-types | ietf-bfd-types | [I-D.ietf-bfd-yang] | | bfd-types | ietf-bfd-types | [I-D.ietf-bfd-yang] |
+-----------+--------------------+--------------------------------+ +-----------+--------------------+------------------------------+
Table 1: Prefixes and Corresponding YANG Modules Table 1: Prefixes and Corresponding YANG Modules
2. Design of Data Model 2. Design of Data Model
2.1. Scope of model 2.1. Scope of model
The model covers PIM Sparse Mode [RFC7761], including the Source- The model covers PIM Sparse Mode [RFC7761], including the Source-
Specific subset [RFC3569] [RFC4607], Dense Mode [RFC3973], and Bi- Specific subset [RFC3569] [RFC4607], Dense Mode [RFC3973], and Bi-
directional PIM [RFC5015]. directional PIM [RFC5015].
skipping to change at page 64, line 28 skipping to change at page 64, line 28
This document is the work result of the PIM working group's YANG This document is the work result of the PIM working group's YANG
multicast design team. The following wiki page contains the multicast design team. The following wiki page contains the
information on the design team members, the meeting discussions, information on the design team members, the meeting discussions,
lists of modeled features, and which features are supported by which lists of modeled features, and which features are supported by which
existing implementations: existing implementations:
https://trac.ietf.org/trac/pim/wiki/yang https://trac.ietf.org/trac/pim/wiki/yang
6. Security Considerations 6. Security Considerations
Configuration and state data defined in this document are designed to The YANG module specified in this document defines a schema for data
be accessed via a management protocol with secure transport layer, that is designed to be accessed via network management protocols such
such as NETCONF [RFC6241]. The NETCONF access control model as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer
[RFC6536] provides the means to restrict access for specific users to is the secure transport layer, and the mandatory-to-implement secure
a pre- configured subset of all available operations and contents. transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer
is HTTPS, and the mandatory-to-implement secure transport is TLS
[RFC5246].
The models defined in this document contain a number of configuration The NETCONF access control model [RFC6536] provides the means to
data nodes that are writable, creatable, and deletable. Unauthorised restrict access for particular NETCONF or RESTCONF users to a
access to the configuration data can adversely affect the routing preconfigured subset of all available NETCONF or RESTCONF protocol
subsystem of both the local device and the network. This may lead to operations and content.
network malfunctions, delivery of packets to inappropriate
destinations and other problems. There are a number of data nodes defined in this YANG module that are
writable/creatable/deletable (i.e., config true, which is the
default). These data nodes may be considered sensitive or vulnerable
in some network environments. Write operations (e.g., edit-config)
to these data nodes without proper protection can have a negative
effect on network operations. These are the subtrees and data nodes
and their sensitivity/vulnerability:
pim-base:graceful-restart
This subtree specifies the configuration for the PIM graceful
restart at the global level on a device. Modifying the
configuration can cause temporary interruption to the multicast
routing during restart.
pim-base:address-family/pim-base:graceful-restart
This subtree specifies the per address family configuration for
the PIM graceful restart on a device. Modifying the configuration
can cause temporary interruption to the multicast routing during
restart.
pim-base:address-family/pim-rp:pim-rp:rp
This subtree specifies the configuration for the PIM Rendezvous
Point (RP) on a device. Modifying the configuration can cause RP
malfunctions.
pim-base:address-family/pim-sm:sm
This subtree specifies the configuration for the PIM Sparse Mode
(PIM-SM) on a device. Modifying the configuration can cause
multicast traffic disabled or rerouted in PIM-SM.
pim-base:address-family/pim-dm:dm
This subtree specifies the configuration for the PIM Dense Mode
(PIM-DM) on a device. Modifying the configuration can cause
multicast traffic disabled or rerouted in PIM-DM.
pim-base:address-family/pim-bidir:bidir
This subtree specifies the configuration for the PIM Bidirectional
Mode (PIM-BIDIR) on a device. Modifying the configuration can
cause multicast traffic disabled or rerouted in PIM-BIDIR.
pim-base:interfaces
This subtree specifies the configuration for the PIM interfaces on
a device. Modifying the configuration can cause the PIM protocol
to get insufficient or incorrect information.
These subtrees are all nnder /rt:routing/rt:control-plane-protocols/
pim-base:pim.
Unauthorized access to any data node of these subtrees can adversely
affect the multicast routing subsystem of both the local device and
the network. This may lead to network malfunctions, delivery of
packets to inappropriate destinations, and other problems.
Some of the readable data nodes in this YANG module may be considered
sensitive or vulnerable in some network environments. It is thus
important to control read access (e.g., via get, get-config, or
notification) to these data nodes. These are the subtrees and data
nodes and their sensitivity/vulnerability:
/rt:routing/rt:control-plane-protocols/pim-base:pim
Unauthorized access to any data node of the above subtree can
disclose the operational state information of PIM on this device.
7. IANA Considerations 7. IANA Considerations
RFC Ed.: In this section, replace all occurrences of 'XXXX' with the RFC Ed.: In this section, replace all occurrences of 'XXXX' with the
actual RFC number (and remove this note). actual RFC number (and remove this note).
This document registers the following namespace URIs in the IETF XML This document registers the following namespace URIs in the IETF XML
registry [RFC3688]: registry [RFC3688]:
-------------------------------------------------------------------- --------------------------------------------------------------------
skipping to change at page 67, line 20 skipping to change at page 68, line 33
[RFC5015] Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano, [RFC5015] Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano,
"Bidirectional Protocol Independent Multicast (BIDIR- "Bidirectional Protocol Independent Multicast (BIDIR-
PIM)", RFC 5015, DOI 10.17487/RFC5015, October 2007, PIM)", RFC 5015, DOI 10.17487/RFC5015, October 2007,
<https://www.rfc-editor.org/info/rfc5015>. <https://www.rfc-editor.org/info/rfc5015>.
[RFC5059] Bhaskar, N., Gall, A., Lingard, J., and S. Venaas, [RFC5059] Bhaskar, N., Gall, A., Lingard, J., and S. Venaas,
"Bootstrap Router (BSR) Mechanism for Protocol Independent "Bootstrap Router (BSR) Mechanism for Protocol Independent
Multicast (PIM)", RFC 5059, DOI 10.17487/RFC5059, January Multicast (PIM)", RFC 5059, DOI 10.17487/RFC5059, January
2008, <https://www.rfc-editor.org/info/rfc5059>. 2008, <https://www.rfc-editor.org/info/rfc5059>.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246,
DOI 10.17487/RFC5246, August 2008, <https://www.rfc-
editor.org/info/rfc5246>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, <https://www.rfc- DOI 10.17487/RFC6020, October 2010, <https://www.rfc-
editor.org/info/rfc6020>. editor.org/info/rfc6020>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<https://www.rfc-editor.org/info/rfc6242>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536,
DOI 10.17487/RFC6536, March 2012, <https://www.rfc-
editor.org/info/rfc6536>.
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
RFC 6991, DOI 10.17487/RFC6991, July 2013, RFC 6991, DOI 10.17487/RFC6991, July 2013,
<https://www.rfc-editor.org/info/rfc6991>. <https://www.rfc-editor.org/info/rfc6991>.
[RFC7761] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I., [RFC7761] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I.,
Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent
Multicast - Sparse Mode (PIM-SM): Protocol Specification Multicast - Sparse Mode (PIM-SM): Protocol Specification
(Revised)", STD 83, RFC 7761, DOI 10.17487/RFC7761, March (Revised)", STD 83, RFC 7761, DOI 10.17487/RFC7761, March
2016, <https://www.rfc-editor.org/info/rfc7761>. 2016, <https://www.rfc-editor.org/info/rfc7761>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016, RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/info/rfc7950>. <https://www.rfc-editor.org/info/rfc7950>.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/info/rfc8040>.
[RFC8294] Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger,
"Common YANG Data Types for the Routing Area", RFC 8294,
DOI 10.17487/RFC8294, December 2017, <https://www.rfc-
editor.org/info/rfc8294>.
[I-D.ietf-netmod-revised-datastores] [I-D.ietf-netmod-revised-datastores]
Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore and R. Wilton, "Network Management Datastore
Architecture", draft-ietf-netmod-revised-datastores-07 Architecture", draft-ietf-netmod-revised-datastores-09
(work in progress), November 2017. (work in progress), December 2017.
[I-D.ietf-netmod-rfc7223bis] [I-D.ietf-netmod-rfc7223bis]
Bjorklund, M., "A YANG Data Model for Interface Bjorklund, M., "A YANG Data Model for Interface
Management", draft-ietf-netmod-rfc7223bis-00 (work in Management", draft-ietf-netmod-rfc7223bis-02 (work in
progress), October 2017. progress), January 2018.
[I-D.ietf-netmod-rfc8022bis] [I-D.ietf-netmod-rfc8022bis]
Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for
Routing Management (NDMA Version)", draft-ietf-netmod- Routing Management (NDMA Version)", draft-ietf-netmod-
rfc8022bis-02 (work in progress), November 2017. rfc8022bis-08 (work in progress), January 2018.
[I-D.ietf-rtgwg-routing-types]
Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger,
"Routing Area Common YANG Data Types", draft-ietf-rtgwg-
routing-types-17 (work in progress), October 2017.
[I-D.ietf-bfd-yang] [I-D.ietf-bfd-yang]
Rahman, R., Zheng, L., Jethanandani, M., Networks, J., and Rahman, R., Zheng, L., Jethanandani, M., Networks, J., and
G. Mirsky, "YANG Data Model for Bidirectional Forwarding G. Mirsky, "YANG Data Model for Bidirectional Forwarding
Detection (BFD)", draft-ietf-bfd-yang-07 (work in Detection (BFD)", draft-ietf-bfd-yang-07 (work in
progress), October 2017. progress), October 2017.
9.2. Informative References 9.2. Informative References
[RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. [RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A.
skipping to change at page 68, line 42 skipping to change at page 70, line 32
[RFC3810] Vida, R., Ed. and L. Costa, Ed., "Multicast Listener [RFC3810] Vida, R., Ed. and L. Costa, Ed., "Multicast Listener
Discovery Version 2 (MLDv2) for IPv6", RFC 3810, Discovery Version 2 (MLDv2) for IPv6", RFC 3810,
DOI 10.17487/RFC3810, June 2004, <https://www.rfc- DOI 10.17487/RFC3810, June 2004, <https://www.rfc-
editor.org/info/rfc3810>. editor.org/info/rfc3810>.
[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010, (BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010,
<https://www.rfc-editor.org/info/rfc5880>. <https://www.rfc-editor.org/info/rfc5880>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>.
[RFC6388] Wijnands, IJ., Ed., Minei, I., Ed., Kompella, K., and B. [RFC6388] Wijnands, IJ., Ed., Minei, I., Ed., Kompella, K., and B.
Thomas, "Label Distribution Protocol Extensions for Point- Thomas, "Label Distribution Protocol Extensions for Point-
to-Multipoint and Multipoint-to-Multipoint Label Switched to-Multipoint and Multipoint-to-Multipoint Label Switched
Paths", RFC 6388, DOI 10.17487/RFC6388, November 2011, Paths", RFC 6388, DOI 10.17487/RFC6388, November 2011,
<https://www.rfc-editor.org/info/rfc6388>. <https://www.rfc-editor.org/info/rfc6388>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536,
DOI 10.17487/RFC6536, March 2012, <https://www.rfc-
editor.org/info/rfc6536>.
[RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running
Code: The Implementation Status Section", BCP 205, Code: The Implementation Status Section", BCP 205,
RFC 7942, DOI 10.17487/RFC7942, July 2016, RFC 7942, DOI 10.17487/RFC7942, July 2016,
<https://www.rfc-editor.org/info/rfc7942>. <https://www.rfc-editor.org/info/rfc7942>.
[I-D.ietf-netmod-rfc6087bis] [I-D.ietf-netmod-rfc6087bis]
Bierman, A., "Guidelines for Authors and Reviewers of YANG Bierman, A., "Guidelines for Authors and Reviewers of YANG
Data Model Documents", draft-ietf-netmod-rfc6087bis-14 Data Model Documents", draft-ietf-netmod-rfc6087bis-15
(work in progress), September 2017. (work in progress), December 2017.
[I-D.ietf-netmod-yang-tree-diagrams] [I-D.ietf-netmod-yang-tree-diagrams]
Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft- Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft-
ietf-netmod-yang-tree-diagrams-02 (work in progress), ietf-netmod-yang-tree-diagrams-04 (work in progress),
October 2017. December 2017.
Authors' Addresses Authors' Addresses
Xufeng Liu Xufeng Liu
Jabil Jabil
8281 Greensboro Drive, Suite 200 8281 Greensboro Drive, Suite 200
McLean VA 22102 McLean VA 22102
USA USA
EMail: Xufeng_Liu@jabil.com EMail: Xufeng_Liu@jabil.com
 End of changes. 23 change blocks. 
66 lines changed or deleted 144 lines changed or added

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