References from draft-ietf-cbor-network-addresses
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 |
|---|---|---|---|---|
| BCP 14 |
References Referenced by |
normatively references | ||
| BCP 141 |
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 4001 |
Textual Conventions for Internet Network Addresses
References Referenced by |
Proposed Standard | informatively references | |
| RFC 4007 |
IPv6 Scoped Address Architecture
References Referenced by |
Proposed Standard | informatively references | |
| RFC 6991 |
Common YANG Data Types
References Referenced by |
Proposed Standard | informatively references | |
| RFC 7042 |
IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters
References Referenced by |
Best Current Practice | 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 8949 |
Concise Binary Object Representation (CBOR)
References Referenced by |
Internet Standard | normatively references | |
| STD 94 |
References Referenced by |
normatively references |