draft-ietf-rtgwg-yang-rib-extend-00.txt   draft-ietf-rtgwg-yang-rib-extend-01.txt 
Network Working Group A. Lindem Network Working Group A. Lindem
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Standards Track Y. Qu Intended status: Standards Track Y. Qu
Expires: September 6, 2019 Huawei Expires: September 11, 2019 Huawei
March 5, 2019 March 10, 2019
RIB YANG Data Model RIB YANG Data Model
draft-ietf-rtgwg-yang-rib-extend-00.txt draft-ietf-rtgwg-yang-rib-extend-01.txt
Abstract Abstract
The Routing Information Base (RIB) is a list of routes and their The Routing Information Base (RIB) is a list of routes and their
corresponding administrative data and operational state. corresponding administrative data and operational state.
RFC 8349 defines the basic building blocks for RIB, and this model RFC 8349 defines the basic building blocks for RIB, and this model
augments it to support multiple next-hops (aka, paths) for each route augments it to support multiple next-hops (aka, paths) for each route
as well as additional attributes. as well as additional attributes.
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 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 September 6, 2019. This Internet-Draft will expire on September 11, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 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 (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
skipping to change at page 2, line 24 skipping to change at page 2, line 24
3. Design of the Model . . . . . . . . . . . . . . . . . . . . . 4 3. Design of the Model . . . . . . . . . . . . . . . . . . . . . 4
3.1. RIB Tags and Preference . . . . . . . . . . . . . . . . . 5 3.1. RIB Tags and Preference . . . . . . . . . . . . . . . . . 5
3.2. Multiple next-hops . . . . . . . . . . . . . . . . . . . 5 3.2. Multiple next-hops . . . . . . . . . . . . . . . . . . . 5
3.3. Repair path . . . . . . . . . . . . . . . . . . . . . . . 5 3.3. Repair path . . . . . . . . . . . . . . . . . . . . . . . 5
4. RIB Model Tree . . . . . . . . . . . . . . . . . . . . . . . 5 4. RIB Model Tree . . . . . . . . . . . . . . . . . . . . . . . 5
5. RIB YANG Model . . . . . . . . . . . . . . . . . . . . . . . 7 5. RIB YANG Model . . . . . . . . . . . . . . . . . . . . . . . 7
6. Security Considerations . . . . . . . . . . . . . . . . . . . 14 6. Security Considerations . . . . . . . . . . . . . . . . . . . 14
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
8.1. Normative References . . . . . . . . . . . . . . . . . . 15 8.1. Normative References . . . . . . . . . . . . . . . . . . 15
8.2. Informative References . . . . . . . . . . . . . . . . . 16 8.2. Informative References . . . . . . . . . . . . . . . . . 17
Appendix A. Combined Tree Diagram . . . . . . . . . . . . . . . 17 Appendix A. Combined Tree Diagram . . . . . . . . . . . . . . . 17
Appendix B. ietf-rib-extension.yang examples . . . . . . . . . . 20 Appendix B. ietf-rib-extension.yang examples . . . . . . . . . . 20
Appendix C. Acknowledgments . . . . . . . . . . . . . . . . . . 20 Appendix C. Acknowledgments . . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21
1. Introduction 1. Introduction
This document defines a YANG, [RFC6020][RFC7950], data model which This document defines a YANG, [RFC6020][RFC7950], data model which
extends the generic data model for RIB by augmenting the ietf-routing extends the generic data model for RIB by augmenting the ietf-routing
model as defined in [RFC8349]. model as defined in [RFC8349].
RIB is a collection of best routes from all routing protocols. RIB is a collection of best routes from all routing protocols.
Within a protocol routes are selected based on the metrics in use by Within a protocol routes are selected based on the metrics in use by
that protocol, and the protocol install its best routes to RIB. RIB that protocol, and the protocol install its best routes to RIB. RIB
skipping to change at page 5, line 24 skipping to change at page 5, line 24
have been augmented with a multi-next-hop option. have been augmented with a multi-next-hop option.
A static route/prefix can be configured to have multiple next-hops, A static route/prefix can be configured to have multiple next-hops,
each with their own tag and route preference. each with their own tag and route preference.
In RIB, a route may have multiple next-hops. They can be either In RIB, a route may have multiple next-hops. They can be either
equal cost multiple paths (ECMP), or they may have different metrics. equal cost multiple paths (ECMP), or they may have different metrics.
3.3. Repair path 3.3. Repair path
The loop-free alternate (LFA) Fast Reroute (FRR) pre-computes repair The IP Fast Reroute (IPFRR) pre-computes repair paths by routing
paths by routing protocols, and RIB stores the best repair path. protocols [RFC5714], and the best repair path is installed in RIB.
A repair path is augmented in RIB operation state for each path. A repair path is augmented in RIB operation state for each path.
4. RIB Model Tree 4. RIB Model Tree
The tree associated with the "ietf-rib-extension" module follows. The tree associated with the "ietf-rib-extension" module follows.
The meaning of the symbols can be found in [RFC8340]. The ietf- The meaning of the symbols can be found in [RFC8340]. The ietf-
routing.yang tree with the augmentations herein is included in routing.yang tree with the augmentations herein is included in
Appendix A. Appendix A.
skipping to change at page 7, line 7 skipping to change at page 7, line 7
+--ro repair-path? +--ro repair-path?
-> /rt:routing/ribs/rib/routes/repair-route/id -> /rt:routing/ribs/rib/routes/repair-route/id
augment /rt:routing/rt:ribs/rt:rib/rt:routes/rt:route augment /rt:routing/rt:ribs/rt:rib/rt:routes/rt:route
/rt:next-hop/rt:next-hop-options/rt:next-hop-list /rt:next-hop/rt:next-hop-options/rt:next-hop-list
/rt:next-hop-list/rt:next-hop: /rt:next-hop-list/rt:next-hop:
+--ro repair-path? +--ro repair-path?
-> /rt:routing/ribs/rib/routes/repair-route/id -> /rt:routing/ribs/rib/routes/repair-route/id
5. RIB YANG Model 5. RIB YANG Model
<CODE BEGINS> file "ietf-rib-extension@2019-03-01.yang" <CODE BEGINS>
module ietf-rib-extension { module ietf-rib-extension {
yang-version "1.1"; yang-version "1.1";
namespace "urn:ietf:params:xml:ns:yang:ietf-rib-extension"; namespace "urn:ietf:params:xml:ns:yang:ietf-rib-extension";
prefix rib-ext; prefix rib-ext;
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix "inet";
} }
skipping to change at page 7, line 35 skipping to change at page 7, line 35
import ietf-ipv4-unicast-routing { import ietf-ipv4-unicast-routing {
prefix "v4ur"; prefix "v4ur";
} }
import ietf-ipv6-unicast-routing { import ietf-ipv6-unicast-routing {
prefix "v6ur"; prefix "v6ur";
} }
organization organization
"IETF RTGWG - Routing Working Group"; "IETF RTGWG - Routing Working Group";
contact contact
"WG Web: <http://datatracker.ietf.org/group/rtgwg/> "WG Web: <http://datatracker.ietf.org/group/rtgwg/>
WG List: <mailto:rtgwg@ietf.org> WG List: <mailto:rtgwg@ietf.org>
Author: Acee Lindem Author: Acee Lindem
<mailto:acee@cisco.com> <mailto:acee@cisco.com>
Author: Yingzhen Qu Author: Yingzhen Qu
<mailto:yingzhen.qu@huawei.com>"; <mailto:yingzhen.qu@huawei.com>";
description description
"This YANG module extends the generic data model for "This YANG module extends the generic data model for
RIB by augmenting the ietf-netmod-routing-cfg RIB by augmenting the ietf-netmod-routing-cfg
model. It is intended that the module will be extended model. It is intended that the module will be extended
by vendors to define vendor-specific RIB parameters. by vendors to define vendor-specific RIB parameters.
This YANG model conforms to the Network Management This YANG model conforms to the Network Management
Datastore Architecture (NDMA) as described in RFC 8342. Datastore Architecture (NDMA) as described in RFC 8242.
Copyright (c) 2018 IETF Trust and the persons identified as Copyright (c) 2018 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
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 XXXX; This version of this YANG module is part of RFC XXXX;
see the RFC itself for full legal notices."; see the RFC itself for full legal notices.";
revision 2019-03-01 { revision 2019-03-11 {
description description
"Initial RFC Version"; "Initial RFC Version";
reference reference
"RFC XXXX: A YANG Data Model for RIB Extensions."; "RFC XXXX: A YANG Data Model for RIB Extensions.";
} }
/* Groupings */ /* Groupings */
grouping rib-statistics { grouping rib-statistics {
description "Statistics grouping used for RIB augmentation"; description "Statistics grouping used for RIB augmentation";
container rib-summary-statistics { container rib-summary-statistics {
skipping to change at page 10, line 8 skipping to change at page 10, line 8
type uint32; type uint32;
description "Route metric"; description "Route metric";
} }
leaf tag { leaf tag {
type uint32; type uint32;
description "Route tag"; description "Route tag";
} }
leaf application-tag { leaf application-tag {
type uint32; type uint32;
description "Additional Application-Specific Route tag"; description "Additional Application-Specific Route tag. This
additional tag can be used by applications that
require semantics and policy different from that
of the tag. For example, the tag is usually
automatically advertised in OSPF AS-External
Link State Advertisements (LSAs) while this
application specific tag is not unless done so
explicitly.";
} }
} }
grouping path-attribute { grouping path-attribute {
description description
"Path attribute grouping"; "Path attribute grouping";
leaf repair-path { leaf repair-path {
type leafref { type leafref {
path "/rt:routing/rt:ribs/rt:rib/" path "/rt:routing/rt:ribs/rt:rib/"
+ "rt:routes/repair-route/id"; + "rt:routes/repair-route/id";
} }
description description
"IP Fast ReRoute (IPFRR) repair path, use a path "IP Fast ReRoute (IPFRR) repair path, use a path
from repair-route list"; from repair-route list";
reference
"RFC 5714: IP Fast Reroute Framework.";
} }
} }
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rt:static-routes/v4ur:ipv4/" + "rt:control-plane-protocol/rt:static-routes/v4ur:ipv4/"
+ "v4ur:route/v4ur:next-hop/v4ur:next-hop-options/" + "v4ur:route/v4ur:next-hop/v4ur:next-hop-options/"
+ "v4ur:simple-next-hop" + "v4ur:simple-next-hop"
{ {
description description
"Augment 'simple-next-hop' case in IPv4 unicast route."; "Augment 'simple-next-hop' case in IPv4 unicast route.";
leaf preference { leaf preference {
type uint32; type uint32;
default "1"; default "1";
description "Route preference - Used to select among multiple description "Route preference - Used to select among multiple
static routes with a lower preference next-hop static routes with a lower preference next-hop
preferred and equal preference paths yielding preferred and equal preference paths yielding
Equal Cost Multi-Path (ECMP)."; Equal Cost Multi-Path (ECMP).";
} }
leaf tag { leaf tag {
type uint32; type uint32;
default "0"; default "0";
description "Route tag"; description "Route tag";
}
leaf application-tag {
type uint32;
description "Additional Application-Specific Route tag";
} }
} }
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rt:static-routes/v4ur:ipv4/" + "rt:control-plane-protocol/rt:static-routes/v4ur:ipv4/"
+ "v4ur:route/v4ur:next-hop/v4ur:next-hop-options/" + "v4ur:route/v4ur:next-hop/v4ur:next-hop-options/"
+ "v4ur:next-hop-list/v4ur:next-hop-list/v4ur:next-hop" + "v4ur:next-hop-list/v4ur:next-hop-list/v4ur:next-hop"
{ {
description description
"Augment static route configuration 'next-hop-list'."; "Augment static route configuration 'next-hop-list'.";
leaf preference { leaf preference {
type uint32; type uint32;
default "1"; default "1";
description "Route preference - Used to select among multiple description "Route preference - Used to select among multiple
static routes with a lower preference next-hop static routes with a lower preference next-hop
preferred and equal preference paths yielding preferred and equal preference paths yielding
Equal Cost Multi-Path (ECMP)."; Equal Cost Multi-Path (ECMP).";
} }
leaf tag { leaf tag {
type uint32; type uint32;
default "0"; default "0";
description "Route tag"; description "Route tag";
} }
leaf application-tag { }
type uint32;
description "Additional Application-Specific Route tag";
}
}
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rt:static-routes/v6ur:ipv6/" + "rt:control-plane-protocol/rt:static-routes/v6ur:ipv6/"
+ "v6ur:route/v6ur:next-hop/v6ur:next-hop-options/" + "v6ur:route/v6ur:next-hop/v6ur:next-hop-options/"
+ "v6ur:simple-next-hop" + "v6ur:simple-next-hop"
{ {
description description
"Augment 'simple-next-hop' case in IPv6 unicast route."; "Augment 'simple-next-hop' case in IPv6 unicast route.";
leaf preference { leaf preference {
type uint32; type uint32;
default "1"; default "1";
description "Route preference - Used to select among multiple description "Route preference - Used to select among multiple
static routes with a lower preference next-hop static routes with a lower preference next-hop
preferred and equal preference paths yielding preferred and equal preference paths yielding
Equal Cost Multi-Path (ECMP)."; Equal Cost Multi-Path (ECMP).";
} }
leaf tag { leaf tag {
type uint32; type uint32;
default "0"; default "0";
description "Route tag"; description "Route tag";
} }
leaf application-tag { }
type uint32;
description "Additional Application-Specific Route tag";
}
}
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rt:static-routes/v6ur:ipv6/" + "rt:control-plane-protocol/rt:static-routes/v6ur:ipv6/"
+ "v6ur:route/v6ur:next-hop/v6ur:next-hop-options/" + "v6ur:route/v6ur:next-hop/v6ur:next-hop-options/"
+ "v6ur:next-hop-list/v6ur:next-hop-list/v6ur:next-hop" + "v6ur:next-hop-list/v6ur:next-hop-list/v6ur:next-hop"
{ {
description description
"Augment static route configuration 'next-hop-list'."; "Augment static route configuration 'next-hop-list'.";
leaf preference { leaf preference {
type uint32; type uint32;
default "1"; default "1";
description "Route preference - Used to select among multiple description "Route preference - Used to select among multiple
static routes with a lower preference next-hop static routes with a lower preference next-hop
preferred and equal preference paths yielding preferred and equal preference paths yielding
Equal Cost Multi-Path (ECMP)."; Equal Cost Multi-Path (ECMP).";
} }
leaf tag { leaf tag {
type uint32; type uint32;
default "0"; default "0";
description "Route tag"; description "Route tag";
} }
leaf application-tag {
type uint32;
description "Additional Application-Specific Route tag";
}
} }
augment "/rt:routing/rt:ribs/rt:rib" augment "/rt:routing/rt:ribs/rt:rib"
{ {
description "Augment a RIB with statistics"; description "Augment a RIB with statistics";
uses rib-statistics; uses rib-statistics;
} }
augment "/rt:routing/rt:ribs/rt:rib/" augment "/rt:routing/rt:ribs/rt:rib/"
+ "rt:routes/rt:route" + "rt:routes/rt:route"
{ {
description description
"Augment a route in RIB with tag."; "Augment a route in RIB with tag.";
uses attributes; uses attributes;
} }
augment "/rt:routing/rt:ribs/rt:rib/" augment "/rt:routing/rt:ribs/rt:rib/"
+ "rt:routes" + "rt:routes"
{ {
description description
"Augment a route with a list of repair-paths."; "Augment a route with a list of repair-paths.";
list repair-route { list repair-route {
key "id"; key "id";
description description
"A repair-path entry, which can be referenced "A repair-path entry, which can be referenced
by a repair-path."; by a repair-path.";
leaf id { leaf id {
type string; type string;
description description
"A unique identifier."; "A unique identifier.";
} }
container next-hop { container next-hop {
description description
"Route's next-hop attribute."; "Route's next-hop attribute.";
leaf outgoing-interface { leaf outgoing-interface {
type if:interface-state-ref; type if:interface-state-ref;
description description
"Name of the outgoing interface."; "Name of the outgoing interface.";
} }
leaf next-hop-address { leaf next-hop-address {
type inet:ip-address; type inet:ip-address;
description description
"IP address of the next hop."; "IP address of the next hop.";
} }
} }
leaf metric { leaf metric {
type uint32; type uint32;
description "Route metric"; description "Route metric";
} }
} }
} }
augment "/rt:routing/rt:ribs/rt:rib/" augment "/rt:routing/rt:ribs/rt:rib/"
+ "rt:routes/rt:route/rt:next-hop/rt:next-hop-options/" + "rt:routes/rt:route/rt:next-hop/rt:next-hop-options/"
+ "rt:simple-next-hop" + "rt:simple-next-hop"
{ {
description description
"Add more parameters to a path."; "Add more parameters to a path.";
uses path-attribute; uses path-attribute;
} }
augment "/rt:routing/rt:ribs/rt:rib/" augment "/rt:routing/rt:ribs/rt:rib/"
+ "rt:routes/rt:route/rt:next-hop/rt:next-hop-options/" + "rt:routes/rt:route/rt:next-hop/rt:next-hop-options/"
+ "rt:special-next-hop" + "rt:special-next-hop"
{ {
description description
"Add more parameters to a path."; "Add more parameters to a path.";
uses path-attribute; uses path-attribute;
} }
augment "/rt:routing/rt:ribs/rt:rib/" augment "/rt:routing/rt:ribs/rt:rib/"
+ "rt:routes/rt:route/rt:next-hop/rt:next-hop-options/" + "rt:routes/rt:route/rt:next-hop/rt:next-hop-options/"
+ "rt:next-hop-list/rt:next-hop-list/rt:next-hop" + "rt:next-hop-list/rt:next-hop-list/rt:next-hop"
{ {
description description
"This case augments the 'next-hop-options' in the routing "This case augments the 'next-hop-options' in the routing
model."; model.";
uses path-attribute; uses path-attribute;
} }
} }
<CODE ENDS> <CODE ENDS>
6. Security Considerations 6. Security Considerations
skipping to change at page 15, line 32 skipping to change at page 15, line 29
name: ietf-acl namespace: urn:ietf:params:xml:ns:yang:ietf-rib- name: ietf-acl namespace: urn:ietf:params:xml:ns:yang:ietf-rib-
extension prefix: ietf-rib-ext reference: RFC XXXX extension prefix: ietf-rib-ext reference: RFC XXXX
8. References 8. References
8.1. Normative References 8.1. Normative References
[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-
<https://www.rfc-editor.org/info/rfc2119>. editor.org/info/rfc2119>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004, <https://www.rfc-
<https://www.rfc-editor.org/info/rfc3688>. editor.org/info/rfc3688>.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, (TLS) Protocol Version 1.2", RFC 5246,
DOI 10.17487/RFC5246, August 2008, DOI 10.17487/RFC5246, August 2008, <https://www.rfc-
<https://www.rfc-editor.org/info/rfc5246>. editor.org/info/rfc5246>.
[RFC5714] Shand, M. and S. Bryant, "IP Fast Reroute Framework",
RFC 5714, DOI 10.17487/RFC5714, January 2010,
<https://www.rfc-editor.org/info/rfc5714>.
[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, DOI 10.17487/RFC6020, October 2010, <https://www.rfc-
<https://www.rfc-editor.org/info/rfc6020>. editor.org/info/rfc6020>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<https://www.rfc-editor.org/info/rfc6242>. <https://www.rfc-editor.org/info/rfc6242>.
skipping to change at page 16, line 27 skipping to change at page 16, line 32
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/info/rfc8040>. <https://www.rfc-editor.org/info/rfc8040>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Model", STD 91, RFC 8341, Access Control Model", STD 91, RFC 8341,
DOI 10.17487/RFC8341, March 2018, DOI 10.17487/RFC8341, March 2018, <https://www.rfc-
<https://www.rfc-editor.org/info/rfc8341>. editor.org/info/rfc8341>.
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore Architecture and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
<https://www.rfc-editor.org/info/rfc8342>. <https://www.rfc-editor.org/info/rfc8342>.
[RFC8343] Bjorklund, M., "A YANG Data Model for Interface [RFC8343] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, Management", RFC 8343, DOI 10.17487/RFC8343, March 2018,
<https://www.rfc-editor.org/info/rfc8343>. <https://www.rfc-editor.org/info/rfc8343>.
[RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for
Routing Management (NMDA Version)", RFC 8349, Routing Management (NMDA Version)", RFC 8349,
DOI 10.17487/RFC8349, March 2018, DOI 10.17487/RFC8349, March 2018, <https://www.rfc-
<https://www.rfc-editor.org/info/rfc8349>. editor.org/info/rfc8349>.
8.2. Informative References 8.2. Informative References
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/info/rfc8340>. <https://www.rfc-editor.org/info/rfc8340>.
[XML-REGISTRY] [XML-REGISTRY]
Mealling, M., "The IETF XML Registry", BCP 81, January Mealling, M., "The IETF XML Registry", BCP 81, January
2004. 2004.
 End of changes. 37 change blocks. 
74 lines changed or deleted 69 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/