Synchronizing Service Boundaries and <mapping> Elements Based on the Location-to-Service Translation Protocol
RFC 6739, “Synchronizing Service Boundaries and <mapping> Elements Based on the Location-to-Service Translation Protocol”, is an Experimental document published in October 2012 by H. Schulzrinne, H. Tschofenig. It has since been updated by RFC 8996. The canonical text is published by the RFC Editor.
Abstract
The Location-to-Service Translation (LoST) protocol is an XML-based protocol for mapping service identifiers and geodetic or civic location information to service URIs and service boundaries. In particular, it can be used to determine the location-appropriate Public Safety Answering Point (PSAP) for emergency services.
The <mapping> element in the LoST protocol specification encapsulates information about service boundaries and circumscribes the region within which all locations map to the same service Uniform Resource Identifier (URI) or set of URIs for a given service.
This document defines an XML protocol to exchange these mappings between two nodes. This mechanism is designed for the exchange of authoritative <mapping> elements between two entities. Exchanging cached <mapping> elements, i.e., non-authoritative elements, is possible but not envisioned. Even though the <mapping> element format is reused from the LoST specification, the mechanism in this document can be used without the LoST protocol. This document defines an Experimental Protocol for the Internet community.
What “Experimental” means
Describes a specification that is part of a research or development effort, published so the community can gain experience with it.
The canonical text of RFC 6739 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6738 Diameter IKEv2 SK: Using Shared Keys to Support Interaction between IKEv2 Servers and Diameter Servers
- RFC 6740 Identifier-Locator Network Protocol Architectural Description
- RFC 6737 The Diameter Capabilities Update Application
- RFC 6741 Identifier-Locator Network Protocol Engineering Considerations
- RFC 6736 Diameter Network Address and Port Translation Control Application
- RFC 6742 DNS Resource Records for the Identifier-Locator Network Protocol
- RFC 6735 Diameter Priority Attribute-Value Pairs
- RFC 6743 ICMP Locator Update Message for the Identifier-Locator Network Protocol for IPv6