References from draft-troan-6man-universal-ra-option
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 26 |
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 4861 |
Neighbor Discovery for IP version 6 (IPv6)
References Referenced by |
Draft Standard | normatively references | |
RFC 6919 |
Further Key Words for Use in RFCs to Indicate Requirement Levels
References Referenced by |
Experimental | normatively references | |
RFC 7049 |
Concise Binary Object Representation (CBOR)
References Referenced by |
Proposed Standard | normatively references | |
RFC 8106 |
IPv6 Router Advertisement Options for DNS Configuration
References Referenced by |
Proposed Standard | informatively references | |
RFC 8126 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | informatively references | |
RFC 8259 |
The JavaScript Object Notation (JSON) Data Interchange Format
References Referenced by |
Internet Standard | informatively 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 8801 |
Discovering Provisioning Domain Names and Data
References Referenced by |
Proposed Standard | informatively references | |
STD 90 |
References Referenced by |
informatively references |