References from rfc3044
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 |
|---|---|---|---|---|
| RFC 1737 |
Functional Requirements for Uniform Resource Names References Referenced by |
Informational | Reference | |
| RFC 2141 |
URN Syntax References Referenced by |
Proposed Standard | Reference | |
| RFC 2168 |
Resolution of Uniform Resource Identifiers using the Domain Name System References Referenced by |
Experimental | Reference | |
| RFC 2248 |
Network Services Monitoring MIB References Referenced by |
Proposed Standard | Possible Reference | |
| RFC 2276 |
Architectural Principles of Uniform Resource Name Resolution References Referenced by |
Informational | Reference | |
| RFC 2288 |
Using Existing Bibliographic Identifiers as Uniform Resource Names References Referenced by |
Informational | Reference | |
| RFC 2483 |
URI Resolution Services Necessary for URN Resolution References Referenced by |
Experimental | Possible Reference | |
| RFC 2611 |
URN Namespace Definition Mechanisms References Referenced by |
Best Current Practice | Possible Reference | |
| RFC 2648 |
A URN Namespace for IETF Documents References Referenced by |
Informational | Possible Reference |