References from rfc6444

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
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
RFC 5031 A Uniform Resource Name (URN) for Emergency and Other Well-Known Services
Refs Ref'd by
Proposed Standard normatively references
RFC 5069 Security Threats and Requirements for Emergency Call Marking and Mapping
Refs Ref'd by
Informational normatively references
RFC 5222 LoST: A Location-to-Service Translation Protocol
Refs Ref'd by
Proposed Standard normatively references
RFC 5687 GEOPRIV Layer 7 Location Configuration Protocol: Problem Statement and Requirements
Refs Ref'd by
Informational normatively references
RFC 5741 RFC Streams, Headers, and Boilerplates
Refs Ref'd by
Informational Possible Reference
RFC 5808 Requirements for a Location-by-Reference Mechanism
Refs Ref'd by
Informational normatively references
RFC 5964 Specifying Holes in Location-to-Service Translation (LoST) Service Boundaries
Refs Ref'd by
Proposed Standard normatively references
RFC 5985 HTTP-Enabled Location Delivery (HELD)
Refs Ref'd by
Proposed Standard normatively references
RFC 6442 Location Conveyance for the Session Initiation Protocol
Refs Ref'd by
Proposed Standard normatively references
RFC 6443 Framework for Emergency Calling Using Internet Multimedia
Refs Ref'd by
Informational normatively references