References to RFC 2288
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 |
---|---|---|---|---|
draft-kunze-ark |
The ARK Identifier Scheme
References Referenced by |
informatively references | ||
RFC 8254 |
Uniform Resource Name (URN) Namespace Registration Transition
References Referenced by |
Proposed Standard | informatively references | |
RFC 8458 |
Using National Bibliography Numbers as Uniform Resource Names
References Referenced by |
Informational | informatively references | |
RFC 3199 |
Request for Comments Summary RFC Numbers 3100-3199
References Referenced by |
Informational | Possible Reference | |
RFC 3499 |
Request for Comments Summary RFC Numbers 3400-3499
References Referenced by |
Informational | Possible Reference | |
RFC 2611 |
URN Namespace Definition Mechanisms
References Referenced by |
Best Current Practice | Reference | |
RFC 3044 |
Using The ISSN (International Serial Standard Number) as URN (Uniform Resource Names) within an ISSN-URN Namespace
References Referenced by |
Historic | Reference | |
RFC 3187 |
Using International Standard Book Numbers as Uniform Resource Names
References Referenced by |
Historic | Reference | |
RFC 3188 |
Using National Bibliography Numbers as Uniform Resource Names
References Referenced by |
Informational | Reference | |
RFC 3406 |
Uniform Resource Names (URN) Namespace Definition Mechanisms
References Referenced by |
Best Current Practice | Reference |