draft-ietf-isis-sr-yang-04.txt   draft-ietf-isis-sr-yang-05.txt 
IS-IS Working Group S. Litkowski IS-IS Working Group S. Litkowski
Internet-Draft Orange Internet-Draft Orange
Intended status: Standards Track Y. Qu Intended status: Standards Track Y. Qu
Expires: December 31, 2018 Huawei Expires: September 11, 2019 Huawei
P. Sarkar P. Sarkar
Individual Individual
I. Chen I. Chen
Jabil The MITRE Corporation
J. Tantsura J. Tantsura
Individual Individual
June 29, 2018 March 10, 2019
YANG Data Model for IS-IS Segment Routing YANG Data Model for IS-IS Segment Routing
draft-ietf-isis-sr-yang-04 draft-ietf-isis-sr-yang-05
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 IS-IS Segment Routing and manage IS-IS Segment Routing.
([I-D.ietf-isis-segment-routing-extensions].
Requirements Language
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 [RFC2119].
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.
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 December 31, 2018. This Internet-Draft will expire on September 11, 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. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. IS-IS Segment Routing . . . . . . . . . . . . . . . . . . . . 3 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
3. IS-IS Segment Routing configuration . . . . . . . . . . . . . 6 3. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Segment Routing activation . . . . . . . . . . . . . . . 6 4. IS-IS Segment Routing . . . . . . . . . . . . . . . . . . . . 3
3.2. Advertising mapping server policy . . . . . . . . . . . . 6 5. IS-IS Segment Routing configuration . . . . . . . . . . . . . 6
3.3. IP Fast reroute . . . . . . . . . . . . . . . . . . . . . 6 5.1. Segment Routing activation . . . . . . . . . . . . . . . 6
4. IS-IS Segment Routing YANG Module . . . . . . . . . . . . . . 6 5.2. Advertising mapping server policy . . . . . . . . . . . . 6
5. Security Considerations . . . . . . . . . . . . . . . . . . . 20 5.3. IP Fast reroute . . . . . . . . . . . . . . . . . . . . . 6
6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 20 6. IS-IS Segment Routing YANG Module . . . . . . . . . . . . . . 6
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21 7. Security Considerations . . . . . . . . . . . . . . . . . . . 20
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 21
9. Change log for ietf-isis-sr YANG module . . . . . . . . . . . 21 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21
9.1. From version -03 to version -04 . . . . . . . . . . . . . 21 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
9.2. From version -02 to version -03 . . . . . . . . . . . . . 21 11. Change log for ietf-isis-sr YANG module . . . . . . . . . . . 21
9.3. From isis-sr document version -01 to version -02 . . . . 21 11.1. From version -03 to version -04 . . . . . . . . . . . . 21
9.4. From isis-sr document version -00 to version -01 . . . . 22 11.2. From version -02 to version -03 . . . . . . . . . . . . 21
9.5. From isis document version -12 to isis-sr document 11.3. From isis-sr document version -01 to version -02 . . . . 22
version -00 . . . . . . . . . . . . . . . . . . . . . . . 22 11.4. From isis-sr document version -00 to version -01 . . . . 22
9.6. From isis document version -12 to version -13 . . . . . . 22 11.5. From isis document version -12 to isis-sr document
9.7. From isis document version -09 to version -11 . . . . . . 22 version -00 . . . . . . . . . . . . . . . . . . . . . . 22
9.8. From isis document version -08 to version -09 . . . . . . 22 11.6. From isis document version -12 to version -13 . . . . . 22
9.9. From isis document version -07 to version -08 . . . . . . 22 11.7. From isis document version -09 to version -11 . . . . . 22
10. Normative References . . . . . . . . . . . . . . . . . . . . 22 11.8. From isis document version -08 to version -09 . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 11.9. From isis document version -07 to version -08 . . . . . 22
12. Normative References . . . . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24
1. Overview 1. Overview
YANG [RFC6020] [RFC7950] is a data definition language used to YANG [RFC6020] [RFC7950] is a data definition language used to define
define the contents of a conceptual data store that allows networked the contents of a conceptual data store that allows networked devices
devices to be managed using NETCONF [RFC6241]. YANG is proving to be managed using NETCONF [RFC6241]. YANG is proving relevant
relevant beyond its initial confines, as bindings to other interfaces beyond its initial confines, as bindings to other interfaces (e.g.,
(e.g., ReST) and encodings other than XML (e.g., JSON) are being ReST) and encodings other than XML (e.g., JSON) are being defined.
defined. Furthermore, YANG data models can be used as the basis for Furthermore, YANG data models can be used as the basis for
implementation of other interfaces, such as CLI and programmatic implementation of other interfaces, such as CLI and programmatic
APIs. APIs.
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 IS-IS Segment Routing and it is an augmentation to the IS- and manage IS-IS Segment Routing
IS YANG data model.
2. IS-IS Segment Routing [I-D.ietf-isis-segment-routing-extensions] and it is an augmentation
to the IS-IS YANG data model.
The YANG modules in this document conform to the Network Management
Datastore Architecture (NMDA) [RFC8342].
2. Requirements Language
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 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
3. Tree Diagrams
This document uses the graphical representation of data models
defined in [RFC8340].
4. IS-IS Segment Routing
This document defines a model for IS-IS Segment Routing feature. It This document defines a model for IS-IS Segment Routing feature. It
is an augmentation of the IS-IS base model. is an augmentation of the IS-IS base model.
The IS-IS SR YANG module requires support for the base segment The IS-IS SR YANG module requires support for the base segment
routing module [I-D.ietf-spring-sr-yang], which defines the global routing module [I-D.ietf-spring-sr-yang], which defines the global
segment routing configuration independent of any specific routing segment routing configuration independent of any specific routing
protocol configuration, and support of IS-IS base model protocol configuration, and support of IS-IS base model
[I-D.ietf-isis-yang-isis-cfg] which defines basic IS-IS configuration [I-D.ietf-isis-yang-isis-cfg] which defines basic IS-IS configuration
and state. and state.
skipping to change at page 6, line 5 skipping to change at page 6, line 13
+--ro fec string +--ro fec string
+--ro range uint16 +--ro range uint16
+--ro flags? bits +--ro flags? bits
+--ro binding +--ro binding
+--ro prefix-sid +--ro prefix-sid
+--ro sid-list* [value] +--ro sid-list* [value]
+--ro flags? bits +--ro flags? bits
+--ro algorithm? uint8 +--ro algorithm? uint8
+--ro value uint32 +--ro value uint32
3. IS-IS Segment Routing configuration 5. IS-IS Segment Routing configuration
3.1. Segment Routing activation 5.1. Segment Routing activation
Activation of segment-routing IS-IS is done by setting the "enable" Activation of segment-routing IS-IS is done by setting the "enable"
leaf to true. This triggers advertisement of segment-routing leaf to true. This triggers advertisement of segment-routing
extensions based on the configuration parameters that have been setup extensions based on the configuration parameters that have been setup
using the base segment routing module. using the base segment routing module.
3.2. Advertising mapping server policy 5.2. Advertising mapping server policy
The base segment routing module defines mapping server policies. By The base segment routing module defines mapping server policies. By
default, IS-IS will not advertise nor receive any mapping server default, IS-IS will not advertise nor receive any mapping server
entry. The IS-IS segment-routing module allows to advertise one or entry. The IS-IS segment-routing module allows to advertise one or
multiple mapping server policies through the "bindings/advertise/ multiple mapping server policies through the "bindings/advertise/
policies" leaf-list. The "bindings/receive" leaf allows to enable policies" leaf-list. The "bindings/receive" leaf allows to enable
the reception of mapping server entries. the reception of mapping server entries.
3.3. IP Fast reroute 5.3. IP Fast reroute
IS-IS SR model augments the fast-reroute container under interface. IS-IS SR model augments the fast-reroute container under interface.
It brings the ability to activate TI-LFA (topology independent LFA) It brings the ability to activate TI-LFA (topology independent LFA)
and also enhances remote LFA to use segment-routing tunneling instead and also enhances remote LFA to use segment-routing tunneling instead
of LDP. of LDP.
4. IS-IS Segment Routing YANG Module 6. IS-IS Segment Routing YANG Module
<CODE BEGINS> file "ietf-isis-sr@2018-06-25.yang" <CODE BEGINS> file "ietf-isis-sr@2019-03-06.yang"
module ietf-isis-sr { module ietf-isis-sr {
namespace "urn:ietf:params:xml:ns:" namespace "urn:ietf:params:xml:ns:"
+ "yang:ietf-isis-sr"; + "yang:ietf-isis-sr";
prefix isis-sr; prefix isis-sr;
import ietf-routing { import ietf-routing {
prefix "rt"; prefix "rt";
} }
import ietf-segment-routing-common { import ietf-segment-routing-common {
skipping to change at page 7, line 23 skipping to change at page 7, line 31
contact contact
"WG List: <mailto:lsr@ietf.org> "WG List: <mailto:lsr@ietf.org>
Editor: Stephane Litkowski Editor: Stephane Litkowski
<mailto:stephane.litkowski@orange.com> <mailto:stephane.litkowski@orange.com>
Author: Acee Lindem Author: Acee Lindem
<mailto:acee@cisco.com> <mailto:acee@cisco.com>
Author: Yingzhen Qu Author: Yingzhen Qu
<mailto:yiqu@cisco.com> <mailto:yingzhen.qu@huawei.com>
Author: Pushpasis Sarkar Author: Pushpasis Sarkar
<mailto:pushpasis.ietf@gmail.com> <mailto:pushpasis.ietf@gmail.com>
Author: Ing-Wher Chen Author: Ing-Wher Chen
<mailto:ichen@kuatrotech.com> <mailto:ingwherchen@mitre.org>
Author: Jeff Tantsura Author: Jeff Tantsura
<mailto:jefftant.ietf@gmail.com> <mailto:jefftant.ietf@gmail.com>
"; ";
description description
"The YANG module defines a generic configuration model for "The YANG module defines a generic configuration model for
Segment routing ISIS extensions common across all of the vendor Segment routing ISIS extensions common across all of the vendor
implementations."; implementations.";
revision 2018-06-25 { revision 2019-03-06 {
description description
"Initial revision."; "Initial revision.";
reference "RFC XXXX"; reference "RFC XXXX";
} }
/* Identities */ /* Identities */
/* Features */ /* Features */
feature remote-lfa-sr { feature remote-lfa-sr {
description description
"Enhance rLFA to use SR path."; "Enhance rLFA to use SR path.";
} }
feature ti-lfa { feature ti-lfa {
description description
"Enhance IPFRR with ti-lfa "Enhance IPFRR with ti-lfa
support"; support";
} }
/* Groupings */ /* Groupings */
skipping to change at page 16, line 15 skipping to change at page 16, line 25
"/isis:isis" { "/isis:isis" {
when "/rt:routing/rt:control-plane-protocols/"+ when "/rt:routing/rt:control-plane-protocols/"+
"rt:control-plane-protocol/rt:type = 'isis:isis'" { "rt:control-plane-protocol/rt:type = 'isis:isis'" {
description description
"This augment ISIS routing protocol when used"; "This augment ISIS routing protocol when used";
} }
description description
"This augments ISIS protocol configuration "This augments ISIS protocol configuration
with segment routing."; with segment routing.";
uses sr:controlplane-cfg; uses sr:sr-controlplane;
container protocol-srgb { container protocol-srgb {
if-feature sr:protocol-srgb; if-feature sr:protocol-srgb;
uses sr-cmn:srgb-cfg; uses sr-cmn:srgb;
description description
"Per-protocol SRGB."; "Per-protocol SRGB.";
} }
} }
augment "/rt:routing/" + augment "/rt:routing/" +
"rt:control-plane-protocols/rt:control-plane-protocol"+ "rt:control-plane-protocols/rt:control-plane-protocol"+
"/isis:isis/isis:interfaces/isis:interface" { "/isis:isis/isis:interfaces/isis:interface" {
when "/rt:routing/rt:control-plane-protocols/"+ when "/rt:routing/rt:control-plane-protocols/"+
"rt:control-plane-protocol/rt:type = 'isis:isis'" { "rt:control-plane-protocol/rt:type = 'isis:isis'" {
description description
"This augment ISIS routing protocol when used"; "This augment ISIS routing protocol when used";
} }
description description
"This augments ISIS protocol configuration "This augments ISIS protocol configuration
with segment routing."; with segment routing.";
uses sr:igp-interface-cfg; uses sr:igp-interface;
} }
augment "/rt:routing/" + augment "/rt:routing/" +
"rt:control-plane-protocols/rt:control-plane-protocol"+ "rt:control-plane-protocols/rt:control-plane-protocol"+
"/isis:isis/isis:interfaces/isis:interface"+ "/isis:isis/isis:interfaces/isis:interface"+
"/isis:fast-reroute" { "/isis:fast-reroute" {
when "/rt:routing/rt:control-plane-protocols/"+ when "/rt:routing/rt:control-plane-protocols/"+
"rt:control-plane-protocol/rt:type = 'isis:isis'" { "rt:control-plane-protocol/rt:type = 'isis:isis'" {
description description
"This augment ISIS routing protocol when used"; "This augment ISIS routing protocol when used";
skipping to change at page 20, line 31 skipping to change at page 20, line 41
description description
"This augments ISIS protocol LSDB."; "This augments ISIS protocol LSDB.";
uses segment-routing-binding-tlv; uses segment-routing-binding-tlv;
} }
/* Notifications */ /* Notifications */
} }
<CODE ENDS> <CODE ENDS>
5. Security Considerations 7. Security Considerations
Configuration and state data defined in this document are designed to Configuration and state data defined in this document are designed to
be accessed via the NETCONF protocol [RFC6241]. be accessed via the NETCONF protocol [RFC6241].
As IS-IS is an IGP protocol (critical piece of the network), ensuring As IS-IS is an IGP protocol (critical piece of the network), ensuring
stability and security of the protocol is mandatory for the network stability and security of the protocol is mandatory for the network
service. service.
Authors recommends to implement NETCONF access control model Authors recommends to implement NETCONF access control model
([RFC6536]) to restrict access to all or part of the configuration to ([RFC6536]) to restrict access to all or part of the configuration to
specific users. specific users.
6. Contributors 8. Contributors
Authors would like to thank Derek Yeung, Acee Lindem, Yi Yang for Authors would like to thank Derek Yeung, Acee Lindem, Yi Yang for
their major contributions to the draft. their major contributions to the draft.
7. Acknowledgements 9. Acknowledgements
TBD. Author affiliation with The MITRE Corporation is provided for
identification purposes only, and is not intended to convey or imply
MITRE's concurrence with, or support for, the positions, opinions or
viewpoints expressed. MITRE has approved this document for Public
Release, Distribution Unlimited, with Public Release Case Number
18-3281.
8. IANA Considerations 10. 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
registry ([RFC3688]). Authors are suggesting the following URI: registry ([RFC3688]). Authors are suggesting the following URI:
URI: urn:ietf:params:xml:ns:yang:ietf-isis-sr URI: urn:ietf:params:xml:ns:yang:ietf-isis-sr
Registrant Contact: IS-IS WG Registrant Contact: IS-IS WG
XML: N/A, the requested URI is an XML namespace XML: N/A, the requested URI is an XML namespace
This document also requests one new YANG module name in the YANG This document also requests one new YANG module name in the YANG
Module Names registry ([RFC6020]) with the following suggestion : Module Names registry ([RFC6020]) with the following suggestion :
name: ietf-isis-sr name: ietf-isis-sr
namespace: urn:ietf:params:xml:ns:yang:ietf-isis-sr namespace: urn:ietf:params:xml:ns:yang:ietf-isis-sr
prefix: isis-sr prefix: isis-sr
reference: RFC XXXX reference: RFC XXXX
9. Change log for ietf-isis-sr YANG module 11. Change log for ietf-isis-sr YANG module
9.1. From version -03 to version -04 11.1. From version -03 to version -04
o Fixed yang module indentations. o Fixed yang module indentations.
9.2. From version -02 to version -03 11.2. From version -02 to version -03
o Change address-family type according to routing types. o Change address-family type according to routing types.
9.3. From isis-sr document version -01 to version -02 11.3. From isis-sr document version -01 to version -02
o NMDA compliancy. o NMDA compliancy.
o Added SRLB in configuration and LSDB. o Added SRLB in configuration and LSDB.
o Added SR capability in LSDB. o Added SR capability in LSDB.
o Added SR algorithms in LSDB. o Added SR algorithms in LSDB.
o Added SRMS preference in LSDB. o Added SRMS preference in LSDB.
o Alignment with iana-rt-types module. o Alignment with iana-rt-types module.
o Align binding SID with draft-ietf-isis-segment-routing-extensions- o Align binding SID with draft-ietf-isis-segment-routing-extensions-
13. 13.
9.4. From isis-sr document version -00 to version -01 11.4. From isis-sr document version -00 to version -01
o Added P-Flag in Adj-SID. o Added P-Flag in Adj-SID.
9.5. From isis document version -12 to isis-sr document version -00 11.5. From isis document version -12 to isis-sr document version -00
o Separate document for IS-IS SR extensions. o Separate document for IS-IS SR extensions.
9.6. From isis document version -12 to version -13 11.6. From isis document version -12 to version -13
o Align with new segment routing common module. o Align with new segment routing common module.
9.7. From isis document version -09 to version -11 11.7. From isis document version -09 to version -11
o Fixed XPATH in 'when' expressions. o Fixed XPATH in 'when' expressions.
9.8. From isis document version -08 to version -09 11.8. From isis document version -08 to version -09
o Align to draft-ietf-netmod-routing-cfg-23. o Align to draft-ietf-netmod-routing-cfg-23.
9.9. From isis document version -07 to version -08 11.9. From isis document version -07 to version -08
o Align to draft-ietf-netmod-routing-cfg-21. o Align to draft-ietf-netmod-routing-cfg-21.
10. Normative References 12. Normative References
[I-D.ietf-isis-segment-routing-extensions] [I-D.ietf-isis-segment-routing-extensions]
Previdi, S., Ginsberg, L., Filsfils, C., Bashandy, A., Previdi, S., Ginsberg, L., Filsfils, C., Bashandy, A.,
Gredler, H., Litkowski, S., Decraene, B., and J. Tantsura, Gredler, H., Litkowski, S., Decraene, B., and J. Tantsura,
"IS-IS Extensions for Segment Routing", draft-ietf-isis- "IS-IS Extensions for Segment Routing", draft-ietf-isis-
segment-routing-extensions-15 (work in progress), December segment-routing-extensions-22 (work in progress).
2017.
[I-D.ietf-isis-yang-isis-cfg] [I-D.ietf-isis-yang-isis-cfg]
Litkowski, S., Yeung, D., Lindem, A., Zhang, Z., and L. Litkowski, S., Yeung, D., Lindem, A., Zhang, Z., and L.
Lhotka, "YANG Data Model for IS-IS protocol", draft-ietf- Lhotka, "YANG Data Model for IS-IS Protocol", draft-ietf-
isis-yang-isis-cfg-19 (work in progress), November 2017. isis-yang-isis-cfg-35 (work in progress), March 2019.
[I-D.ietf-spring-sr-yang] [I-D.ietf-spring-sr-yang]
Litkowski, S., Qu, Y., Sarkar, P., and J. Tantsura, "YANG Litkowski, S., Qu, Y., Sarkar, P., and J. Tantsura, "YANG
Data Model for Segment Routing", draft-ietf-spring-sr- Data Model for Segment Routing", draft-ietf-spring-sr-
yang-08 (work in progress), December 2017. yang-08 (work in progress), December 2017.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
skipping to change at page 23, line 28 skipping to change at page 23, line 43
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536, Protocol (NETCONF) Access Control Model", RFC 6536,
DOI 10.17487/RFC6536, March 2012, DOI 10.17487/RFC6536, March 2012,
<https://www.rfc-editor.org/info/rfc6536>. <https://www.rfc-editor.org/info/rfc6536>.
[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>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/info/rfc8340>.
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
<https://www.rfc-editor.org/info/rfc8342>.
Authors' Addresses Authors' Addresses
Stephane Litkowski Stephane Litkowski
Orange Orange
Email: stephane.litkowski@orange.com Email: stephane.litkowski@orange.com
Yinghzen Qu Yinghzen Qu
Huawei Huawei
Email: yingzhen.qu@huawei.com Email: yingzhen.qu@huawei.com
Pushpasis Sarkar Pushpasis Sarkar
Individual Individual
Email: pushpasis.ietf@gmail.com Email: pushpasis.ietf@gmail.com
Ing-Wher Chen Ing-Wher Chen
Jabil The MITRE Corporation
Email: ingwherchen@mitre.org
Email: ing-wher_chen@jabil.com
Jeff Tantsura Jeff Tantsura
Individual Individual
Email: jefftant.ietf@gmail.com Email: jefftant.ietf@gmail.com
 End of changes. 46 change blocks. 
82 lines changed or deleted 111 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/