References from rfc7840

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
References Referenced by
Best Current Practice normatively references
BCP 181 Best Current Practice for Communications Services in Support of Emergency Calling
References Referenced by
Best Current Practice normatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
RFC 3688 The IETF XML Registry
References Referenced by
Best Current Practice 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 5582 Location-to-URL Mapping Architecture and Framework
References Referenced by
Informational informatively references
RFC 5687 GEOPRIV Layer 7 Location Configuration Protocol: Problem Statement and Requirements
References Referenced by
Informational informatively references
RFC 5985 HTTP-Enabled Location Delivery (HELD)
References Referenced by
Proposed Standard normatively references
RFC 5986 Discovering the Local Location Information Server (LIS)
References Referenced by
Proposed Standard informatively references
RFC 6155 Use of Device Identity in HTTP-Enabled Location Delivery (HELD)
References Referenced by
Proposed Standard informatively references
RFC 6443 Framework for Emergency Calling Using Internet Multimedia
References Referenced by
Informational informatively references
RFC 6881 Best Current Practice for Communications Services in Support of Emergency Calling
References Referenced by
Best Current Practice normatively references
RFC 6915 Flow Identity Extension for HTTP-Enabled Location Delivery (HELD)
References Referenced by
Proposed Standard informatively references
RFC 7216 Location Information Server (LIS) Discovery Using IP Addresses and Reverse DNS
References Referenced by
Proposed Standard informatively references