YANG Module Library
RFC 7895
Document | Type |
RFC - Proposed Standard
(June 2016; No errata)
Obsoleted by RFC 8525
|
|||||
---|---|---|---|---|---|---|---|
Authors | Andy Bierman , Martin Björklund , Kent Watsen | ||||||
Last updated | 2016-06-30 | ||||||
Stream | IETF | ||||||
Formats | plain text html pdf htmlized bibtex | ||||||
Yang Validation | ☯ 2 errors, 0 warnings. | ||||||
Reviews | |||||||
Additional Resources |
|
||||||
Stream | WG state | Submitted to IESG for Publication | |||||
Document shepherd | Mahesh Jethanandani | ||||||
Shepherd write-up | Show (last changed 2016-04-25) | ||||||
IESG | IESG state | RFC 7895 (Proposed Standard) | |||||
Action Holders |
(None)
|
||||||
Consensus Boilerplate | Yes | ||||||
Telechat date | |||||||
Responsible AD | Benoît Claise | ||||||
Send notices to | (None) | ||||||
IANA | IANA review state | IANA OK - Actions Needed | |||||
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) A. Bierman Request for Comments: 7895 YumaWorks Category: Standards Track M. Bjorklund ISSN: 2070-1721 Tail-f Systems K. Watsen Juniper Networks June 2016 YANG Module Library Abstract This document describes a YANG library that provides information about all the YANG modules used by a network management server (e.g., a Network Configuration Protocol (NETCONF) server). Simple caching mechanisms are provided to allow clients to minimize retrieval of this information. 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 http://www.rfc-editor.org/info/rfc7895. Copyright Notice Copyright (c) 2016 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 described in the Simplified BSD License. Bierman, et al. Standards Track [Page 1] RFC 7895 YANG Library June 2016 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3 2. YANG Module Library . . . . . . . . . . . . . . . . . . . . . 4 2.1. modules-state . . . . . . . . . . . . . . . . . . . . . . 4 2.1.1. modules-state/module-set-id . . . . . . . . . . . . . 4 2.1.2. modules-state/module . . . . . . . . . . . . . . . . 5 2.2. YANG Library Module . . . . . . . . . . . . . . . . . . . 5 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 3.1. YANG Module Registry . . . . . . . . . . . . . . . . . . 11 4. Security Considerations . . . . . . . . . . . . . . . . . . . 11 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 5.1. Normative References . . . . . . . . . . . . . . . . . . 12 5.2. Informative References . . . . . . . . . . . . . . . . . 12 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 1. Introduction There is a need for standard mechanisms to identify the YANG modules and submodules that are in use by a server that implements YANG data models. If a large number of YANG modules are utilized by the server, then the YANG library contents needed can be relatively large. This information changes very infrequently, so it is important that clients be able to cache the YANG library contents and easily identify whether their cache is out of date. YANG library information can be different on every server and can change at runtime or across a server reboot. If the server implements multiple protocols to access the YANG- defined data, each such protocol has its own conceptual instantiation of the YANG library. The following information is needed by a client application (for each YANG module in the library) to fully utilize the YANG data modeling language: o name: The name of the YANG module. o revision: Each YANG module and submodule within the library has a revision. This is derived from the most recent revision statement within the module or submodule. If no such revision statement exists, the module's or submodule's revision is the zero-length string. Bierman, et al. Standards Track [Page 2] RFC 7895 YANG Library June 2016 o submodule list: The name and revision of each submodule used by the module MUST be identified.Show full document text