draft-ietf-geopriv-lis-discovery-11.txt   draft-ietf-geopriv-lis-discovery-12.txt 
GEOPRIV M. Thomson GEOPRIV M. Thomson
Internet-Draft J. Winterbottom Internet-Draft J. Winterbottom
Intended status: Standards Track Andrew Intended status: Standards Track Andrew
Expires: November 8, 2009 May 7, 2009 Expires: May 12, 2010 November 8, 2009
Discovering the Local Location Information Server (LIS) Discovering the Local Location Information Server (LIS)
draft-ietf-geopriv-lis-discovery-11 draft-ietf-geopriv-lis-discovery-12
Abstract
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.
Status of This Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 32 skipping to change at page 1, line 42
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on November 8, 2009. This Internet-Draft will expire on May 12, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Abstract include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
Discovery of the correct Location Information Server (LIS) in the described in the BSD License.
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.
Table of Contents Table of Contents
1. Introduction and Overview . . . . . . . . . . . . . . . . . . 3 1. Introduction and Overview . . . . . . . . . . . . . . . . . . 3
1.1. Discovery Procedure Overview . . . . . . . . . . . . . . . 3 1.1. Discovery Procedure Overview . . . . . . . . . . . . . . . 3
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
2. LIS Discovery Procedure . . . . . . . . . . . . . . . . . . . 4 2. LIS Discovery Procedure . . . . . . . . . . . . . . . . . . . 4
2.1. Residential Gateways . . . . . . . . . . . . . . . . . . . 5 2.1. Residential Gateways . . . . . . . . . . . . . . . . . . . 5
2.2. Virtual Private Networks (VPNs) . . . . . . . . . . . . . 6 2.2. Virtual Private Networks (VPNs) . . . . . . . . . . . . . 6
3. Access Network Domain Name DHCP Option . . . . . . . . . . . . 7 3. Access Network Domain Name DHCP Option . . . . . . . . . . . . 7
skipping to change at page 6, line 40 skipping to change at page 6, line 40
[I-D.ietf-dhc-container-opt] might be used by an access network [I-D.ietf-dhc-container-opt] might be used by an access network
provider to convey configuration information to a residential gateway provider to convey configuration information to a residential gateway
for use by the devices it serves. Support and use of this option is for use by the devices it serves. Support and use of this option is
RECOMMENDED for both residential gateways and devices. Option values RECOMMENDED for both residential gateways and devices. Option values
found within the container MUST be used after values that are found within the container MUST be used after values that are
directly in the DHCP response. directly in the DHCP response.
2.2. Virtual Private Networks (VPNs) 2.2. Virtual Private Networks (VPNs)
LIS discovery over a VPN network interface SHOULD NOT be performed. A Device MUST avoid performing LIS discovery over a VPN network
A LIS discovered in this way is unlikely to have the information interface unless discovery on other interfaces is unsuccessful. A
LIS discovered in this way is unlikely to have the information
necessary to determine an accurate location. necessary to determine an accurate location.
Not all interfaces connected to a VPN can be detected by devices or Not all interfaces connected to a VPN can be detected by devices or
the software running on them. A LIS MUST NOT provide location the software running on them. In these cases, it might be that a LIS
information in response to requests that it can identify as on the remote side of a VPN is inadvertently discovered. A LIS MUST
originating from a device on the remote end of a VPN tunnel, unless NOT provide location information in response to requests that it can
it is able to accurately determine location. The "notLocatable" HELD identify as originating from a device on the remote end of a VPN
error code can be used to indicate to a device that discovery has tunnel, unless it is able to accurately determine location. The
revealed an unsuitable LIS. This ensures that even if a device "notLocatable" HELD error code can be used to indicate to a device
discovers a LIS over the VPN, it does not rely on a LIS that is that discovery has revealed an unsuitable LIS. This ensures that
unable to provide accurate location information. even if a device discovers a LIS over the VPN, it does not rely on a
LIS that is unable to provide accurate location information.
3. Access Network Domain Name DHCP Option 3. Access Network Domain Name DHCP Option
DHCP provides a direct means for the access network provider to DHCP provides a direct means for the access network provider to
configure a device. The access network domain name option identifies configure a device. The access network domain name option identifies
a domain name that is suitable for service discovery within the a domain name that is suitable for service discovery within the
access network. This domain name is used as input to the U-NAPTR access network. This domain name is used as input to the U-NAPTR
resolution process for LIS discovery. resolution process for LIS discovery.
The domain name provided in this option is one owned by the access The domain name provided in this option is one owned by the access
skipping to change at page 12, line 34 skipping to change at page 12, line 34
Author/Change controller: The IESG Author/Change controller: The IESG
6.3. Registration of a Location Server Application Protocol Tag for 6.3. Registration of a Location Server Application Protocol Tag for
HELD HELD
This section registers a new S-NAPTR/U-NAPTR Application Protocol tag This section registers a new S-NAPTR/U-NAPTR Application Protocol tag
for the HELD [I-D.ietf-geopriv-http-location-delivery] protocol, as for the HELD [I-D.ietf-geopriv-http-location-delivery] protocol, as
mandated by [RFC3958]. mandated by [RFC3958].
Application Service Tag: HELD Application Protocol Tag: HELD
Intended Usage: Identifies the HELD protocol. Intended Usage: Identifies the HELD protocol.
Applicable Service Tag(s): LIS Applicable Service Tag(s): LIS
Terminal NAPTR Record Type(s): U Terminal NAPTR Record Type(s): U
Defining Publication: RFCXXXX Defining Publication: RFCXXXX
Related Publications: HELD [I-D.ietf-geopriv-http-location-delivery] Related Publications: HELD [I-D.ietf-geopriv-http-location-delivery]
skipping to change at page 14, line 25 skipping to change at page 14, line 25
Location Using URIs and Location Using URIs and
the Dynamic Delegation the Dynamic Delegation
Discovery Service (DDDS)", Discovery Service (DDDS)",
RFC 4848, April 2007. RFC 4848, April 2007.
[I-D.ietf-geopriv-http-location-delivery] Barnes, M., Winterbottom, [I-D.ietf-geopriv-http-location-delivery] Barnes, M., Winterbottom,
J., Thomson, M., and B. J., Thomson, M., and B.
Stark, "HTTP Enabled Stark, "HTTP Enabled
Location Delivery (HELD)", Location Delivery (HELD)",
draft-ietf-geopriv-http- draft-ietf-geopriv-http-
location-delivery-13 (work location-delivery-16 (work
in progress), in progress), August 2009.
February 2009.
[I-D.ietf-dhc-container-opt] Droms, R., "Container [I-D.ietf-dhc-container-opt] Droms, R., "Container
Option for Server Option for Server
Configuration", draft- Configuration", draft-
ietf-dhc-container-opt-05 ietf-dhc-container-opt-05
(work in progress), (work in progress),
March 2009. March 2009.
[RFC2119] Bradner, S., "Key words [RFC2119] Bradner, S., "Key words
for use in RFCs to for use in RFCs to
skipping to change at page 15, line 36 skipping to change at page 15, line 35
Host Configuration Host Configuration
Protocol (DHCP)", Protocol (DHCP)",
RFC 5223, August 2008. RFC 5223, August 2008.
[I-D.ietf-geopriv-l7-lcp-ps] Tschofenig, H. and H. [I-D.ietf-geopriv-l7-lcp-ps] Tschofenig, H. and H.
Schulzrinne, "GEOPRIV Schulzrinne, "GEOPRIV
Layer 7 Location Layer 7 Location
Configuration Protocol; Configuration Protocol;
Problem Statement and Problem Statement and
Requirements", draft-ietf- Requirements", draft-ietf-
geopriv-l7-lcp-ps-09 (work geopriv-l7-lcp-ps-10 (work
in progress), in progress), July 2009.
February 2009.
[I-D.ietf-geopriv-lbyr-requirements] Marshall, R., [I-D.ietf-geopriv-lbyr-requirements] Marshall, R.,
"Requirements for a "Requirements for a
Location-by-Reference Location-by-Reference
Mechanism", draft-ietf- Mechanism", draft-ietf-
geopriv-lbyr-requirements- geopriv-lbyr-requirements-
07 (work in progress), 08 (work in progress),
February 2009. September 2009.
Authors' Addresses Authors' Addresses
Martin Thomson Martin Thomson
Andrew Andrew
PO Box U40 PO Box U40
Wollongong University Campus, NSW 2500 Wollongong University Campus, NSW 2500
AU AU
Phone: +61 2 4221 2915 Phone: +61 2 4221 2915
 End of changes. 10 change blocks. 
36 lines changed or deleted 40 lines changed or added

This html diff was produced by rfcdiff 1.37a. The latest version is available from http://tools.ietf.org/tools/rfcdiff/