< draft-ietf-netmod-rfc8022bis-09.txt   draft-ietf-netmod-rfc8022bis-10.txt >
NETMOD Working Group L. Lhotka NETMOD Working Group L. Lhotka
Internet-Draft CZ.NIC Internet-Draft CZ.NIC
Obsoletes: 8022 (if approved) A. Lindem Obsoletes: 8022 (if approved) A. Lindem
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: July 21, 2018 Y. Qu Expires: July 29, 2018 Y. Qu
Huawei Huawei
January 17, 2018 January 25, 2018
A YANG Data Model for Routing Management (NDMA Version) A YANG Data Model for Routing Management (NMDA Version)
draft-ietf-netmod-rfc8022bis-09 draft-ietf-netmod-rfc8022bis-10
Abstract Abstract
This document contains a specification of three YANG modules and one This document contains a specification of three YANG modules and one
submodule. Together they form the core routing data model that submodule. Together they form the core routing data model that
serves as a framework for configuring and managing a routing serves as a framework for configuring and managing a routing
subsystem. It is expected that these modules will be augmented by subsystem. It is expected that these modules will be augmented by
additional YANG modules defining data models for control-plane additional YANG modules defining data models for control-plane
protocols, route filters, and other functions. The core routing data protocols, route filters, and other functions. The core routing data
model provides common building blocks for such extensions -- routes, model provides common building blocks for such extensions -- routes,
skipping to change at page 1, line 43 skipping to change at page 1, line 43
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 July 21, 2018. This Internet-Draft will expire on July 29, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 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
skipping to change at page 3, line 41 skipping to change at page 3, line 41
model will be augmented by numerous modules developed by various IETF model will be augmented by numerous modules developed by various IETF
working groups. working groups.
The YANG modules in this document conform to the Network Management The YANG modules in this document conform to the Network Management
Datastore Architecture (NMDA) [I-D.ietf-netmod-revised-datastores]. Datastore Architecture (NMDA) [I-D.ietf-netmod-revised-datastores].
This document obsoletes RFC 8022 [RFC8022]. This document obsoletes RFC 8022 [RFC8022].
2. Terminology and Notation 2. Terminology and Notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in [RFC2119]. "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.
The following terms are defined in The following terms are defined in
[I-D.ietf-netmod-revised-datastores]: [I-D.ietf-netmod-revised-datastores]:
o client o client
o server o server
o configuration o configuration
o system state o system state
o operational state o operational state
o intended configuration o intended configuration
The following terms are defined in [RFC7950]: The following terms are defined in [RFC7950]:
o action o action
skipping to change at page 13, line 32 skipping to change at page 13, line 32
In addition, the "ietf-ip" module allows for configuring IPv4 and In addition, the "ietf-ip" module allows for configuring IPv4 and
IPv6 addresses and network prefixes or masks on network-layer IPv6 addresses and network prefixes or masks on network-layer
interfaces. Configuration of these parameters on an enabled interfaces. Configuration of these parameters on an enabled
interface MUST result in an immediate creation of the corresponding interface MUST result in an immediate creation of the corresponding
direct route. The destination prefix of this route is set according direct route. The destination prefix of this route is set according
to the configured IP address and network prefix/mask, and the to the configured IP address and network prefix/mask, and the
interface is set as the outgoing interface for that route. interface is set as the outgoing interface for that route.
7. Routing Management YANG Module 7. Routing Management YANG Module
<CODE BEGINS> file "ietf-routing@2018-01-07.yang" <CODE BEGINS> file "ietf-routing@2018-01-25.yang"
module ietf-routing { module ietf-routing {
yang-version "1.1"; yang-version "1.1";
namespace "urn:ietf:params:xml:ns:yang:ietf-routing"; namespace "urn:ietf:params:xml:ns:yang:ietf-routing";
prefix "rt"; prefix "rt";
import ietf-yang-types { import ietf-yang-types {
prefix "yang"; prefix "yang";
} }
import ietf-interfaces { import ietf-interfaces {
prefix "if"; prefix "if";
description description
"A Network Management Datastore Architecture (NDMA) "A Network Management Datastore Architecture (NMDA)
compatible version of the ietf-interfaces module compatible version of the ietf-interfaces module
is required."; is required.";
} }
organization organization
"IETF NETMOD - Networking Modeling Working Group"; "IETF NETMOD - Networking Modeling Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/netmod/> "WG Web: <http://tools.ietf.org/wg/netmod/>
WG List: <mailto:rtgwg@ietf.org> WG List: <mailto:rtgwg@ietf.org>
skipping to change at page 14, line 35 skipping to change at page 14, line 35
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; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
reference "RFC XXXX"; reference "RFC XXXX";
revision 2018-01-07 { revision 2018-01-25 {
description description
"Network Management Datastore Architecture (NDMA) Revision"; "Network Management Datastore Architecture (NMDA) Revision";
reference reference
"RFC XXXX: A YANG Data Model for Routing Management "RFC XXXX: A YANG Data Model for Routing Management
(NDMA Version)"; (NMDA Version)";
} }
revision 2016-11-04 { revision 2016-11-04 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC 8022: A YANG Data Model for Routing Management"; "RFC 8022: A YANG Data Model for Routing Management";
} }
/* Features */ /* Features */
skipping to change at page 27, line 48 skipping to change at page 27, line 48
} }
} }
} }
} }
} }
} }
<CODE ENDS> <CODE ENDS>
8. IPv4 Unicast Routing Management YANG Module 8. IPv4 Unicast Routing Management YANG Module
<CODE BEGINS> file "ietf-ipv4-unicast-routing@2018-01-07.yang" <CODE BEGINS> file "ietf-ipv4-unicast-routing@2018-01-25.yang"
module ietf-ipv4-unicast-routing { module ietf-ipv4-unicast-routing {
yang-version "1.1"; yang-version "1.1";
namespace namespace
"urn:ietf:params:xml:ns:yang:ietf-ipv4-unicast-routing"; "urn:ietf:params:xml:ns:yang:ietf-ipv4-unicast-routing";
prefix "v4ur"; prefix "v4ur";
import ietf-routing { import ietf-routing {
prefix "rt"; prefix "rt";
description description
"A Network Management Datastore Architecture (NDMA) "A Network Management Datastore Architecture (NMDA)
compatible version of the ietf-routing module compatible version of the ietf-routing module
is required."; is required.";
} }
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix "inet";
} }
organization organization
"IETF NETMOD - Networking Modeling Working Group"; "IETF NETMOD - Networking Modeling Working Group";
contact contact
skipping to change at page 28, line 50 skipping to change at page 28, line 50
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; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
reference "RFC XXXX"; reference "RFC XXXX";
revision 2018-01-07 { revision 2018-01-25 {
description description
"Network Management Datastore Architecture (NDMA) Revision"; "Network Management Datastore Architecture (NMDA) Revision";
reference reference
"RFC XXXX: A YANG Data Model for Routing Management "RFC XXXX: A YANG Data Model for Routing Management
(NDMA Version)"; (NMDA Version)";
} }
revision 2016-11-04 { revision 2016-11-04 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC 8022: A YANG Data Model for Routing Management"; "RFC 8022: A YANG Data Model for Routing Management";
} }
/* Identities */ /* Identities */
skipping to change at page 35, line 47 skipping to change at page 35, line 47
status obsolete; status obsolete;
description description
"IPv4 address of the next hop."; "IPv4 address of the next hop.";
} }
} }
} }
<CODE ENDS> <CODE ENDS>
9. IPv6 Unicast Routing Management YANG Module 9. IPv6 Unicast Routing Management YANG Module
<CODE BEGINS> file "ietf-ipv6-unicast-routing@2018-01-07.yang" <CODE BEGINS> file "ietf-ipv6-unicast-routing@2018-01-25.yang"
module ietf-ipv6-unicast-routing { module ietf-ipv6-unicast-routing {
yang-version "1.1"; yang-version "1.1";
namespace namespace
"urn:ietf:params:xml:ns:yang:ietf-ipv6-unicast-routing"; "urn:ietf:params:xml:ns:yang:ietf-ipv6-unicast-routing";
prefix "v6ur"; prefix "v6ur";
import ietf-routing { import ietf-routing {
prefix "rt"; prefix "rt";
description description
"A Network Management Datastore Architecture (NDMA) "A Network Management Datastore Architecture (NMDA)
compatible version of the ietf-routing module compatible version of the ietf-routing module
is required."; is required.";
} }
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix "inet";
description description
"A Network Management Datastore Architecture (NDMA) "A Network Management Datastore Architecture (NMDA)
compatible version of the ietf-interfaces module compatible version of the ietf-interfaces module
is required."; is required.";
} }
include ietf-ipv6-router-advertisements { include ietf-ipv6-router-advertisements {
revision-date 2018-01-07; revision-date 2018-01-25;
} }
organization organization
"IETF NETMOD - Networking Modeling Working Group"; "IETF NETMOD - Networking Modeling Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/netmod/> "WG Web: <http://tools.ietf.org/wg/netmod/>
WG List: <mailto:rtgwg@ietf.org> WG List: <mailto:rtgwg@ietf.org>
Editor: Ladislav Lhotka Editor: Ladislav Lhotka
<mailto:lhotka@nic.cz> <mailto:lhotka@nic.cz>
skipping to change at page 37, line 10 skipping to change at page 37, line 10
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; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
reference "RFC XXXX"; reference "RFC XXXX";
revision 2018-01-07 { revision 2018-01-25 {
description description
"Network Management Datastore Architecture (NDMA) revision"; "Network Management Datastore Architecture (NMDA) revision";
reference reference
"RFC XXXX: A YANG Data Model for Routing Management "RFC XXXX: A YANG Data Model for Routing Management
(NDMA Version)"; (NMDA Version)";
} }
/* Identities */ /* Identities */
revision 2016-11-04 { revision 2016-11-04 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC 8022: A YANG Data Model for Routing Management"; "RFC 8022: A YANG Data Model for Routing Management";
} }
skipping to change at page 44, line 10 skipping to change at page 44, line 10
description description
"IPv6 address of the next hop."; "IPv6 address of the next hop.";
} }
} }
} }
<CODE ENDS> <CODE ENDS>
9.1. IPv6 Router Advertisements Submodule 9.1. IPv6 Router Advertisements Submodule
<CODE BEGINS> file "ietf-ipv6-router-advertisements@2018-01-07.yang" <CODE BEGINS> file "ietf-ipv6-router-advertisements@2018-01-25.yang"
submodule ietf-ipv6-router-advertisements { submodule ietf-ipv6-router-advertisements {
yang-version "1.1"; yang-version "1.1";
belongs-to ietf-ipv6-unicast-routing { belongs-to ietf-ipv6-unicast-routing {
prefix "v6ur"; prefix "v6ur";
} }
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix "inet";
} }
import ietf-interfaces { import ietf-interfaces {
prefix "if"; prefix "if";
description description
"A Network Management Datastore Architecture (NDMA) "A Network Management Datastore Architecture (NMDA)
compatible version of the ietf-interfaces module compatible version of the ietf-interfaces module
is required."; is required.";
} }
import ietf-ip { import ietf-ip {
prefix "ip"; prefix "ip";
description description
"A Network Management Datastore Architecture (NDMA) "A Network Management Datastore Architecture (NMDA)
compatible version of the ietf-ip module is compatible version of the ietf-ip module is
required."; required.";
} }
organization organization
"IETF NETMOD (NETCONF Data Modeling Language) Working Group"; "IETF NETMOD (NETCONF Data Modeling Language) Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/netmod/> "WG Web: <http://tools.ietf.org/wg/netmod/>
WG List: <mailto:rtgwg@ietf.org> WG List: <mailto:rtgwg@ietf.org>
skipping to change at page 45, line 23 skipping to change at page 45, line 23
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; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
reference reference
"RFC 4861: Neighbor Discovery for IP version 6 (IPv6)."; "RFC 4861: Neighbor Discovery for IP version 6 (IPv6).";
revision 2018-01-07 { revision 2018-01-25 {
description description
"Network Management Datastore Architecture (NDMA) Revision"; "Network Management Datastore Architecture (NMDA) Revision";
reference reference
"RFC XXXX: A YANG Data Model for Routing Management "RFC XXXX: A YANG Data Model for Routing Management
(NDMA Version)"; (NMDA Version)";
} }
revision 2016-11-04 { revision 2016-11-04 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC 8022: A YANG Data Model for Routing Management"; "RFC 8022: A YANG Data Model for Routing Management";
} }
augment "/if:interfaces/if:interface/ip:ipv6" { augment "/if:interfaces/if:interface/ip:ipv6" {
skipping to change at page 46, line 11 skipping to change at page 46, line 11
"A flag indicating whether or not the router sends "A flag indicating whether or not the router sends
periodic Router Advertisements and responds to periodic Router Advertisements and responds to
Router Solicitations."; Router Solicitations.";
reference reference
"RFC 4861: Neighbor Discovery for IP version 6 (IPv6) - "RFC 4861: Neighbor Discovery for IP version 6 (IPv6) -
AdvSendAdvertisements."; AdvSendAdvertisements.";
} }
leaf max-rtr-adv-interval { leaf max-rtr-adv-interval {
type uint16 { type uint16 {
range "4..1800"; range "4..65535";
} }
units "seconds"; units "seconds";
default "600"; default "600";
description description
"The maximum time allowed between sending unsolicited "The maximum time allowed between sending unsolicited
multicast Router Advertisements from the interface."; multicast Router Advertisements from the interface.";
reference reference
"RFC 4861: Neighbor Discovery for IP version 6 (IPv6) - "RFC 4861: Neighbor Discovery for IP version 6 (IPv6) -
MaxRtrAdvInterval."; MaxRtrAdvInterval.";
} }
skipping to change at page 48, line 28 skipping to change at page 48, line 28
was in effect at the time of implementation."; was in effect at the time of implementation.";
reference reference
"RFC 4861: Neighbor Discovery for IP version 6 (IPv6) - "RFC 4861: Neighbor Discovery for IP version 6 (IPv6) -
AdvCurHopLimit. AdvCurHopLimit.
IANA: IP Parameters, IANA: IP Parameters,
http://www.iana.org/assignments/ip-parameters"; http://www.iana.org/assignments/ip-parameters";
} }
leaf default-lifetime { leaf default-lifetime {
type uint16 { type uint16 {
range "0..9000"; range "0..65535";
} }
units "seconds"; units "seconds";
description description
"The value to be placed in the Router Lifetime field of "The value to be placed in the Router Lifetime field of
Router Advertisements sent from the interface, in Router Advertisements sent from the interface, in
seconds. It MUST be either zero or between seconds. It MUST be either zero or between
max-rtr-adv-interval and 9000 seconds. A value of zero max-rtr-adv-interval and 9000 seconds. A value of zero
default indicates that the router is not to be used as default indicates that the router is not to be used as
a router. These limits may be overridden by specific a router. These limits may be overridden by specific
documents that describe how IPv6 operates over documents that describe how IPv6 operates over
skipping to change at page 57, line 25 skipping to change at page 57, line 25
Protocol (NETCONF) Access Control Model", RFC 6536, Protocol (NETCONF) Access Control Model", RFC 6536,
DOI 10.17487/RFC6536, March 2012, <https://www.rfc- DOI 10.17487/RFC6536, March 2012, <https://www.rfc-
editor.org/info/rfc6536>. 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>.
[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-01 (work in Management", draft-ietf-netmod-rfc7223bis-03 (work in
progress), December 2017. progress), January 2018.
[I-D.ietf-netmod-rfc7277bis] [I-D.ietf-netmod-rfc7277bis]
Bjorklund, M., "A YANG Data Model for IP Management", Bjorklund, M., "A YANG Data Model for IP Management",
draft-ietf-netmod-rfc7277bis-01 (work in progress), draft-ietf-netmod-rfc7277bis-03 (work in progress),
December 2017. January 2018.
[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>.
[RFC8022] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing [RFC8022] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing
Management", RFC 8022, DOI 10.17487/RFC8022, November Management", RFC 8022, DOI 10.17487/RFC8022, November
2016, <https://www.rfc-editor.org/info/rfc8022>. 2016, <https://www.rfc-editor.org/info/rfc8022>.
[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
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[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-09 Architecture", draft-ietf-netmod-revised-datastores-10
(work in progress), December 2017. (work in progress), January 2018.
12.2. Informative References 12.2. Informative References
[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-15 Data Model Documents", draft-ietf-netmod-rfc6087bis-16
(work in progress), December 2017. (work in progress), January 2018.
[RFC7895] Bierman, A., Bjorklund, M., and K. Watsen, "YANG Module [RFC7895] Bierman, A., Bjorklund, M., and K. Watsen, "YANG Module
Library", RFC 7895, DOI 10.17487/RFC7895, June 2016, Library", RFC 7895, DOI 10.17487/RFC7895, June 2016,
<https://www.rfc-editor.org/info/rfc7895>. <https://www.rfc-editor.org/info/rfc7895>.
[RFC7951] Lhotka, L., "JSON Encoding of Data Modeled with YANG", [RFC7951] Lhotka, L., "JSON Encoding of Data Modeled with YANG",
RFC 7951, DOI 10.17487/RFC7951, August 2016, RFC 7951, DOI 10.17487/RFC7951, August 2016,
<https://www.rfc-editor.org/info/rfc7951>. <https://www.rfc-editor.org/info/rfc7951>.
[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-04 (work in progress), ietf-netmod-yang-tree-diagrams-05 (work in progress),
December 2017. January 2018.
Appendix A. The Complete Schema Tree Appendix A. The Complete Schema Tree
This appendix presents the complete tree of the core routing data This appendix presents the complete tree of the core routing data
model. See Section 2.2 for an explanation of the symbols used. The model. See Section 2.2 for an explanation of the symbols used. The
data type of every leaf node is shown near the right end of the data type of every leaf node is shown near the right end of the
corresponding line. corresponding line.
module: ietf-routing module: ietf-routing
+--rw routing +--rw routing
skipping to change at page 67, line 33 skipping to change at page 67, line 33
operational state, in the JSON encoding [RFC7951]. The data conforms operational state, in the JSON encoding [RFC7951]. The data conforms
to a data model that is defined by the following YANG library to a data model that is defined by the following YANG library
specification [RFC7895]: specification [RFC7895]:
{ {
"ietf-yang-library:modules-state": { "ietf-yang-library:modules-state": {
"module-set-id": "c2e1f54169aa7f36e1a6e8d0865d441d3600f9c4", "module-set-id": "c2e1f54169aa7f36e1a6e8d0865d441d3600f9c4",
"module": [ "module": [
{ {
"name": "ietf-routing", "name": "ietf-routing",
"revision": "2018-01-07", "revision": "2018-01-25",
"feature": [ "feature": [
"multiple-ribs", "multiple-ribs",
"router-id" "router-id"
], ],
"namespace": "urn:ietf:params:xml:ns:yang:ietf-routing", "namespace": "urn:ietf:params:xml:ns:yang:ietf-routing",
"conformance-type": "implement" "conformance-type": "implement"
}, },
{ {
"name": "ietf-ipv4-unicast-routing", "name": "ietf-ipv4-unicast-routing",
"revision": "2018-01-07", "revision": "2018-01-25",
"namespace": "namespace":
"urn:ietf:params:xml:ns:yang:ietf-ipv4-unicast-routing", "urn:ietf:params:xml:ns:yang:ietf-ipv4-unicast-routing",
"conformance-type": "implement" "conformance-type": "implement"
}, },
{ {
"name": "ietf-ipv6-unicast-routing", "name": "ietf-ipv6-unicast-routing",
"revision": "2018-01-07", "revision": "2018-01-25",
"namespace": "namespace":
"urn:ietf:params:xml:ns:yang:ietf-ipv6-unicast-routing", "urn:ietf:params:xml:ns:yang:ietf-ipv6-unicast-routing",
"conformance-type": "implement", "conformance-type": "implement",
"submodule": [ "submodule": [
{ {
"name": "ietf-ipv6-router-advertisements", "name": "ietf-ipv6-router-advertisements",
"revision": "2018-01-07" "revision": "2018-01-25"
} }
] ]
}, },
{ {
"name": "ietf-interfaces", "name": "ietf-interfaces",
"revision": "2017-12-16", "revision": "2017-12-16",
"namespace": "urn:ietf:params:xml:ns:yang:ietf-interfaces", "namespace": "urn:ietf:params:xml:ns:yang:ietf-interfaces",
"conformance-type": "implement" "conformance-type": "implement"
}, },
{ {
skipping to change at page 76, line 40 skipping to change at page 76, line 40
</rpc-reply> </rpc-reply>
Acknowledgments Acknowledgments
The authors wish to thank Nitin Bahadur, Martin Bjorklund, Dean The authors wish to thank Nitin Bahadur, Martin Bjorklund, Dean
Bogdanovic, Jeff Haas, Joel Halpern, Wes Hardaker, Sriganesh Kini, Bogdanovic, Jeff Haas, Joel Halpern, Wes Hardaker, Sriganesh Kini,
David Lamparter, Andrew McGregor, Jan Medved, Xiang Li, Stephane David Lamparter, Andrew McGregor, Jan Medved, Xiang Li, Stephane
Litkowski, Thomas Morin, Tom Petch, Bruno Rijsman, Litkowski, Thomas Morin, Tom Petch, Bruno Rijsman,
Juergen Schoenwaelder, Phil Shafer, Dave Thaler, Yi Yang, Juergen Schoenwaelder, Phil Shafer, Dave Thaler, Yi Yang,
Derek Man-Kit Yeung, Jeffrey Zhang, Vladimir Vassilev, Rob Wilton, Derek Man-Kit Yeung, Jeffrey Zhang, Vladimir Vassilev, Rob Wilton,
Joe Clark, and Jia He for their helpful comments and suggestions. Joe Clark, Jia He, and Suresh Krishnan for their helpful comments and
suggestions.
Authors' Addresses Authors' Addresses
Ladislav Lhotka Ladislav Lhotka
CZ.NIC CZ.NIC
EMail: lhotka@nic.cz EMail: lhotka@nic.cz
Acee Lindem Acee Lindem
Cisco Systems Cisco Systems
 End of changes. 43 change blocks. 
48 lines changed or deleted 55 lines changed or added

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