Skip to main content

References from draft-saintandre-urnbis-3406bis

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.

Reference type help

Document Title Status Type Downref
BCP 14
References Referenced by
normatively references
BCP 178
References Referenced by
informatively references
BCP 26
References Referenced by
normatively references
BCP 32
References Referenced by
informatively references
BCP 33
References Referenced by
informatively references
BCP 66
References Referenced by
informatively references
draft-saintandre-urnbis-2141bis Uniform Resource Name (URN) Syntax
References Referenced by
normatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
RFC 2276 Architectural Principles of Uniform Resource Name Resolution
References Referenced by
Informational Possible Reference
RFC 2288 Using Existing Bibliographic Identifiers as Uniform Resource Names
References Referenced by
Informational Possible Reference
RFC 2606 Reserved Top Level DNS Names
References Referenced by
Best Current Practice informatively references
RFC 2611 URN Namespace Definition Mechanisms
References Referenced by
Best Current Practice informatively references
RFC 3406 Uniform Resource Names (URN) Namespace Definition Mechanisms
References Referenced by
Best Current Practice informatively references
RFC 5226 Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by
Best Current Practice normatively references
RFC 6648 Deprecating the "X-" Prefix and Similar Constructs in Application Protocols
References Referenced by
Best Current Practice informatively references