RFC 5986 on Discovering the Local Location Information Server (LIS)

rfc-editor@rfc-editor.org Tue, 07 September 2010 16:23 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 14F563A6A4D; Tue, 7 Sep 2010 09:23:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.037
X-Spam-Level:
X-Spam-Status: No, score=-102.037 tagged_above=-999 required=5 tests=[AWL=-0.037, 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 IcesLJs028xi; Tue, 7 Sep 2010 09:23:54 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 0AC7F3A6A93; Tue, 7 Sep 2010 09:23:54 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A10DCE06E4; Tue, 7 Sep 2010 09:24:22 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5986 on Discovering the Local Location Information Server (LIS)
From: rfc-editor@rfc-editor.org
Message-Id: <20100907162422.A10DCE06E4@rfc-editor.org>
Date: Tue, 7 Sep 2010 09:24:22 -0700 (PDT)
Cc: geopriv@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: Tue, 07 Sep 2010 16:23:55 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5986

        Title:      Discovering the Local Location Information 
                    Server (LIS) 
        Author:     M. Thomson, J. Winterbottom
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2010
        Mailbox:    martin.thomson@andrew.com, 
                    james.winterbottom@andrew.com
        Pages:      16
        Characters: 34450
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-geopriv-lis-discovery-15.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5986.txt

Discovery of the correct Location Information Server (LIS) in the
local access network is necessary for Devices that wish to acquire
location information from the network.  A method is described for the
discovery of a LIS in the access network serving a Device.  Dynamic
Host Configuration Protocol (DHCP) options for IP versions 4 and 6
are defined that specify a domain name.  This domain name is then
used as input to a URI-enabled NAPTR (U-NAPTR) resolution process.
[STANDARDS TRACK]

This document is a product of the Geographic Location/Privacy 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