References from rfc8465

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.

Reference type help

Document Title Status Type Downref
BCP 14 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
draft-atarius-dispatch-meid-urn A URN Namespace for Device Identity and Mobile Equipment Identity (MEID)
Refs Ref'd by
Informational normatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
RFC 3261 SIP: Session Initiation Protocol
Refs Ref'd by
Proposed Standard normatively references
RFC 3680 A Session Initiation Protocol (SIP) Event Package for Registrations
Refs Ref'd by
Proposed Standard normatively references
RFC 4122 A Universally Unique IDentifier (UUID) URN Namespace
Refs Ref'd by
Proposed Standard normatively references
RFC 4346 The Transport Layer Security (TLS) Protocol Version 1.1
Refs Ref'd by
Proposed Standard normatively references
RFC 5626 Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)
Refs Ref'd by
Proposed Standard normatively references
RFC 5627 Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP)
Refs Ref'd by
Proposed Standard normatively references
RFC 7255 Using the International Mobile station Equipment Identity (IMEI) Uniform Resource Name (URN) as an Instance ID
Refs Ref'd by
Informational informatively references
RFC 8141 Uniform Resource Names (URNs)
Refs Ref'd by
Proposed Standard normatively references
RFC 8174 Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Refs Ref'd by
Best Current Practice normatively references