References from rfc3172
This is an experimental product. 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 40 |
Root Name Server Operational Requirements Refs Ref'd by |
Best Current Practice | Reference | |
| BCP 49 |
Delegation of IP6.ARPA Refs Ref'd by |
Best Current Practice | Reference | |
| BCP 9 |
Reducing the Standards Track to Two Maturity Levels Refs Ref'd by |
Best Current Practice | Reference | |
| RFC 1034 |
Domain names - concepts and facilities Refs Ref'd by |
Internet Standard | Reference | |
| RFC 2026 |
The Internet Standards Process -- Revision 3 Refs Ref'd by |
Best Current Practice | Reference | |
| RFC 2860 |
Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers Authority Refs Ref'd by |
Informational | Reference | Possible Downref |
| RFC 2870 |
Root Name Server Operational Requirements Refs Ref'd by |
Best Current Practice | Possible Reference | |
| RFC 2874 |
DNS Extensions to Support IPv6 Address Aggregation and Renumbering Refs Ref'd by |
Historic | Reference | Possible Downref |
| RFC 2916 |
E.164 number and DNS Refs Ref'd by |
Proposed Standard | Reference | Possible Downref |
| RFC 3026 |
Liaison to IETF/ISOC on ENUM Refs Ref'd by |
Informational | Reference | Possible Downref |
| STD 13 |
Domain names - implementation and specification Refs Ref'd by |
Internet Standard | Reference |