References from RFC 8522
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 13 |
References Referenced by |
informatively references | ||
BCP 6 |
References Referenced by |
informatively references | ||
RFC 3849 |
IPv6 Address Prefix Reserved for Documentation
References Referenced by |
Informational | informatively references | |
RFC 4760 |
Multiprotocol Extensions for BGP-4
References Referenced by |
Draft Standard | normatively references | |
RFC 5737 |
IPv4 Address Blocks Reserved for Documentation
References Referenced by |
Informational | informatively references | |
RFC 5785 |
Defining Well-Known Uniform Resource Identifiers (URIs)
References Referenced by |
Proposed Standard | normatively references | |
RFC 6570 |
URI Template
References Referenced by |
Proposed Standard | normatively references | |
RFC 6761 |
Special-Use Domain Names
References Referenced by |
Proposed Standard | informatively references | |
RFC 6838 |
Media Type Specifications and Registration Procedures
References Referenced by |
Best Current Practice | informatively references | |
RFC 6996 |
Autonomous System (AS) Reservation for Private Use
References Referenced by |
Best Current Practice | informatively references | |
RFC 7231 |
Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
References Referenced by |
Proposed Standard | normatively references | |
RFC 7320 |
URI Design and Ownership
References Referenced by |
Best Current Practice | informatively references | |
RFC 8259 |
The JavaScript Object Notation (JSON) Data Interchange Format
References Referenced by |
Internet Standard | normatively references | |
STD 90 |
References Referenced by |
normatively references |