References from rfc8610

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
BCP 14	Key words for use in RFCs to Indicate Requirement Levels References Referenced by	Best Current Practice	normatively references
BCP 26	Guidelines for Writing an IANA Considerations Section in RFCs References Referenced by	Best Current Practice	normatively references
BCP 72	Guidelines for Writing RFC Text on Security Considerations References Referenced by	Best Current Practice	normatively references
draft-bormann-cbor-cddl-freezer	A feature freezer for the Concise Data Definition Language (CDDL) References Referenced by		informatively references
draft-ietf-anima-grasp	A Generic Autonomic Signaling Protocol (GRASP) References Referenced by	Proposed Standard	informatively references
draft-newton-json-content-rules	A Language for Rules Describing JSON Content References Referenced by		informatively references
RFC 2119	Key words for use in RFCs to Indicate Requirement Levels References Referenced by	Best Current Practice	normatively references
RFC 3552	Guidelines for Writing RFC Text on Security Considerations References Referenced by	Best Current Practice	normatively references
RFC 3629	UTF-8, a transformation format of ISO 10646 References Referenced by	Internet Standard	normatively references
RFC 4648	The Base16, Base32, and Base64 Data Encodings References Referenced by	Proposed Standard	normatively references
RFC 5234	Augmented BNF for Syntax Specifications: ABNF References Referenced by	Internet Standard	normatively references
RFC 7049	Concise Binary Object Representation (CBOR) References Referenced by	Proposed Standard	normatively references
RFC 7071	A Media Type for Reputation Interchange References Referenced by	Proposed Standard	informatively references
RFC 7493	The I-JSON Message Format References Referenced by	Proposed Standard	normatively references
RFC 7950	The YANG 1.1 Data Modeling Language References Referenced by	Proposed Standard	informatively references
RFC 8007	Content Delivery Network Interconnection (CDNI) Control Interface / Triggers References Referenced by	Proposed Standard	informatively references
RFC 8126	Guidelines for Writing an IANA Considerations Section in RFCs References Referenced by	Best Current Practice	normatively references
RFC 8152	CBOR Object Signing and Encryption (COSE) References Referenced by	Proposed Standard	informatively references
RFC 8174	Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words References Referenced by	Best Current Practice	normatively references
RFC 8259	The JavaScript Object Notation (JSON) Data Interchange Format References Referenced by	Internet Standard	normatively references
RFC 8428	Sensor Measurement Lists (SenML) References Referenced by	Proposed Standard	informatively references
STD 63	UTF-8, a transformation format of ISO 10646 References Referenced by	Internet Standard	normatively references
STD 68	Augmented BNF for Syntax Specifications: ABNF References Referenced by	Internet Standard	normatively references
STD 90	The JavaScript Object Notation (JSON) Data Interchange Format References Referenced by	Internet Standard	normatively references