[Ecrit] RFC 6739 on Synchronizing Service Boundaries and <mapping> Elements Based on the Location-to-Service Translation (LoST) Protocol
rfc-editor@rfc-editor.org Thu, 25 October 2012 04:20 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ecrit@ietfa.amsl.com
Delivered-To: ecrit@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0395B21F8540; Wed, 24 Oct 2012 21:20:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.227
X-Spam-Level:
X-Spam-Status: No, score=-102.227 tagged_above=-999 required=5 tests=[AWL=0.373, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XtsUT9GmSE1T; Wed, 24 Oct 2012 21:20:43 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 8205121F84BF; Wed, 24 Oct 2012 21:20:43 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 2140F72E038; Wed, 24 Oct 2012 21:14:57 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20121025041457.2140F72E038@rfc-editor.org>
Date: Wed, 24 Oct 2012 21:14:57 -0700
Cc: ecrit@ietf.org, rfc-editor@rfc-editor.org
Subject: [Ecrit] RFC 6739 on Synchronizing Service Boundaries and <mapping> Elements Based on the Location-to-Service Translation (LoST) Protocol
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ecrit>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 04:20:44 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6739
Title: Synchronizing Service Boundaries and <mapping>
Elements Based on the Location-to-Service Translation
(LoST) Protocol
Author: H. Schulzrinne, H. Tschofenig
Status: Experimental
Stream: IETF
Date: October 2012
Mailbox: hgs+ecrit@cs.columbia.edu,
Hannes.Tschofenig@gmx.net
Pages: 25
Characters: 52011
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-ecrit-lost-sync-18.txt
URL: http://www.rfc-editor.org/rfc/rfc6739.txt
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.
This document is a product of the Emergency Context Resolution with Internet Technologies Working Group of the IETF.
EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community. It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC