--- 1/draft-ietf-netmod-rfc8022bis-09.txt 2018-01-25 09:13:43.870114111 -0800 +++ 2/draft-ietf-netmod-rfc8022bis-10.txt 2018-01-25 09:13:44.010117424 -0800 @@ -1,21 +1,21 @@ NETMOD Working Group L. Lhotka Internet-Draft CZ.NIC Obsoletes: 8022 (if approved) A. Lindem Intended status: Standards Track Cisco Systems -Expires: July 21, 2018 Y. Qu +Expires: July 29, 2018 Y. Qu Huawei - January 17, 2018 + January 25, 2018 - A YANG Data Model for Routing Management (NDMA Version) - draft-ietf-netmod-rfc8022bis-09 + A YANG Data Model for Routing Management (NMDA Version) + draft-ietf-netmod-rfc8022bis-10 Abstract This document contains a specification of three YANG modules and one submodule. Together they form the core routing data model that serves as a framework for configuring and managing a routing subsystem. It is expected that these modules will be augmented by additional YANG modules defining data models for control-plane protocols, route filters, and other functions. The core routing data model provides common building blocks for such extensions -- routes, @@ -32,21 +32,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference 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 (c) 2018 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -122,31 +122,33 @@ model will be augmented by numerous modules developed by various IETF working groups. The YANG modules in this document conform to the Network Management Datastore Architecture (NMDA) [I-D.ietf-netmod-revised-datastores]. This document obsoletes RFC 8022 [RFC8022]. 2. Terminology and Notation 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]. + "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. The following terms are defined in [I-D.ietf-netmod-revised-datastores]: o client o server - o configuration + o system state o operational state o intended configuration The following terms are defined in [RFC7950]: o action @@ -570,34 +572,34 @@ In addition, the "ietf-ip" module allows for configuring IPv4 and IPv6 addresses and network prefixes or masks on network-layer interfaces. Configuration of these parameters on an enabled interface MUST result in an immediate creation of the corresponding direct route. The destination prefix of this route is set according to the configured IP address and network prefix/mask, and the interface is set as the outgoing interface for that route. 7. Routing Management YANG Module - file "ietf-routing@2018-01-07.yang" + file "ietf-routing@2018-01-25.yang" module ietf-routing { yang-version "1.1"; namespace "urn:ietf:params:xml:ns:yang:ietf-routing"; prefix "rt"; import ietf-yang-types { prefix "yang"; } import ietf-interfaces { prefix "if"; description - "A Network Management Datastore Architecture (NDMA) + "A Network Management Datastore Architecture (NMDA) compatible version of the ietf-interfaces module is required."; } organization "IETF NETMOD - Networking Modeling Working Group"; contact "WG Web: WG List: @@ -621,26 +623,26 @@ without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; reference "RFC XXXX"; - revision 2018-01-07 { + revision 2018-01-25 { description - "Network Management Datastore Architecture (NDMA) Revision"; + "Network Management Datastore Architecture (NMDA) Revision"; reference "RFC XXXX: A YANG Data Model for Routing Management - (NDMA Version)"; + (NMDA Version)"; } revision 2016-11-04 { description "Initial revision."; reference "RFC 8022: A YANG Data Model for Routing Management"; } /* Features */ @@ -1262,31 +1264,31 @@ } } } } } } 8. IPv4 Unicast Routing Management YANG Module - file "ietf-ipv4-unicast-routing@2018-01-07.yang" + file "ietf-ipv4-unicast-routing@2018-01-25.yang" module ietf-ipv4-unicast-routing { yang-version "1.1"; namespace "urn:ietf:params:xml:ns:yang:ietf-ipv4-unicast-routing"; prefix "v4ur"; import ietf-routing { prefix "rt"; description - "A Network Management Datastore Architecture (NDMA) + "A Network Management Datastore Architecture (NMDA) compatible version of the ietf-routing module is required."; } import ietf-inet-types { prefix "inet"; } organization "IETF NETMOD - Networking Modeling Working Group"; contact @@ -1312,26 +1314,26 @@ without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; reference "RFC XXXX"; - revision 2018-01-07 { + revision 2018-01-25 { description - "Network Management Datastore Architecture (NDMA) Revision"; + "Network Management Datastore Architecture (NMDA) Revision"; reference "RFC XXXX: A YANG Data Model for Routing Management - (NDMA Version)"; + (NMDA Version)"; } revision 2016-11-04 { description "Initial revision."; reference "RFC 8022: A YANG Data Model for Routing Management"; } /* Identities */ @@ -1647,46 +1649,46 @@ status obsolete; description "IPv4 address of the next hop."; } } } 9. IPv6 Unicast Routing Management YANG Module - file "ietf-ipv6-unicast-routing@2018-01-07.yang" + file "ietf-ipv6-unicast-routing@2018-01-25.yang" module ietf-ipv6-unicast-routing { yang-version "1.1"; namespace "urn:ietf:params:xml:ns:yang:ietf-ipv6-unicast-routing"; prefix "v6ur"; import ietf-routing { prefix "rt"; description - "A Network Management Datastore Architecture (NDMA) + "A Network Management Datastore Architecture (NMDA) compatible version of the ietf-routing module is required."; } import ietf-inet-types { prefix "inet"; description - "A Network Management Datastore Architecture (NDMA) + "A Network Management Datastore Architecture (NMDA) compatible version of the ietf-interfaces module is required."; } include ietf-ipv6-router-advertisements { - revision-date 2018-01-07; + revision-date 2018-01-25; } organization "IETF NETMOD - Networking Modeling Working Group"; contact "WG Web: WG List: Editor: Ladislav Lhotka @@ -1707,26 +1709,26 @@ without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; reference "RFC XXXX"; - revision 2018-01-07 { + revision 2018-01-25 { description - "Network Management Datastore Architecture (NDMA) revision"; + "Network Management Datastore Architecture (NMDA) revision"; reference "RFC XXXX: A YANG Data Model for Routing Management - (NDMA Version)"; + (NMDA Version)"; } /* Identities */ revision 2016-11-04 { description "Initial revision."; reference "RFC 8022: A YANG Data Model for Routing Management"; } @@ -2044,44 +2046,44 @@ description "IPv6 address of the next hop."; } } } 9.1. IPv6 Router Advertisements Submodule - file "ietf-ipv6-router-advertisements@2018-01-07.yang" + file "ietf-ipv6-router-advertisements@2018-01-25.yang" submodule ietf-ipv6-router-advertisements { yang-version "1.1"; belongs-to ietf-ipv6-unicast-routing { prefix "v6ur"; } import ietf-inet-types { prefix "inet"; } import ietf-interfaces { prefix "if"; description - "A Network Management Datastore Architecture (NDMA) + "A Network Management Datastore Architecture (NMDA) compatible version of the ietf-interfaces module is required."; } import ietf-ip { prefix "ip"; description - "A Network Management Datastore Architecture (NDMA) + "A Network Management Datastore Architecture (NMDA) compatible version of the ietf-ip module is required."; } organization "IETF NETMOD (NETCONF Data Modeling Language) Working Group"; contact "WG Web: WG List: @@ -2106,26 +2108,26 @@ to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; reference "RFC 4861: Neighbor Discovery for IP version 6 (IPv6)."; - revision 2018-01-07 { + revision 2018-01-25 { description - "Network Management Datastore Architecture (NDMA) Revision"; + "Network Management Datastore Architecture (NMDA) Revision"; reference "RFC XXXX: A YANG Data Model for Routing Management - (NDMA Version)"; + (NMDA Version)"; } revision 2016-11-04 { description "Initial revision."; reference "RFC 8022: A YANG Data Model for Routing Management"; } augment "/if:interfaces/if:interface/ip:ipv6" { @@ -2142,21 +2144,21 @@ "A flag indicating whether or not the router sends periodic Router Advertisements and responds to Router Solicitations."; reference "RFC 4861: Neighbor Discovery for IP version 6 (IPv6) - AdvSendAdvertisements."; } leaf max-rtr-adv-interval { type uint16 { - range "4..1800"; + range "4..65535"; } units "seconds"; default "600"; description "The maximum time allowed between sending unsolicited multicast Router Advertisements from the interface."; reference "RFC 4861: Neighbor Discovery for IP version 6 (IPv6) - MaxRtrAdvInterval."; } @@ -2256,21 +2258,21 @@ was in effect at the time of implementation."; reference "RFC 4861: Neighbor Discovery for IP version 6 (IPv6) - AdvCurHopLimit. IANA: IP Parameters, http://www.iana.org/assignments/ip-parameters"; } leaf default-lifetime { type uint16 { - range "0..9000"; + range "0..65535"; } units "seconds"; description "The value to be placed in the Router Lifetime field of Router Advertisements sent from the interface, in seconds. It MUST be either zero or between max-rtr-adv-interval and 9000 seconds. A value of zero default indicates that the router is not to be used as a router. These limits may be overridden by specific documents that describe how IPv6 operates over @@ -2681,65 +2683,69 @@ Protocol (NETCONF) Access Control Model", RFC 6536, DOI 10.17487/RFC6536, March 2012, . [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC 6991, DOI 10.17487/RFC6991, July 2013, . [I-D.ietf-netmod-rfc7223bis] Bjorklund, M., "A YANG Data Model for Interface - Management", draft-ietf-netmod-rfc7223bis-01 (work in - progress), December 2017. + Management", draft-ietf-netmod-rfc7223bis-03 (work in + progress), January 2018. [I-D.ietf-netmod-rfc7277bis] Bjorklund, M., "A YANG Data Model for IP Management", - draft-ietf-netmod-rfc7277bis-01 (work in progress), - December 2017. + draft-ietf-netmod-rfc7277bis-03 (work in progress), + January 2018. [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", RFC 7950, DOI 10.17487/RFC7950, August 2016, . [RFC8022] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing Management", RFC 8022, DOI 10.17487/RFC8022, November 2016, . [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, . + [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC + 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, + May 2017, . + [I-D.ietf-netmod-revised-datastores] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., and R. Wilton, "Network Management Datastore - Architecture", draft-ietf-netmod-revised-datastores-09 - (work in progress), December 2017. + Architecture", draft-ietf-netmod-revised-datastores-10 + (work in progress), January 2018. 12.2. Informative References [I-D.ietf-netmod-rfc6087bis] Bierman, A., "Guidelines for Authors and Reviewers of YANG - Data Model Documents", draft-ietf-netmod-rfc6087bis-15 - (work in progress), December 2017. + Data Model Documents", draft-ietf-netmod-rfc6087bis-16 + (work in progress), January 2018. [RFC7895] Bierman, A., Bjorklund, M., and K. Watsen, "YANG Module Library", RFC 7895, DOI 10.17487/RFC7895, June 2016, . [RFC7951] Lhotka, L., "JSON Encoding of Data Modeled with YANG", RFC 7951, DOI 10.17487/RFC7951, August 2016, . [I-D.ietf-netmod-yang-tree-diagrams] Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft- - ietf-netmod-yang-tree-diagrams-04 (work in progress), - December 2017. + ietf-netmod-yang-tree-diagrams-05 (work in progress), + January 2018. Appendix A. The Complete Schema Tree This appendix presents the complete tree of the core routing data 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 corresponding line. module: ietf-routing +--rw routing @@ -3140,46 +3146,46 @@ operational state, in the JSON encoding [RFC7951]. The data conforms to a data model that is defined by the following YANG library specification [RFC7895]: { "ietf-yang-library:modules-state": { "module-set-id": "c2e1f54169aa7f36e1a6e8d0865d441d3600f9c4", "module": [ { "name": "ietf-routing", - "revision": "2018-01-07", + "revision": "2018-01-25", "feature": [ "multiple-ribs", "router-id" ], "namespace": "urn:ietf:params:xml:ns:yang:ietf-routing", "conformance-type": "implement" }, { "name": "ietf-ipv4-unicast-routing", - "revision": "2018-01-07", + "revision": "2018-01-25", "namespace": "urn:ietf:params:xml:ns:yang:ietf-ipv4-unicast-routing", "conformance-type": "implement" }, { "name": "ietf-ipv6-unicast-routing", - "revision": "2018-01-07", + "revision": "2018-01-25", "namespace": "urn:ietf:params:xml:ns:yang:ietf-ipv6-unicast-routing", "conformance-type": "implement", "submodule": [ { "name": "ietf-ipv6-router-advertisements", - "revision": "2018-01-07" + "revision": "2018-01-25" } ] }, { "name": "ietf-interfaces", "revision": "2017-12-16", "namespace": "urn:ietf:params:xml:ns:yang:ietf-interfaces", "conformance-type": "implement" }, { @@ -3579,21 +3585,22 @@ Acknowledgments The authors wish to thank Nitin Bahadur, Martin Bjorklund, Dean Bogdanovic, Jeff Haas, Joel Halpern, Wes Hardaker, Sriganesh Kini, David Lamparter, Andrew McGregor, Jan Medved, Xiang Li, Stephane Litkowski, Thomas Morin, Tom Petch, Bruno Rijsman, Juergen Schoenwaelder, Phil Shafer, Dave Thaler, Yi Yang, 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 Ladislav Lhotka CZ.NIC EMail: lhotka@nic.cz Acee Lindem Cisco Systems