References from draft-rosen-ecrit-emergency-registries

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
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	informatively references
RFC 3550	RTP: A Transport Protocol for Real-Time Applications References Referenced by	Internet Standard	informatively references
RFC 3840	Indicating User Agent Capabilities in the Session Initiation Protocol (SIP) References Referenced by	Proposed Standard	informatively references
RFC 5031	A Uniform Resource Name (URN) for Emergency and Other Well-Known Services References Referenced by	Proposed Standard	informatively references
RFC 5222	LoST: A Location-to-Service Translation Protocol References Referenced by	Proposed Standard	informatively references
RFC 5727	Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area References Referenced by	Best Current Practice	informatively references
RFC 6061	Uniform Resource Name (URN) Namespace for the National Emergency Number Association (NENA) References Referenced by	Informational	informatively references
RFC 6443	Framework for Emergency Calling Using Internet Multimedia References Referenced by	Informational	informatively references
RFC 8126	Guidelines for Writing an IANA Considerations Section in RFCs References Referenced by	Best Current Practice	informatively references
RFC 8216	HTTP Live Streaming References Referenced by	Informational	informatively references