draft-ietf-geopriv-lis-discovery-14.txt   draft-ietf-geopriv-lis-discovery-15.txt 
GEOPRIV M. Thomson GEOPRIV M. Thomson
Internet-Draft J. Winterbottom Internet-Draft J. Winterbottom
Intended status: Standards Track Andrew Corporation Intended status: Standards Track Andrew Corporation
Expires: August 29, 2010 February 25, 2010 Expires: September 9, 2010 March 8, 2010
Discovering the Local Location Information Server (LIS) Discovering the Local Location Information Server (LIS)
draft-ietf-geopriv-lis-discovery-14 draft-ietf-geopriv-lis-discovery-15
Abstract Abstract
Discovery of the correct Location Information Server (LIS) in the Discovery of the correct Location Information Server (LIS) in the
local access network is necessary for devices that wish to acquire local access network is necessary for devices that wish to acquire
location information from the network. A method is described for the location information from the network. A method is described for the
discovery of a LIS in the access network serving a device. Dynamic discovery of a LIS in the access network serving a device. Dynamic
Host Configuration Protocol (DHCP) options for IP versions 4 and 6 Host Configuration Protocol (DHCP) options for IP versions 4 and 6
are defined that specify a domain name. This domain name is then are defined that specify a domain name. This domain name is then
used as input to a URI-enabled NAPTR (U-NAPTR) resolution process. used as input to a URI-enabled NAPTR (U-NAPTR) resolution process.
skipping to change at page 1, line 42 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 August 29, 2010. This Internet-Draft will expire on September 9, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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 Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 26 skipping to change at page 2, line 26
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 . . . . . . . . . . . . . . . . . . . 6 2.1. Residential Gateways . . . . . . . . . . . . . . . . . . . 6
2.2. Virtual Private Networks (VPNs) . . . . . . . . . . . . . 7 2.2. Virtual Private Networks (VPNs) . . . . . . . . . . . . . 7
3. Determining a Domain Name . . . . . . . . . . . . . . . . . . 8 3. Determining a Domain Name . . . . . . . . . . . . . . . . . . 8
3.1. Domain Name Encoding . . . . . . . . . . . . . . . . . . . 8 3.1. Domain Name Encoding . . . . . . . . . . . . . . . . . . . 8
3.2. Access Network Domain Name DHCPv4 Option . . . . . . . . . 9 3.2. Access Network Domain Name DHCPv4 Option . . . . . . . . . 9
3.3. Access Network Domain Name DHCPv6 Option . . . . . . . . . 9 3.3. Access Network Domain Name DHCPv6 Option . . . . . . . . . 9
3.4. Alternative Domain Names . . . . . . . . . . . . . . . . . 10 3.4. Alternative Domain Names . . . . . . . . . . . . . . . . . 10
4. U-NAPTR Resolution of a LIS URI . . . . . . . . . . . . . . . 10 4. U-NAPTR Resolution of a LIS URI . . . . . . . . . . . . . . . 11
5. Security Considerations . . . . . . . . . . . . . . . . . . . 12 5. Security Considerations . . . . . . . . . . . . . . . . . . . 12
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
6.1. Registration of DHCPv4 and DHCPv6 Option Codes . . . . . . 13 6.1. Registration of DHCPv4 and DHCPv6 Option Codes . . . . . . 13
6.2. Registration of a Location Server Application Service 6.2. Registration of a Location Server Application Service
Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
6.3. Registration of a Location Server Application Protocol 6.3. Registration of a Location Server Application Protocol
Tag for HELD . . . . . . . . . . . . . . . . . . . . . . . 14 Tag for HELD . . . . . . . . . . . . . . . . . . . . . . . 14
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
8.1. Normative References . . . . . . . . . . . . . . . . . . . 14 8.1. Normative References . . . . . . . . . . . . . . . . . . . 14
skipping to change at page 8, line 48 skipping to change at page 8, line 48
octets or less. To simplify implementations, the total length of a octets or less. To simplify implementations, the total length of a
domain name (i.e., label octets and label length octets) is domain name (i.e., label octets and label length octets) is
restricted to 255 octets or less. restricted to 255 octets or less.
For example, the domain "example.com." is encoded in 13 octets as: For example, the domain "example.com." is encoded in 13 octets as:
+---+---+---+---+---+---+---+---+---+---+---+---+---+ +---+---+---+---+---+---+---+---+---+---+---+---+---+
| 7 | e | x | a | m | p | l | e | 3 | c | o | m | 0 | | 7 | e | x | a | m | p | l | e | 3 | c | o | m | 0 |
+---+---+---+---+---+---+---+---+---+---+---+---+---+ +---+---+---+---+---+---+---+---+---+---+---+---+---+
Note that the length field in the either option represents the length Note that the length field in either option represents the length of
of the entire domain name encoding, whereas the length fields in the the entire domain name encoding, whereas the length fields in the
domain name encoding is the length of a single domain name label. domain name encoding is the length of a single domain name label.
3.2. Access Network Domain Name DHCPv4 Option 3.2. Access Network Domain Name DHCPv4 Option
This section defines a DHCP for IPv4 (DHCPv4) option for the domain This section defines a DHCP for IPv4 (DHCPv4) option for the domain
name associated with the access network. name associated with the access network.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 10, line 35 skipping to change at page 10, line 35
If a device knows one or more alternative domain names that might be If a device knows one or more alternative domain names that might be
used for discovery, it MAY repeat the U-NAPTR process using those used for discovery, it MAY repeat the U-NAPTR process using those
domain names as input. For instance, static configuration of a domain names as input. For instance, static configuration of a
device might be used to provide a device with a domain name. device might be used to provide a device with a domain name.
DHCPv4 option 15 [RFC2132] provides an indication of the domain name DHCPv4 option 15 [RFC2132] provides an indication of the domain name
that a host uses when resolving hostnames in DNS. This option is that a host uses when resolving hostnames in DNS. This option is
used when the DHCPv4 access domain name is not available. used when the DHCPv4 access domain name is not available.
DHCPv4 option 15 might not be suitable for some network deployments.
For instance, a global enterprise could operate multiple sites, with
devices at all sites using the same value for option 15. In this
type of deployment, it might be desirable to discover a LIS local to
a site. The access domain name option can be given a different value
at each site to enable discovery of a LIS at that site.
Alternative domain names MUST NOT be used unless the access network Alternative domain names MUST NOT be used unless the access network
domain name option is unsuccessful or where external information domain name option is unsuccessful or where external information
indicates that a particular domain name is to be used. indicates that a particular domain name is to be used.
Other domain names might be provided by a DHCP server (for example, Other domain names might be provided by a DHCP server (for example,
[RFC4702] for DHCPv4, [RFC4704] for DHCPv6). However, these domain [RFC4702] for DHCPv4, [RFC4704] for DHCPv6). However, these domain
names could be provided without considering their use for LIS names could be provided without considering their use for LIS
discovery; therefore, it is not likely that these options contain discovery; therefore, it is not likely that these options contain
useful values. useful values.
 End of changes. 6 change blocks. 
6 lines changed or deleted 13 lines changed or added

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