References from draft-bormann-cbor-cddl-more-control
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.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 4648 |
The Base16, Base32, and Base64 Data Encodings
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7951 |
JSON Encoding of Data Modeled with YANG
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 8610 |
Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8742 |
Concise Binary Object Representation (CBOR) Sequences
References Referenced by |
Proposed Standard | normatively references | |
| RFC 9090 |
Concise Binary Object Representation (CBOR) Tags for Object Identifiers
References Referenced by |
Proposed Standard | informatively references | |
| RFC 9165 |
Additional Control Operators for the Concise Data Definition Language (CDDL)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 9285 |
The Base45 Data Encoding
References Referenced by |
Informational | normatively references | |
| STD 90 |
References Referenced by |
normatively references | ||
| STD 94 |
References Referenced by |
normatively references |