ITU-T A.5 reference justification

Home : ITU-T Home : ITU-T Work Programme : G.8052.1/Y.1346.1

ITU-T A.5 justification information for referenced document IETF RFC 7950 (2016) in draft G.8052.1/Y.1346.1

Clear description of the referenced document:

Name:	IETF RFC 7950 (2016)
Title:	The YANG 1.1 Data Modeling Language

Status of approval:

The referred RFC was approved by IESG (Internet Engineering Steering Group).

Justification for the specific reference:

YANG 1.1 is the maintenance release of the YANG 1.0 language that is leveraged by the ITU-T as the data modeling language format

Current information, if any, about IPR issues:

Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?draft=&rfc=8531&submit=rfc&doctitle=&group=&holder=&iprtitle=&patent=

Other useful information describing the "Quality" of the document:

The status of the referred RFC, is "Proposed Standard".

The degree of stability or maturity of the document:

RFC is a standards-track document and is currently in the "Proposed Standard" state. Errata exist.

Relationship with other existing or emerging documents:

References within the referenced RFC are listed under item (8).

Any explicit references within that referenced document should also be listed:

Normative References/
/
[ISO.10646]/
International Organization for Standardization,/
"Information Technology - Universal Multiple-Octet Coded/
Character Set (UCS)", ISO Standard 10646:2014, 2014./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119,/
DOI 10.17487/RFC2119, March 1997,/
http://www.rfc-editor.org/info/rfc2119./
/
[RFC3629] Yergeau, F., "UTF-8, a transformation format of/
ISO 10646", STD 63, RFC 3629, DOI 10.17487/RFC3629,/
November 2003, http://www.rfc-editor.org/info/rfc3629./
/
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform/
Resource Identifier (URI): Generic Syntax", STD 66,/
RFC 3986, DOI 10.17487/RFC3986, January 2005,/
http://www.rfc-editor.org/info/rfc3986./
/
[RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data/
Encodings", RFC 4648, DOI 10.17487/RFC4648, October 2006,/
http://www.rfc-editor.org/info/rfc4648./
/
[RFC5234] Crocker, D., Ed., and P. Overell, "Augmented BNF for/
Syntax Specifications: ABNF", STD 68, RFC 5234,/
DOI 10.17487/RFC5234, January 2008,/
http://www.rfc-editor.org/info/rfc5234./
/
[RFC5277] Chisholm, S. and H. Trevino, "NETCONF Event/
Notifications", RFC 5277, DOI 10.17487/RFC5277, July 2008,/
http://www.rfc-editor.org/info/rfc5277./
/
[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,/
http://www.rfc-editor.org/info/rfc6241./
/
[RFC7405] Kyzivat, P., "Case-Sensitive String Support in ABNF",/
RFC 7405, DOI 10.17487/RFC7405, December 2014,/
http://www.rfc-editor.org/info/rfc7405./
/
[RFC7895] Bierman, A., Bjorklund, M., and K. Watsen, "YANG Module/
Library", RFC 7895, DOI 10.17487/RFC7895, June 2016,/
http://www.rfc-editor.org/info/rfc7895./
/
[XML] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and/
F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth/
Edition)", W3C Recommendation REC-xml-20081126,/
November 2008,/
https://www.w3.org/TR/2008/REC-xml-20081126/./
/
[XML-NAMES]/
Bray, T., Hollander, D., Layman, A., Tobin, R., and H./
Thompson, "Namespaces in XML 1.0 (Third Edition)", World/
Wide Web Consortium Recommendation REC-xml-names-20091208,/
December 2009,/
http://www.w3.org/TR/2009/REC-xml-names-20091208./
/
[XPATH] Clark, J. and S. DeRose, "XML Path Language (XPath)/
Version 1.0", World Wide Web Consortium Recommendation/
REC-xpath-19991116, November 1999,/
http://www.w3.org/TR/1999/REC-xpath-19991116./
/
[XSD-TYPES]/
Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes/
Second Edition", World Wide Web Consortium Recommendation/
REC-xmlschema-2-20041028, October 2004,/
http://www.w3.org/TR/2004/REC-xmlschema-2-20041028./
/
Informative References/
/
[CoMI] van der Stok, P. and A. Bierman, "CoAP Management/
Interface", Work in Progress,/
draft-vanderstok-core-comi-09, March 2016./
/
[IEEE754-2008]/
IEEE, "IEEE Standard for Floating-Point Arithmetic",/
IEEE 754-2008, DOI 10.1109/IEEESTD.2008.4610935, 2008,/
http://standards.ieee.org/findstds//
standard/754-2008.html./
/
[RESTCONF]/
Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF/
Protocol", Work in Progress,/
draft-ietf-netconf-restconf-16, August 2016./
/
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J./
Schoenwaelder, Ed., "Structure of Management Information/
Version 2 (SMIv2)", STD 58, RFC 2578,/
DOI 10.17487/RFC2578, April 1999,/
http://www.rfc-editor.org/info/rfc2578./
/
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J./
Schoenwaelder, Ed., "Textual Conventions for SMIv2",/
STD 58, RFC 2579, DOI 10.17487/RFC2579, April 1999,/
http://www.rfc-editor.org/info/rfc2579./
/
[RFC3780] Strauss, F. and J. Schoenwaelder, "SMIng - Next Generation/
Structure of Management Information", RFC 3780,/
DOI 10.17487/RFC3780, May 2004,/
http://www.rfc-editor.org/info/rfc3780./
/
[RFC4844] Daigle, L., Ed., and Internet Architecture Board, "The RFC/
Series and RFC Editor", RFC 4844, DOI 10.17487/RFC4844,/
July 2007, http://www.rfc-editor.org/info/rfc4844./
/
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for/
the Network Configuration Protocol (NETCONF)", RFC 6020,/
DOI 10.17487/RFC6020, October 2010,/
http://www.rfc-editor.org/info/rfc6020./
/
[RFC6643] Schoenwaelder, J., "Translation of Structure of Management/
Information Version 2 (SMIv2) MIB Modules to YANG/
Modules", RFC 6643, DOI 10.17487/RFC6643, July 2012,/
http://www.rfc-editor.org/info/rfc6643./
/
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",/
RFC 6991, DOI 10.17487/RFC6991, July 2013,/
http://www.rfc-editor.org/info/rfc6991./
/
[RFC7951] Lhotka, L., "JSON Encoding of Data Modeled with YANG",/
RFC 7951, DOI 10.17487/RFC7951, August 2016,/
http://www.rfc-editor.org/info/rfc7951./
/
[XPATH2.0]/
Berglund, A., Boag, S., Chamberlin, D., Fernandez, M.,/
Kay, M., Robie, J., and J. Simeon, "XML Path Language/
(XPath) 2.0 (Second Edition)", World Wide Web Consortium/
Recommendation REC-xpath20-20101214, December 2010,/
http://www.w3.org/TR/2010/REC-xpath20-20101214./
/
[XSLT] Clark, J., "XSL Transformations (XSLT) Version 1.0", World/
Wide Web Consortium Recommendation REC-xslt-19991116,/
November 1999,/
http://www.w3.org/TR/1999/REC-xslt-19991116./
/
[YANG-Guidelines]/
Bierman, A., "Guidelines for Authors and Reviewers of YANG/
Data Model Documents", Work in Progress,/
draft-ietf-netmod-rfc6087bis-07, July 2016.

Qualification of ISOC/IETF:

9.1-9.6     Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7     The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8     Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.

10.

Other (for any supplementary information):

Reference should always be made by RFC number (and not by other designations such as STD, BCP, etc.). References should not be made to documents referred to as "Internet Drafts" or to IETF RFCs categorized as Historic or Experimental. Normative references must only be made to IETF RFCs that are Standards Track or to Informational RFCs that have IETF consensus.

Note: This form is based on Recommendation ITU-T A.5

Connecting the world and beyond

ITU-T work programme