References from draft-mahesh-netconf-binary-encoding

This is an experimental product. These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.

Reference type help

Document Title Status Type Downref
BCP 14 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
draft-ietf-core-yang-cbor CBOR Encoding of Data Modeled with YANG
Refs Ref'd by
normatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
RFC 3688 The IETF XML Registry
Refs Ref'd by
Best Current Practice normatively references
RFC 6241 Network Configuration Protocol (NETCONF)
Refs Ref'd by
Proposed Standard normatively references
RFC 7049 Concise Binary Object Representation (CBOR)
Refs Ref'd by
Proposed Standard normatively references
RFC 7950 The YANG 1.1 Data Modeling Language
Refs Ref'd by
Proposed Standard normatively references
RFC 7951 JSON Encoding of Data Modeled with YANG
Refs Ref'd by
Proposed Standard informatively references
RFC 8174 Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Refs Ref'd by
Best Current Practice normatively references
RFC 8259 The JavaScript Object Notation (JSON) Data Interchange Format
Refs Ref'd by
Internet Standard normatively references
STD 90 The JavaScript Object Notation (JSON) Data Interchange Format
Refs Ref'd by
Internet Standard normatively references