References to RFC 2050
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.
Showing RFCs and active Internet-Drafts, sorted by reference type, then document name.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| RFC 4085 | Embedding Globally-Routable Internet Addresses Considered Harmful References Referenced by | Best Current Practice | normatively references | |
| RFC 3779 | X.509 Extensions for IP Addresses and AS Identifiers References Referenced by | Proposed Standard | informatively references | |
| RFC 5211 | An Internet Transition Plan References Referenced by | Informational | informatively references | |
| RFC 5737 | IPv4 Address Blocks Reserved for Documentation References Referenced by | Informational | informatively references | |
| RFC 2626 | The Internet and the Millennium Problem (Year 2000) References Referenced by | Informational | Possible Reference | |
| RFC 2993 | Architectural Implications of NAT References Referenced by | Informational | Possible Reference | |
| RFC 7020 | The Internet Numbers Registry System References Referenced by | Informational | Possible Reference | |
| RFC 2374 | An IPv6 Aggregatable Global Unicast Address Format References Referenced by | Historic | Reference | |
| RFC 2725 | Routing Policy System Security References Referenced by | Proposed Standard | Reference | |
| RFC 2901 | Guide to Administrative Procedures of the Internet Infrastructure References Referenced by | Informational | Reference | |
| RFC 3021 | Using 31-Bit Prefixes on IPv4 Point-to-Point Links References Referenced by | Proposed Standard | Reference | |
| RFC 3330 | Special-Use IPv4 Addresses References Referenced by | Informational | Reference |