References from draft-ietf-core-dev-urn

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 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
draft-atarius-dispatch-meid-urn A URN Namespace for Device Identity and Mobile Equipment Identity (MEID)
References Referenced by
Informational informatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
RFC 2578 Structure of Management Information Version 2 (SMIv2)
References Referenced by
Internet Standard normatively references
RFC 2616 Hypertext Transfer Protocol -- HTTP/1.1
References Referenced by
Draft Standard informatively references
RFC 3261 SIP: Session Initiation Protocol
References Referenced by
Proposed Standard informatively references
RFC 3406 Uniform Resource Names (URN) Namespace Definition Mechanisms
References Referenced by
Best Current Practice normatively references
RFC 3986 Uniform Resource Identifier (URI): Generic Syntax
References Referenced by
Internet Standard normatively references
RFC 4122 A Universally Unique IDentifier (UUID) URN Namespace
References Referenced by
Proposed Standard informatively references
RFC 4627 The application/json Media Type for JavaScript Object Notation (JSON)
References Referenced by
Informational informatively references
RFC 5226 Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by
Best Current Practice normatively references
RFC 5234 Augmented BNF for Syntax Specifications: ABNF
References Referenced by
Internet Standard normatively references
RFC 6920 Naming Things with Hashes
References Referenced by
Proposed Standard informatively references
RFC 7252 The Constrained Application Protocol (CoAP)
References Referenced by
Proposed Standard informatively references
RFC 7254 A Uniform Resource Name Namespace for the Global System for Mobile Communications Association (GSMA) and the International Mobile station Equipment Identity (IMEI)
References Referenced by
Informational informatively references
RFC 7721 Security and Privacy Considerations for IPv6 Address Generation Mechanisms
References Referenced by
Informational informatively references
RFC 8141 Uniform Resource Names (URNs)
References Referenced by
Proposed Standard normatively references
RFC 8259 The JavaScript Object Notation (JSON) Data Interchange Format
References Referenced by
Internet Standard informatively references
RFC 8428 Sensor Measurement Lists (SenML)
References Referenced by
Proposed Standard informatively references
STD 58 Conformance Statements for SMIv2
References Referenced by
Internet Standard normatively references
STD 66 Uniform Resource Identifier (URI): Generic Syntax
References Referenced by
Internet Standard normatively references
STD 68 Augmented BNF for Syntax Specifications: ABNF
References Referenced by
Internet Standard normatively references
STD 90 The JavaScript Object Notation (JSON) Data Interchange Format
References Referenced by
Internet Standard informatively references