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