References from rfc2611
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 26 |
Guidelines for Writing an IANA Considerations Section in RFCs References Referenced by |
Best Current Practice | Reference | |
| RFC 1035 |
Domain names - implementation and specification References Referenced by |
Internet Standard | Possible Reference | |
| RFC 1737 |
Functional Requirements for Uniform Resource Names References Referenced by |
Informational | Reference | Possible Downref |
| RFC 2141 |
URN Syntax References Referenced by |
Proposed Standard | Reference | Possible Downref |
| RFC 2168 |
Resolution of Uniform Resource Identifiers using the Domain Name System References Referenced by |
Experimental | Reference | Possible Downref |
| RFC 2169 |
A Trivial Convention for using HTTP in URN Resolution References Referenced by |
Experimental | Reference | Possible Downref |
| RFC 2276 |
Architectural Principles of Uniform Resource Name Resolution References Referenced by |
Informational | Reference | Possible Downref |
| RFC 2288 |
Using Existing Bibliographic Identifiers as Uniform Resource Names References Referenced by |
Informational | Reference | Possible Downref |
| RFC 2434 |
Guidelines for Writing an IANA Considerations Section in RFCs References Referenced by |
Best Current Practice | Reference |