References from RFC 6217
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 153 |
References Referenced by |
informatively references | ||
| BCP 32 |
References Referenced by |
informatively references | ||
| RFC 1087 |
Ethics and the Internet
References Referenced by |
Unknown | informatively references | |
| RFC 1149 |
Standard for the transmission of IP datagrams on avian carriers
References Referenced by |
Experimental | informatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | Possible Reference | |
| RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | Possible Reference | |
| RFC 4291 |
IP Version 6 Addressing Architecture
References Referenced by |
Draft Standard | informatively references | |
| RFC 5156 |
Special-Use IPv6 Addresses
References Referenced by |
Informational | informatively references | |
| RFC 5735 |
Special Use IPv4 Addresses
References Referenced by |
Best Current Practice | informatively references | |
| RFC 5741 |
RFC Streams, Headers, and Boilerplates
References Referenced by |
Informational | Possible Reference | |
| RFC 5952 |
A Recommendation for IPv6 Address Text Representation
References Referenced by |
Proposed Standard | informatively references | |
| RFC 919 |
Broadcasting Internet Datagrams
References Referenced by |
Internet Standard | Possible Reference | |
| STD 5 |
References Referenced by |
normatively references | ||
| STD 66 |
References Referenced by |
informatively references |