References from RFC 8464
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 14 |
References Referenced by |
normatively references | ||
draft-atarius-dispatch-meid-urn-as-instanceid |
Using the Mobile Equipment Identity (MEID) URN as an Instance ID
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 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 | normatively 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 5626 |
Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)
References Referenced by |
Proposed Standard | normatively 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 8141 |
Uniform Resource Names (URNs)
References Referenced by |
Proposed Standard | normatively references | |
STD 66 |
References Referenced by |
normatively references | ||
STD 68 |
References Referenced by |
normatively references |