< draft-ietf-geopriv-dhcp-civil-08.txt		draft-ietf-geopriv-dhcp-civil-09.txt >
	GEOPRIV H. Schulzrinne		GEOPRIV H. Schulzrinne
	Internet-Draft Columbia U.		Internet-Draft Columbia U.
	Expires: June 23, 2006 December 20, 2005		Expires: July 20, 2006 January 16, 2006
	Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic		Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic
	Addresses Configuration Information		Addresses Configuration Information
	draft-ietf-geopriv-dhcp-civil-08		draft-ietf-geopriv-dhcp-civil-09
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, each author represents that any		By submitting this Internet-Draft, each author represents that any
	applicable patent or other IPR claims of which he or she is aware		applicable patent or other IPR claims of which he or she is aware
	have been or will be disclosed, and any of which he or she becomes		have been or will be disclosed, and any of which he or she becomes
	aware will be disclosed, in accordance with Section 6 of BCP 79.		aware will be disclosed, in accordance with Section 6 of 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
	skipping to change at page 1, line 34 ¶		skipping to change at page 1, line 34 ¶
	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 June 23, 2006.		This Internet-Draft will expire on July 20, 2006.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2005).		Copyright (C) The Internet Society (2006).
	Abstract		Abstract
	This document specifies a Dynamic Host Configuration Protocol (DHCPv4		This document specifies a Dynamic Host Configuration Protocol (DHCPv4
	and DHCPv6) option containing the civic location of the client or the		and DHCPv6) option containing the civic location of the client or the
	DHCP server. The Location Configuration Information (LCI) includes		DHCP server. The Location Configuration Information (LCI) includes
	information about the country, administrative units such as states,		information about the country, administrative units such as states,
	provinces and cities, as well as street addresses, postal community		provinces and cities, as well as street addresses, postal community
	names and building information. The option allows multiple		names and building information. The option allows multiple
	renditions of the same address in different scripts and languages.		renditions of the same address in different scripts and languages.
	skipping to change at page 4, line 46 ¶		skipping to change at page 4, line 46 ¶
	the DHCP server to the client, due to security concerns related to		the DHCP server to the client, due to security concerns related to
	using DHCP to update the database. Within the GEOPRIV architecture		using DHCP to update the database. Within the GEOPRIV architecture
	as defined by RFC 3693 [11], the defined mechanism in this document		as defined by RFC 3693 [11], the defined mechanism in this document
	for conveying initial location information is known as a "sighting"		for conveying initial location information is known as a "sighting"
	function. Sighting functions are not required to have security		function. Sighting functions are not required to have security
	capabilities and are only intended to be configured in trusted and		capabilities and are only intended to be configured in trusted and
	controlled environments. (A classic example of the sighting function		controlled environments. (A classic example of the sighting function
	is a Global Positioning System wired directly to a network node.)		is a Global Positioning System wired directly to a network node.)
	After initial location information has been introduced, it MUST be		After initial location information has been introduced, it MUST be
	afforded the protections defined in RFC 3694 [12]. Therefore,		afforded the protections defined in RFC 3694 [12]. Therefore,
	location information MUST NOT be sent from a DHCP client to a DHCP		location information SHOULD NOT be sent from a DHCP client to a DHCP
	server as is normally allowed by DHCP.		server. If a client decides to send location information to the
			server, it is implicitly granting that server unlimited retention and
			distribution permissions.
	End systems that obtain location information via the mechanism		End systems that obtain location information via the mechanism
	described here then use other protocol mechanisms to communicate this		described here then use other protocol mechanisms to communicate this
	information to an emergency call center or to convey it as part of		information to an emergency call center or to convey it as part of
	presence information.		presence information.
	Civic information is useful since it often provides additional,		Civic information is useful since it often provides additional,
	human-usable information particularly within buildings. Also,		human-usable information particularly within buildings. Also,
	compared to geospatial information, it is readily obtained for most		compared to geospatial information, it is readily obtained for most
	occupied structures and can often be interpreted even if incomplete.		occupied structures and can often be interpreted even if incomplete.
	skipping to change at page 23, line 41 ¶		skipping to change at page 23, line 41 ¶
	This document and the information contained herein are provided on an		This document and the information contained herein are provided on an
	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS		"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
	OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET		OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
	ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,		ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
	INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE		INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
	INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED		INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
	WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.		WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
	Copyright Statement		Copyright Statement
	Copyright (C) The Internet Society (2005). This document is subject		Copyright (C) The Internet Society (2006). This document is subject
	to the rights, licenses and restrictions contained in BCP 78, and		to the rights, licenses and restrictions contained in BCP 78, and
	except as set forth therein, the authors retain all their rights.		except as set forth therein, the authors retain all their rights.
	Acknowledgment		Acknowledgment
	Funding for the RFC Editor function is currently provided by the		Funding for the RFC Editor function is currently provided by the
	Internet Society.		Internet Society.
End of changes. 6 change blocks.
	7 lines changed or deleted		9 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/