References from rfc3245
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 References Referenced by |
Best Current Practice | normatively references | |
| BCP 52 |
Management Guidelines & Operational Requirements for the Address and Routing Parameter Area Domain ("arpa") References Referenced by |
Best Current Practice | normatively references | |
| RFC 2826 |
IAB Technical Comment on the Unique DNS Root References Referenced by |
Informational | Possible Reference | |
| RFC 2860 |
Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers Authority References Referenced by |
Informational | normatively references | |
| RFC 2870 |
Root Name Server Operational Requirements References Referenced by |
Best Current Practice | normatively references | |
| RFC 2916 |
E.164 number and DNS References Referenced by |
Proposed Standard | normatively references | |
| RFC 3172 |
Management Guidelines & Operational Requirements for the Address and Routing Parameter Area Domain ("arpa") References Referenced by |
Best Current Practice | normatively references | |
| RFC 881 |
Domain names plan and schedule References Referenced by |
Unknown | Possible Reference |