--- 1/draft-ietf-netmod-rfc7277bis-01.txt 2018-01-09 01:13:10.030562283 -0800 +++ 2/draft-ietf-netmod-rfc7277bis-02.txt 2018-01-09 01:13:10.090563722 -0800 @@ -1,19 +1,19 @@ Network Working Group M. Bjorklund Internet-Draft Tail-f Systems -Obsoletes: rfc7277 (if approved) December 17, 2017 +Obsoletes: rfc7277 (if approved) January 9, 2018 Intended status: Standards Track -Expires: June 20, 2018 +Expires: July 13, 2018 A YANG Data Model for IP Management - draft-ietf-netmod-rfc7277bis-01 + draft-ietf-netmod-rfc7277bis-02 Abstract This document defines a YANG data model for management of IP implementations. The data model includes configuration and system state. This document obsoletes RFC 7277. Status of This Memo This Internet-Draft is submitted in full conformance with the @@ -22,25 +22,25 @@ 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 June 20, 2018. + This Internet-Draft will expire on July 13, 2018. Copyright Notice - Copyright (c) 2017 IETF Trust and the persons identified as the + Copyright (c) 2018 IETF Trust and the persons identified as the document authors. All rights reserved. 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 carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as @@ -54,21 +54,21 @@ 1.3. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3 2. IP Data Model . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Relationship to the IP-MIB . . . . . . . . . . . . . . . . . 6 4. IP Management YANG Module . . . . . . . . . . . . . . . . . . 7 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26 6. Security Considerations . . . . . . . . . . . . . . . . . . . 26 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 27 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 27 8.1. Normative References . . . . . . . . . . . . . . . . . . 27 8.2. Informative References . . . . . . . . . . . . . . . . . 29 - Appendix A. Example: NETCONF reply . . . . . . . . 29 + Appendix A. Example: NETCONF reply . . . . . . . . 30 Appendix B. Example: NETCONF Reply . . . . . . . . . 30 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 32 1. Introduction This document defines a YANG [RFC7950] data model for management of IP implementations. The data model covers configuration of per-interface IPv4 and IPv6 parameters, and mappings of IP addresses to link-layer addresses. It @@ -249,21 +249,21 @@ 4. IP Management YANG Module This module imports typedefs from [RFC6991] and [I-D.ietf-netmod-rfc7223bis], and it references [RFC0791], [RFC0826], [RFC2460], [RFC4861], [RFC4862], [RFC4941] and [RFC7217]. RFC Ed.: update the date below with the date of RFC publication and remove this note. - file "ietf-ip@2017-12-16.yang" + file "ietf-ip@2018-01-09.yang" module ietf-ip { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-ip"; prefix ip; import ietf-interfaces { prefix if; } import ietf-inet-types { prefix inet; @@ -278,34 +278,34 @@ contact "WG Web: WG List: Editor: Martin Bjorklund "; description "This module contains a collection of YANG definitions for managing IP implementations. - Copyright (c) 2017 IETF Trust and the persons identified as + Copyright (c) 2018 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or 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."; - revision 2017-12-16 { + revision 2018-01-09 { description "Updated to support NMDA."; reference "RFC XXXX: A YANG Data Model for IP Management"; } revision 2014-06-16 { description "Initial revision."; reference @@ -1141,27 +1141,31 @@ This document registers a YANG module in the "YANG Module Names" registry [RFC6020]. Name: ietf-ip Namespace: urn:ietf:params:xml:ns:yang:ietf-ip Prefix: ip Reference: RFC 7277 6. Security Considerations - The YANG module defined in this memo is designed to be accessed via - the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the - secure transport layer and the mandatory-to-implement secure - transport is SSH [RFC6242]. The NETCONF access control model - [RFC6536] provides the means to restrict access for particular - NETCONF users to a pre-configured subset of all available NETCONF - protocol operations and content. + The YANG module defined in this document is designed to be accessed + via network management protocols such as NETCONF [RFC6241] or + RESTCONF [RFC8040]. The lowest NETCONF layer is the secure transport + layer, and the mandatory-to-implement secure transport is Secure + Shell (SSH) [RFC6242]. The lowest RESTCONF layer is HTTPS, and the + mandatory-to-implement secure transport is TLS [RFC5246]. + + The NETCONF access control model [RFC6536] provides the means to + restrict access for particular NETCONF or RESTCONF users to a + preconfigured subset of all available NETCONF or RESTCONF protocol + operations and content. There are a number of data nodes defined in the YANG module which are writable/creatable/deletable (i.e., config true, which is the default). These data nodes may be considered sensitive or vulnerable in some network environments. Write operations (e.g., edit-config) to these data nodes without proper protection can have a negative effect on network operations. These are the subtrees and data nodes and their sensitivity/vulnerability: ipv4/enabled and ipv6/enabled: These leafs are used to enable or @@ -1208,73 +1212,86 @@ 8.1. Normative References [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-07 (work in progress), November 2017. [I-D.ietf-netmod-rfc7223bis] Bjorklund, M., "A YANG Data Model for Interface - Management", draft-ietf-netmod-rfc7223bis-00 (work in - progress), October 2017. + Management", draft-ietf-netmod-rfc7223bis-01 (work in + progress), December 2017. - [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, DOI - 10.17487/RFC0791, September 1981, . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate - Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ - RFC2119, March 1997, . + Requirement Levels", BCP 14, RFC 2119, + DOI 10.17487/RFC2119, March 1997, . [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460, December 1998, . [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, . [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, DOI 10.17487/RFC4861, September 2007, . [RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless - Address Autoconfiguration", RFC 4862, DOI 10.17487/ - RFC4862, September 2007, . + Address Autoconfiguration", RFC 4862, + DOI 10.17487/RFC4862, September 2007, . [RFC4941] Narten, T., Draves, R., and S. Krishnan, "Privacy Extensions for Stateless Address Autoconfiguration in IPv6", RFC 4941, DOI 10.17487/RFC4941, September 2007, . + [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security + (TLS) Protocol Version 1.2", RFC 5246, + DOI 10.17487/RFC5246, August 2008, . + [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, DOI 10.17487/RFC6020, October 2010, . [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., and A. Bierman, Ed., "Network Configuration Protocol (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, . - [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC - 6991, DOI 10.17487/RFC6991, July 2013, . + [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure + Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, + . + + [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", + RFC 6991, DOI 10.17487/RFC6991, July 2013, + . [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", RFC 7950, DOI 10.17487/RFC7950, August 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, . 8.2. Informative References [I-D.ietf-netmod-yang-tree-diagrams] Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft- ietf-netmod-yang-tree-diagrams-02 (work in progress), October 2017. @@ -1282,34 +1299,30 @@ [RFC0826] Plummer, D., "Ethernet Address Resolution Protocol: Or Converting Network Protocol Addresses to 48.bit Ethernet Address for Transmission on Ethernet Hardware", STD 37, RFC 826, DOI 10.17487/RFC0826, November 1982, . [RFC4293] Routhier, S., Ed., "Management Information Base for the Internet Protocol (IP)", RFC 4293, DOI 10.17487/RFC4293, April 2006, . - [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure - Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, - . - [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration - Protocol (NETCONF) Access Control Model", RFC 6536, DOI - 10.17487/RFC6536, March 2012, . [RFC7217] Gont, F., "A Method for Generating Semantically Opaque Interface Identifiers with IPv6 Stateless Address - Autoconfiguration (SLAAC)", RFC 7217, DOI 10.17487/ - RFC7217, April 2014, . + Autoconfiguration (SLAAC)", RFC 7217, + DOI 10.17487/RFC7217, April 2014, . [RFC8022] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing Management", RFC 8022, DOI 10.17487/RFC8022, November 2016, . Appendix A. Example: NETCONF reply This section gives an example of a reply to the NETCONF request for the running configuration datastore for a device that implements the data model defined in this document. @@ -1342,33 +1355,37 @@ Appendix B. Example: NETCONF Reply This section gives an example of a reply to the NETCONF request for the operational state datastore for a device that implements the data model defined in this document. + This example uses the "origin" annotation, which is defined in the + module "ietf-origin" [I-D.ietf-netmod-revised-datastores]. + - + eth0 ianaift:ethernetCsmacd + true false 1500
192.0.2.1 24 static