RFC 5964 on Specifying Holes in Location-to-Service Translation (LoST) Service Boundaries
rfc-editor@rfc-editor.org Thu, 26 August 2010 17:01 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 571A23A6AB2; Thu, 26 Aug 2010 10:01:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.047
X-Spam-Level:
X-Spam-Status: No, score=-102.047 tagged_above=-999 required=5 tests=[AWL=-0.047, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4ZPUKcqbxMxc; Thu, 26 Aug 2010 10:01:00 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 508B43A69D2; Thu, 26 Aug 2010 10:01:00 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 184E5E065E; Thu, 26 Aug 2010 10:01:33 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5964 on Specifying Holes in Location-to-Service Translation (LoST) Service Boundaries
From: rfc-editor@rfc-editor.org
Message-Id: <20100826170133.184E5E065E@rfc-editor.org>
Date: Thu, 26 Aug 2010 10:01:33 -0700
Cc: ecrit@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 26 Aug 2010 17:01:01 -0000
A new Request for Comments is now available in online RFC libraries. RFC 5964 Title: Specifying Holes in Location-to-Service Translation (LoST) Service Boundaries Author: J. Winterbottom, M. Thomson Status: Standards Track Stream: IETF Date: August 2010 Mailbox: james.winterbottom@andrew.com, martin.thomson@andrew.com Pages: 11 Characters: 21269 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ecrit-specifying-holes-03.txt URL: http://www.rfc-editor.org/rfc/rfc5964.txt This document describes how holes can be specified in geodetic service boundaries. One means of implementing a search solution in a service database, such as one might provide with a Location-to- Service Translation (LoST) server, is described. [STANDARDS TRACK] This document is a product of the Emergency Context Resolution with Internet Technologies Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. 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