References from rfc8465

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
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	normatively references
RFC 2119	Key words for use in RFCs to Indicate Requirement Levels References Referenced by	Best Current Practice	normatively references
RFC 3261	SIP: Session Initiation Protocol References Referenced by	Proposed Standard	normatively references
RFC 3680	A Session Initiation Protocol (SIP) Event Package for Registrations References Referenced by	Proposed Standard	normatively references
RFC 4122	A Universally Unique IDentifier (UUID) URN Namespace References Referenced by	Proposed Standard	normatively references
RFC 4346	The Transport Layer Security (TLS) Protocol Version 1.1 References Referenced by	Historic	normatively references
RFC 5626	Managing Client-Initiated Connections in the Session Initiation Protocol (SIP) References Referenced by	Proposed Standard	normatively references
RFC 5627	Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP) References Referenced by	Proposed Standard	normatively references
RFC 7255	Using the International Mobile station Equipment Identity (IMEI) Uniform Resource Name (URN) as an Instance ID References Referenced by	Informational	informatively references
RFC 8141	Uniform Resource Names (URNs) References Referenced by	Proposed Standard	normatively references
RFC 8174	Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words References Referenced by	Best Current Practice	normatively references