References to draft-ietf-ecrit-lost

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
draft-ietf-ecrit-similar-location As rfc5222	A LoST extension to return complete and similar location info References Referenced by	Proposed Standard	normatively references
RFC 5582 As rfc5222	Location-to-URL Mapping Architecture and Framework References Referenced by	Informational	normatively references
RFC 5964 As rfc5222	Specifying Holes in Location-to-Service Translation (LoST) Service Boundaries References Referenced by	Proposed Standard	normatively references
RFC 6197 As rfc5222	Location-to-Service Translation (LoST) Service List Boundary Extension References Referenced by	Experimental	normatively references
RFC 6444 As rfc5222	Location Hiding: Problem Statement and Requirements References Referenced by	Informational	normatively references
RFC 6451 As rfc5222	Location-to-Service Translation (LoST) Protocol Extensions References Referenced by	Experimental	normatively references
RFC 6739 As rfc5222	Synchronizing Service Boundaries and <mapping> Elements Based on the Location-to-Service Translation (LoST) Protocol References Referenced by	Experimental	normatively references
RFC 6848 As rfc5222	Specifying Civic Address Extensions in the Presence Information Data Format Location Object (PIDF-LO) References Referenced by	Proposed Standard	normatively references
RFC 6881 As rfc5222	Best Current Practice for Communications Services in Support of Emergency Calling References Referenced by	Best Current Practice	normatively references
RFC 7406 As rfc5222	Extensions to the Emergency Services Architecture for Dealing With Unauthenticated and Unauthorized Devices References Referenced by	Informational	normatively references
RFC 8917 As rfc5222	The LoST-Validation Straightforward-Naming Authority PoinTeR (S-NAPTR) Application Service Tag References Referenced by	Proposed Standard	normatively references
RFC 9036 As rfc5222	Changing the Location-to-Service Translation (LoST) Location Profiles Registry Policy References Referenced by	Proposed Standard	normatively references
draft-gundavelli-dispatch-e911-wifi As rfc5222	Emergency Communication Services over Wi-Fi Access Networks References Referenced by		informatively references
RFC 5223 As rfc5222	Discovering Location-to-Service Translation (LoST) Servers Using the Dynamic Host Configuration Protocol (DHCP) References Referenced by	Proposed Standard	informatively references
RFC 5638 As rfc5222	Simple SIP Usage Scenario for Applications in the Endpoints References Referenced by	Informational	informatively references
RFC 5986 As rfc5222	Discovering the Local Location Information Server (LIS) References Referenced by	Proposed Standard	informatively references
RFC 6280 As rfc5222	An Architecture for Location and Location Privacy in Internet Applications References Referenced by	Best Current Practice	informatively references
RFC 6443 As rfc5222	Framework for Emergency Calling Using Internet Multimedia References Referenced by	Informational	informatively references
RFC 7090 As rfc5222	Public Safety Answering Point (PSAP) Callback References Referenced by	Proposed Standard	informatively references
RFC 7459 As rfc5222	Representation of Uncertainty and Confidence in the Presence Information Data Format Location Object (PIDF-LO) References Referenced by	Proposed Standard	informatively references
RFC 7840 As rfc5222	A Routing Request Extension for the HTTP-Enabled Location Delivery (HELD) Protocol References Referenced by	Proposed Standard	informatively references
RFC 8876 As rfc5222	Non-interactive Emergency Calls References Referenced by	Proposed Standard	informatively references