|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
The referred RFC was approved by IESG (Internet Engineering Steering Group).
|
|
3.
|
Justification for the specific reference:
|
|
|
The Common YANG Data Types are used by YANG data models to promote consistency in data type definition.
|
|
4.
|
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=
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
The status of the referred RFC, is "Proposed Standard".
|
|
6.
|
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.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced RFC are listed under item (8).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative References/
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the/
Internet: Timestamps", RFC 3339, July 2002./
/
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,/
January 2004./
/
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform/
Resource Identifier (URI): Generic Syntax", STD 66,/
RFC 3986, January 2005./
/
[RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and/
B. Zill, "IPv6 Scoped Address Architecture", RFC 4007,/
March 2005./
/
[RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally/
Unique IDentifier (UUID) URN Namespace", RFC 4122,/
July 2005./
/
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing/
Architecture", RFC 4291, February 2006./
/
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for/
the Network Configuration Protocol (NETCONF)", RFC 6020,/
October 2010./
/
[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./
/
Informative References/
/
[IEEE802] IEEE, "IEEE Standard for Local and Metropolitan Area/
Networks: Overview and Architecture", IEEE Std. 802-/
2001, 2001./
/
[ISO9834-1] ISO/IEC, "Information technology -- Open Systems/
Interconnection -- Procedures for the operation of OSI/
Registration Authorities: General procedures and top/
arcs of the ASN.1 Object Identifier tree", ISO//
IEC 9834-1:2008, 2008./
/
[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,/
August 1980./
/
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791,/
September 1981./
/
[RFC0793] Postel, J., "Transmission Control Protocol", STD 7,/
RFC 793, September 1981./
/
[RFC0952] Harrenstien, K., Stahl, M., and E. Feinler, "DoD/
Internet host table specification", RFC 952,/
October 1985./
/
[RFC1034] Mockapetris, P., "Domain names - concepts and/
facilities", STD 13, RFC 1034, November 1987./
/
[RFC1123] Braden, R., "Requirements for Internet Hosts -/
Application and Support", STD 3, RFC 1123, October 1989./
/
[RFC1930] Hawkinson, J. and T. Bates, "Guidelines for creation,/
selection, and registration of an Autonomous System/
(AS)", BCP 6, RFC 1930, March 1996./
/
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6/
(IPv6) Specification", RFC 2460, December 1998./
/
[RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black,/
"Definition of the Differentiated Services Field (DS/
Field) in the IPv4 and IPv6 Headers", RFC 2474,/
December 1998./
/
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J./
Schoenwaelder, Ed., "Structure of Management Information/
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999./
/
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J./
Schoenwaelder, Ed., "Textual Conventions for SMIv2",/
STD 58, RFC 2579, April 1999./
/
[RFC2780] Bradner, S. and V. Paxson, "IANA Allocation Guidelines/
For Values In the Internet Protocol and Related/
Headers", BCP 37, RFC 2780, March 2000./
/
[RFC2782] Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for/
specifying the location of services (DNS SRV)",/
RFC 2782, February 2000./
/
[RFC2856] Bierman, A., McCloghrie, K., and R. Presuhn, "Textual/
Conventions for Additional High Capacity Data Types",/
RFC 2856, June 2000./
/
[RFC3289] Baker, F., Chan, K., and A. Smith, "Management/
Information Base for the Differentiated Services/
Architecture", RFC 3289, May 2002./
/
[RFC3305] Mealling, M. and R. Denenberg, "Report from the Joint/
W3C/IETF URI Planning Interest Group: Uniform Resource/
Identifiers (URIs), URLs, and Uniform Resource Names/
(URNs): Clarifications and Recommendations", RFC 3305,/
August 2002./
/
[RFC3595] Wijnen, B., "Textual Conventions for IPv6 Flow Label",/
RFC 3595, September 2003./
/
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J./
Schoenwaelder, "Textual Conventions for Internet Network/
Addresses", RFC 4001, February 2005./
/
[RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway/
Protocol 4 (BGP-4)", RFC 4271, January 2006./
/
[RFC4340] Kohler, E., Handley, M., and S. Floyd, "Datagram/
Congestion Control Protocol (DCCP)", RFC 4340,/
March 2006./
/
[RFC4502] Waldbusser, S., "Remote Network Monitoring Management/
Information Base Version 2", RFC 4502, May 2006./
/
[RFC4960] Stewart, R., "Stream Control Transmission Protocol",/
RFC 4960, September 2007./
/
[RFC5017] McWalter, D., "MIB Textual Conventions for Uniform/
Resource Identifiers (URIs)", RFC 5017, September 2007./
/
[RFC5890] Klensin, J., "Internationalized Domain Names for/
Applications (IDNA): Definitions and Document/
Framework", RFC 5890, August 2010./
/
[RFC5952] Kawamura, S. and M. Kawashima, "A Recommendation for/
IPv6 Address Text Representation", RFC 5952,/
August 2010./
/
[RFC6021] Schoenwaelder, J., "Common YANG Data Types", RFC 6021,/
October 2010./
/
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J.,/
Ed., and A. Bierman, Ed., "Network Configuration/
Protocol (NETCONF)", RFC 6241, June 2011./
/
[RFC6793] Vohra, Q. and E. Chen, "BGP Support for Four-Octet/
Autonomous System (AS) Number Space", RFC 6793,/
December 2012./
/
[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.
|
|
9.
|
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.
|
|
