A YANG Data Model for IP Management
RFC 8344
Document | Type |
RFC - Proposed Standard
(March 2018; No errata)
Obsoletes RFC 7277
|
|||||
---|---|---|---|---|---|---|---|
Author | Martin Björklund | ||||||
Last updated | 2018-12-19 | ||||||
Replaces | draft-bjorklund-netmod-rfc7277bis | ||||||
Stream | IETF | ||||||
Formats | plain text html pdf htmlized bibtex | ||||||
Yang Validation | ☯ 0 errors, 0 warnings. | ||||||
Reviews | |||||||
Additional Resources |
|
||||||
Stream | WG state | Submitted to IESG for Publication | |||||
Document shepherd | Joel Jaeggli | ||||||
Shepherd write-up | Show (last changed 2017-12-18) | ||||||
IESG | IESG state | RFC 8344 (Proposed Standard) | |||||
Action Holders |
(None)
|
||||||
Consensus Boilerplate | Yes | ||||||
Telechat date | |||||||
Responsible AD | Benoît Claise | ||||||
Send notices to | Joel Jaeggli <joelja@bogus.com> | ||||||
IANA | IANA review state | Version Changed - Review Needed | |||||
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) M. Bjorklund Request for Comments: 8344 Tail-f Systems Obsoletes: 7277 March 2018 Category: Standards Track ISSN: 2070-1721 A YANG Data Model for IP Management Abstract This document defines a YANG data model for management of IP implementations. The data model includes configuration and system state. The YANG data model in this document conforms to the Network Management Datastore Architecture defined in RFC 8342. This document obsoletes RFC 7277. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc8344. 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 (https://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 described in the Simplified BSD License. Bjorklund Standards Track [Page 1] RFC 8344 YANG IP Management March 2018 Table of Contents 1. Introduction ....................................................2 1.1. Summary of Changes from RFC 7277 ...........................2 1.2. Terminology ................................................3 1.3. Tree Diagrams ..............................................3 2. IP Data Model ...................................................4 3. Relationship to the IP-MIB ......................................5 4. IP Management YANG Module .......................................7 5. IANA Considerations ............................................27 6. Security Considerations ........................................27 7. References .....................................................29 7.1. Normative References ......................................29 7.2. Informative References ....................................31 Appendix A. Example: NETCONF <get-config> Reply ...................32 Appendix B. Example: NETCONF <get-data> Reply .....................33 Acknowledgments ...................................................34 Author's Address ..................................................34 1. Introduction This document defines a YANG data model [RFC7950] for management of IP implementations. The data model covers configuration of per-interface IPv4 and IPv6 parameters as well as mappings of IP addresses to link-layer addresses. It also provides information about which IP addresses are operationally used and which link-layer mappings exist. Per-interface parameters are added through augmentation of the interface data model defined in [RFC8343]. This version of the IP data model supports the Network Management Datastore Architecture (NMDA) [RFC8342]. 1.1. Summary of Changes from RFC 7277 The "ipv4" and "ipv6" subtrees with "config false" data nodes in the "/interfaces-state/interface" subtree are deprecated. All "config false" data nodes are now present in the "ipv4" and "ipv6" subtrees in the "/interfaces/interface" subtree. Servers that do not implement NMDA or that wish to support clients that do not implement NMDA MAY implement the deprecated "ipv4" and "ipv6" subtrees in the "/interfaces-state/interface" subtree. Bjorklund Standards Track [Page 2] RFC 8344 YANG IP Management March 2018 1.2. Terminology 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. The following terms are defined in [RFC8342] and are not redefined here: o client o server o configuration o system stateShow full document text