Skip to main content

References to draft-ietf-ecrit-requirements

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.

Showing RFCs and active Internet-Drafts, sorted by reference type, then document name.

Document Title Status Type Downref
RFC 5687
As rfc5012
GEOPRIV Layer 7 Location Configuration Protocol: Problem Statement and Requirements
References Referenced by
Informational normatively references
RFC 5031
As rfc5012
A Uniform Resource Name (URN) for Emergency and Other Well-Known Services
References Referenced by
Proposed Standard informatively references
RFC 5069
As rfc5012
Security Threats and Requirements for Emergency Call Marking and Mapping
References Referenced by
Informational informatively references
RFC 5222
As rfc5012
LoST: A Location-to-Service Translation Protocol
References Referenced by
Proposed Standard informatively references
RFC 5223
As rfc5012
Discovering Location-to-Service Translation (LoST) Servers Using the Dynamic Host Configuration Protocol (DHCP)
References Referenced by
Proposed Standard informatively references
RFC 5582
As rfc5012
Location-to-URL Mapping Architecture and Framework
References Referenced by
Informational informatively references
RFC 6443
As rfc5012
Framework for Emergency Calling Using Internet Multimedia
References Referenced by
Informational informatively references
RFC 6739
As rfc5012
Synchronizing Service Boundaries and <mapping> Elements Based on the Location-to-Service Translation (LoST) Protocol
References Referenced by
Experimental informatively references
RFC 6848
As rfc5012
Specifying Civic Address Extensions in the Presence Information Data Format Location Object (PIDF-LO)
References Referenced by
Proposed Standard informatively references
RFC 6881
As rfc5012
Best Current Practice for Communications Services in Support of Emergency Calling
References Referenced by
Best Current Practice informatively references
RFC 7090
As rfc5012
Public Safety Answering Point (PSAP) Callback
References Referenced by
Proposed Standard informatively references
RFC 7216
As rfc5012
Location Information Server (LIS) Discovery Using IP Addresses and Reverse DNS
References Referenced by
Proposed Standard informatively references
RFC 7406
As rfc5012
Extensions to the Emergency Services Architecture for Dealing With Unauthenticated and Unauthorized Devices
References Referenced by
Informational informatively references
RFC 7852
As rfc5012
Additional Data Related to an Emergency Call
References Referenced by
Proposed Standard informatively references
RFC 8147
As rfc5012
Next-Generation Pan-European eCall
References Referenced by
Proposed Standard informatively references
RFC 8148
As rfc5012
Next-Generation Vehicle-Initiated Emergency Calls
References Referenced by
Proposed Standard informatively references