< draft-ietf-geopriv-lis-discovery-10.txt		draft-ietf-geopriv-lis-discovery-11.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: October 25, 2009 April 23, 2009		Expires: November 8, 2009 May 7, 2009
	Discovering the Local Location Information Server (LIS)		Discovering the Local Location Information Server (LIS)
	draft-ietf-geopriv-lis-discovery-10		draft-ietf-geopriv-lis-discovery-11
	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 32 ¶
	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 October 25, 2009.		This Internet-Draft will expire on November 8, 2009.
	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 in effect on the date of
	publication of this document (http://trustee.ietf.org/license-info).		publication of this document (http://trustee.ietf.org/license-info).
	Please review these documents carefully, as they describe your rights		Please review these documents carefully, as they describe your rights
	skipping to change at page 2, line 17 ¶		skipping to change at page 2, line 17 ¶
	used as input to a URI-enabled NAPTR (U-NAPTR) resolution process.		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 . . . . . . . . . . . . 6		3. Access Network Domain Name DHCP Option . . . . . . . . . . . . 7
	3.1. Domain Name Encoding . . . . . . . . . . . . . . . . . . . 7		3.1. Domain Name Encoding . . . . . . . . . . . . . . . . . . . 7
	3.2. Access Network Domain Name DHCPv4 Option . . . . . . . . . 7		3.2. Access Network Domain Name DHCPv4 Option . . . . . . . . . 7
	3.3. Access Network Domain Name DHCPv6 Option . . . . . . . . . 8		3.3. Access Network Domain Name DHCPv6 Option . . . . . . . . . 8
	4. U-NAPTR Resolution of a LIS URI . . . . . . . . . . . . . . . 8		4. U-NAPTR Resolution of a LIS URI . . . . . . . . . . . . . . . 9
	4.1. Determining a Domain Name . . . . . . . . . . . . . . . . 9		4.1. Determining a Domain Name . . . . . . . . . . . . . . . . 10
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 10		5. Security Considerations . . . . . . . . . . . . . . . . . . . 10
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
	6.1. Registration of DHCPv4 and DHCPv6 Option Codes . . . . . . 11		6.1. Registration of DHCPv4 and DHCPv6 Option Codes . . . . . . 11
	6.2. Registration of a Location Server Application Service		6.2. Registration of a Location Server Application Service
	Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . 11		Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
	6.3. Registration of a Location Server Application Protocol		6.3. Registration of a Location Server Application Protocol
	Tag for HELD . . . . . . . . . . . . . . . . . . . . . . . 12		Tag for HELD . . . . . . . . . . . . . . . . . . . . . . . 12
	7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12		7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12		8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
	8.1. Normative References . . . . . . . . . . . . . . . . . . . 12		8.1. Normative References . . . . . . . . . . . . . . . . . . . 13
	8.2. Informative References . . . . . . . . . . . . . . . . . . 14		8.2. Informative References . . . . . . . . . . . . . . . . . . 14
	1. Introduction and Overview		1. Introduction and Overview
	The location of a device is a useful and sometimes necessary part of		The location of a device is a useful and sometimes necessary part of
	many services. A Location Information Server (LIS) is responsible		many services. A Location Information Server (LIS) is responsible
	for providing that location information to devices with an access		for providing that location information to devices with an access
	network. The LIS uses knowledge of the access network and its		network. The LIS uses knowledge of the access network and its
	physical topology to generate and serve location information to		physical topology to generate and serve location information to
	devices.		devices.
	skipping to change at page 5, line 49 ¶		skipping to change at page 5, line 49 ¶
	common deployment scenario. A fixed wireline scenario is described		common deployment scenario. A fixed wireline scenario is described
	in more detail in Section 3.1 of [I-D.ietf-geopriv-l7-lcp-ps]. In		in more detail in Section 3.1 of [I-D.ietf-geopriv-l7-lcp-ps]. In
	this fixed wireline environment an intervening residential gateway		this fixed wireline environment an intervening residential gateway
	exists between the device and the access network. If the residential		exists between the device and the access network. If the residential
	gateway does not provide this option to the devices it serves, those		gateway does not provide this option to the devices it serves, those
	devices are unable to discover a LIS.		devices are unable to discover a LIS.
	Support of this specification by residential gateways ensures that		Support of this specification by residential gateways ensures that
	the devices they serve are able to acquire location information. In		the devices they serve are able to acquire location information. In
	many cases the residential gateway configures the devices it serves		many cases the residential gateway configures the devices it serves
	using DHCP. When DHCP is used, the residential gateway MUST provide		using DHCP. A residential gateway is able to use DHCP to assist
	the devices it serves with an access network domain name DHCP option		devices in gaining access to their location information. This can be
	suitable for LIS discovery. In order to provide a useful value for		accomplished by providing an access network domain name DHCP option
	this option, the residential gateway MUST either:		suitable for LIS discovery, or by acting as a LIS directly. To
			actively assist devices, a residential gateway can either:
	o acquire an access network domain name from the access network		o acquire an access network domain name from the access network
	provider (possibly using DHCP) and pass the resulting value to		provider (possibly using DHCP) and pass the resulting value to
	devices; or		devices; or
	o discover a LIS on its external interface, then provide devices		o discover a LIS on its external interface, then provide devices
	with the domain name that was used to successfully discover the		with the domain name that was used to successfully discover the
	LIS; or		LIS; or
	o explicitly include configuration that refers to a particular LIS.		o explicitly include configuration that refers to a particular LIS;
			or
	In either case, the residential gateway provides an access network		o act as a LIS and directly provide location information to the
	domain name DHCP option to devices.		devices it serves, including providing a means to discover this
			service.
			As with devices, configuration of a specific domain name or location
			information is only accurate as long as the residential gateway does
			not move. If a residential gateway that relies on configuration
			rather than automatic discovery is moved, the devices it serves could
			be provided with inaccurate information. Devices could be led to
			discover a LIS that is unable to provide accurate location
			information, or - if location is configured on the residential
			gateway - the residential gateway could provide incorrect location
			information.
	[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)
	skipping to change at page 7, line 52 ¶		skipping to change at page 8, line 17 ¶
	Code: OPTION_V4_ACCESS_DOMAIN (TBD). [[IANA/RFC-Editor Note: Please		Code: OPTION_V4_ACCESS_DOMAIN (TBD). [[IANA/RFC-Editor Note: Please
	replace TBD with the assigned DHCPv4 option code, both here and in		replace TBD with the assigned DHCPv4 option code, both here and in
	Figure 1.]]		Figure 1.]]
	Length: The length of the entire access network domain name option		Length: The length of the entire access network domain name option
	in octets.		in octets.
	Access Network Domain Name: The domain name associated with the		Access Network Domain Name: The domain name associated with the
	access network, encoded as described in Section 3.1.		access network, encoded as described in Section 3.1.
	A DHCPv4 client MAY request a LoST server domain name in a Parameter		A DHCPv4 client MAY request a access network domain name option in a
	Request List option, as described in [RFC2131].		Parameter Request List option, as described in [RFC2131].
	This option contains a single domain name and, as such, MUST contain		This option contains a single domain name and, as such, MUST contain
	precisely one root label.		precisely one root label.
	3.3. Access Network Domain Name DHCPv6 Option		3.3. Access Network Domain Name DHCPv6 Option
	This section defines a DHCP for IPv6 (DHCPv6) option for the domain		This section defines a DHCP for IPv6 (DHCPv6) option for the domain
	name associated with the access network. The DHCPv6 option for this		name associated with the access network. The DHCPv6 option for this
	parameter is similarly formatted to the DHCPv4 option.		parameter is similarly formatted to the DHCPv4 option.
	skipping to change at page 8, line 35 ¶		skipping to change at page 8, line 49 ¶
	option-code: OPTION_V6_ACCESS_DOMAIN (TBD). [[IANA/RFC-Editor Note:		option-code: OPTION_V6_ACCESS_DOMAIN (TBD). [[IANA/RFC-Editor Note:
	Please replace TBD with the assigned DHCPv6 option code.]]		Please replace TBD with the assigned DHCPv6 option code.]]
	option-length: The length of the entire access network domain name		option-length: The length of the entire access network domain name
	option in octets.		option in octets.
	option-value: The access network domain name, encoded as described		option-value: The access network domain name, encoded as described
	in Section 3.1.		in Section 3.1.
	A DHCPv6 client MAY request a LoST server domain name in a Options		A DHCPv6 client MAY request a access network domain name option in a
	Request Option (ORO), as described in [RFC3315].		Options Request Option (ORO), as described in [RFC3315].
	This option contains a single domain name and, as such, MUST contain		This option contains a single domain name and, as such, MUST contain
	precisely one root label.		precisely one root label.
	4. U-NAPTR Resolution of a LIS URI		4. U-NAPTR Resolution of a LIS URI
	U-NAPTR [RFC4848] resolution for a LIS takes a domain name as input		U-NAPTR [RFC4848] resolution for a LIS takes a domain name as input
	and produces a URI that identifies the LIS. This process also		and produces a URI that identifies the LIS. This process also
	requires an Application Service tag and an Application Protocol tag,		requires an Application Service tag and an Application Protocol tag,
	which differentiate LIS-related NAPTR records from other records for		which differentiate LIS-related NAPTR records from other records for
	skipping to change at page 12, line 38 ¶		skipping to change at page 13, line 7 ¶
	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]
	Contact Information: The authors of this document		Contact Information: The authors of this document
	Author/Change Controller: The IESG		Author/Change Controller: The IESG
	7. Acknowledgements		7. Acknowledgements
	The authors would like to thank Leslie Daigle for her work on		This document uses a mechanism that is largely identical to that in
	U-NAPTR; Peter Koch for feedback on how not to use DNS for discovery;		[RFC5222] and [RFC5223]. The authors would like to thank Leslie
	Andy Newton for constructive suggestions with regards to document		Daigle for her work on U-NAPTR; Peter Koch for feedback on how not to
	direction; Hannes Tschofenig, Richard Barnes, and Joe Salowey for		use DNS for discovery; Andy Newton for constructive suggestions with
	input and reviews; Dean Willis for constructive feedback.		regards to document direction; Richard Barnes, Joe Salowey, Barbara
			Stark, and Hannes Tschofenig for input and reviews; Dean Willis for
			constructive feedback.
	8. References		8. References
	8.1. Normative References		8.1. Normative References
	[RFC1035] Mockapetris, P., "Domain		[RFC1035] Mockapetris, P., "Domain
	names - implementation and		names - implementation and
	specification", STD 13,		specification", STD 13,
	RFC 1035, November 1987.		RFC 1035, November 1987.
	skipping to change at page 14, line 44 ¶		skipping to change at page 15, line 14 ¶
	February 2004.		February 2004.
	[RFC3958] Daigle, L. and A. Newton,		[RFC3958] Daigle, L. and A. Newton,
	"Domain-Based Application		"Domain-Based Application
	Service Location Using SRV		Service Location Using SRV
	RRs and the Dynamic		RRs and the Dynamic
	Delegation Discovery		Delegation Discovery
	Service (DDDS)", RFC 3958,		Service (DDDS)", RFC 3958,
	January 2005.		January 2005.
			[RFC5222] Hardie, T., Newton, A.,
			Schulzrinne, H., and H.
			Tschofenig, "LoST: A
			Location-to-Service
			Translation Protocol",
			RFC 5222, August 2008.
			[RFC5223] Schulzrinne, H., Polk, J.,
			and H. Tschofenig,
			"Discovering Location-to-
			Service Translation (LoST)
			Servers Using the Dynamic
			Host Configuration
			Protocol (DHCP)",
			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-09 (work
	in progress),		in progress),
	February 2009.		February 2009.
End of changes. 14 change blocks.
	26 lines changed or deleted		57 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/