RFC 6197 on Location-to-Service Translation (LoST) Service List Boundary Extension
rfc-editor@rfc-editor.org Thu, 21 April 2011 05:14 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfc.amsl.com
Delivered-To: ietf-announce@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id E506CE0791; Wed, 20 Apr 2011 22:14:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.337
X-Spam-Level:
X-Spam-Status: No, score=-102.337 tagged_above=-999 required=5 tests=[AWL=0.263, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b-GEoPwM1xeM; Wed, 20 Apr 2011 22:14:50 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfc.amsl.com (Postfix) with ESMTP id 3E9C4E07D1; Wed, 20 Apr 2011 22:14:50 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 66ED4E077E; Wed, 20 Apr 2011 22:14:49 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6197 on Location-to-Service Translation (LoST) Service List Boundary Extension
From: rfc-editor@rfc-editor.org
Message-Id: <20110421051449.66ED4E077E@rfc-editor.org>
Date: Wed, 20 Apr 2011 22:14:49 -0700
Cc: ecrit@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Apr 2011 05:14:51 -0000
A new Request for Comments is now available in online RFC libraries. RFC 6197 Title: Location-to-Service Translation (LoST) Service List Boundary Extension Author: K. Wolf Status: Experimental Stream: IETF Date: April 2011 Mailbox: karlheinz.wolf@nic.at Pages: 15 Characters: 27562 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ecrit-lost-servicelistboundary-05.txt URL: http://www.rfc-editor.org/rfc/rfc6197.txt Location-to-Service Translation (LoST) maps service identifiers and location information to service contact URIs. If a LoST client wants to discover available services for a particular location, it will perform a <listServicesByLocation> query to the LoST server. However, the LoST server, in its response, does not provide context information; that is, it does not provide any additional information about the geographical region within which the returned list of services is considered valid. Therefore, this document defines a Service List Boundary that returns a local context along with the list of services returned, in order to assist the client in not missing a change in available services when moving. 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