< draft-ietf-geopriv-policy-07.txt		draft-ietf-geopriv-policy-08.txt >
	GEOPRIV H. Schulzrinne		GEOPRIV H. Schulzrinne
	Internet-Draft Columbia U.		Internet-Draft Columbia U.
	Expires: April 24, 2006 H. Tschofenig		Expires: August 15, 2006 H. Tschofenig
	Siemens		Siemens
	J. Morris		J. Morris
	CDT		CDT
	J. Cuellar		J. Cuellar
	Siemens		Siemens
	J. Polk		J. Polk
	Cisco		Cisco
	October 21, 2005		February 11, 2006
	A Document Format for Expressing Privacy Preferences for Location		A Document Format for Expressing Privacy Preferences for Location
	Information		Information
	draft-ietf-geopriv-policy-07.txt		draft-ietf-geopriv-policy-08.txt
	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 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 April 24, 2006.		This Internet-Draft will expire on August 15, 2006.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2005).		Copyright (C) The Internet Society (2006).
	Abstract		Abstract
	This document defines an authorization policy language for controling		This document defines an authorization policy language for controling
	access to location information. It extends the authorization		access to location information. It extends the authorization
	framework of the common policy markup language to provide location-		framework of the common policy markup language to provide location-
	specific access control.		specific access control.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	skipping to change at page 2, line 30 ¶		skipping to change at page 2, line 30 ¶
	6.2.2. Altitude . . . . . . . . . . . . . . . . . . . . . . . 11		6.2.2. Altitude . . . . . . . . . . . . . . . . . . . . . . . 11
	7. Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . 12		7. Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
	8. Transformations . . . . . . . . . . . . . . . . . . . . . . . 13		8. Transformations . . . . . . . . . . . . . . . . . . . . . . . 13
	8.1. Distribution Transformation . . . . . . . . . . . . . . . 13		8.1. Distribution Transformation . . . . . . . . . . . . . . . 13
	8.2. Retention Transformation . . . . . . . . . . . . . . . . . 13		8.2. Retention Transformation . . . . . . . . . . . . . . . . . 13
	8.3. Keep Rules Transformation . . . . . . . . . . . . . . . . 14		8.3. Keep Rules Transformation . . . . . . . . . . . . . . . . 14
	8.4. Civic Location Transformation . . . . . . . . . . . . . . 14		8.4. Civic Location Transformation . . . . . . . . . . . . . . 14
	8.5. Geospatial Location Transformation . . . . . . . . . . . . 15		8.5. Geospatial Location Transformation . . . . . . . . . . . . 15
	9. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 17		9. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
	9.1. Rule Example with Civic Location Condition . . . . . . . . 17		9.1. Rule Example with Civic Location Condition . . . . . . . . 17
	9.2. Rule Example with Geospatial Location Information . . . . 18		9.2. Rule Example with Geospatial Location Information . . . . 19
	10. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 22		10. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 22
	11. Security Considerations . . . . . . . . . . . . . . . . . . . 25		11. Security Considerations . . . . . . . . . . . . . . . . . . . 25
	12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 26		12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 26
	12.1. Normative References . . . . . . . . . . . . . . . . . . . 26		12.1. Normative References . . . . . . . . . . . . . . . . . . . 26
	12.2. Informative References . . . . . . . . . . . . . . . . . . 26		12.2. Informative References . . . . . . . . . . . . . . . . . . 26
	Appendix A. Contributors . . . . . . . . . . . . . . . . . . . . 28		Appendix A. Contributors . . . . . . . . . . . . . . . . . . . . 28
	Appendix B. Acknowledgments . . . . . . . . . . . . . . . . . . . 29		Appendix B. Acknowledgments . . . . . . . . . . . . . . . . . . . 29
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 30		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 30
	Intellectual Property and Copyright Statements . . . . . . . . . . 32		Intellectual Property and Copyright Statements . . . . . . . . . . 32
	skipping to change at page 3, line 19 ¶		skipping to change at page 3, line 19 ¶
	information. In [RFC3693], a protocol-independent model for access		information. In [RFC3693], a protocol-independent model for access
	to geographic information was defined. The model includes a Location		to geographic information was defined. The model includes a Location
	Generator (LG) that produces Location Information (LI), a Location		Generator (LG) that produces Location Information (LI), a Location
	Server (LS) that authorizes access to LI, a location recipient (LR)		Server (LS) that authorizes access to LI, a location recipient (LR)
	that requests and receives information, and a Rulemaker (RM) that		that requests and receives information, and a Rulemaker (RM) that
	provides authorization policy rules. An authorization policy is a		provides authorization policy rules. An authorization policy is a
	set of rules that regulate an entity's activities with respect to		set of rules that regulate an entity's activities with respect to
	privacy-sensitive information such as location information. The data		privacy-sensitive information such as location information. The data
	object containing LI is referred to as Location Object (LO).		object containing LI is referred to as Location Object (LO).
	The basic rule set defined in PIDF-LO [I-D.ietf-geopriv-pidf-lo] can		The basic rule set defined in PIDF-LO [RFC4119] can restrict how long
	restrict how long the receiver can retain the information and it can		the receiver can retain the information and it can prohibitfurther
	prohibitfurther distribution of the information. It does not allow		distribution of the information. It does not allow to customize
	to customize information to specific receivers, for example. This		information to specific receivers, for example. This document
	document describes an enhanced rule set that provides richer		describes an enhanced rule set that provides richer constraints on
	constraints on the distribution of LOs.		the distribution of LOs.
	We refer to any entity that uses the rules in this document to		We refer to any entity that uses the rules in this document to
	restrict the retention or distribution of information as a Rule		restrict the retention or distribution of information as a Rule
	Enforcer (RE). The rule set allows the RE to enforce access		Enforcer (RE). The rule set allows the RE to enforce access
	restrictions on location data, including prohibiting any		restrictions on location data, including prohibiting any
	dissemination to particular individuals, during particular times or		dissemination to particular individuals, during particular times or
	when the Target is located in a specific region. The RM can also		when the Target is located in a specific region. The RM can also
	stipulate that only certain parts of the location object are to be		stipulate that only certain parts of the location object are to be
	distributed to recipients or that the resolution of parts of the		distributed to recipients or that the resolution of parts of the
	location object is limited.		location object is limited.
	skipping to change at page 4, line 21 ¶		skipping to change at page 4, line 21 ¶
	to perform actions and transformations. Transformations regulate how		to perform actions and transformations. Transformations regulate how
	a location server handles location objects; it might limit when and		a location server handles location objects; it might limit when and
	how data and policy can be distributed and may modify the information		how data and policy can be distributed and may modify the information
	elements that are returned to the requestor, e.g., reducing the		elements that are returned to the requestor, e.g., reducing the
	granularity of location information).		granularity of location information).
	The XML schema in Section 10 extends the XML-based authorization		The XML schema in Section 10 extends the XML-based authorization
	framework (see [I-D.ietf-geopriv-common-policy]) by introducing new		framework (see [I-D.ietf-geopriv-common-policy]) by introducing new
	members of the condition and transformation substitution groups		members of the condition and transformation substitution groups
	defined there. The schema does not define new actions. To express		defined there. The schema does not define new actions. To express
	civic location information, it makes use of that schema in [I-D.ietf-		civic location information, it makes use of that schema in [RFC4119]
	geopriv-pidf-lo] that defines the 'civicAddress' complex type.		that defines the 'civicAddress' complex type.
	2. Terminology		2. Terminology
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in [RFC2119].		document are to be interpreted as described in [RFC2119].
	This document reuses the terminology of [RFC3693], e.g., the terms		This document reuses the terminology of [RFC3693], e.g., the terms
	Location Server (LS) and Location Recipient (LR). This document and		Location Server (LS) and Location Recipient (LR). This document and
	the common policy document [I-D.ietf-geopriv-common-policy] share the		the common policy document [I-D.ietf-geopriv-common-policy] share the
	skipping to change at page 7, line 7 ¶		skipping to change at page 7, line 7 ¶
	3. Basic Data Model and Processing		3. Basic Data Model and Processing
	Since the geo privacy policy markup language defined in Section 10		Since the geo privacy policy markup language defined in Section 10
	extends the common policy markup language in [I-D.ietf-geopriv-		extends the common policy markup language in [I-D.ietf-geopriv-
	common-policy], this document adopts the basic data model as		common-policy], this document adopts the basic data model as
	introduced in Section 6 of [I-D.ietf-geopriv-common-policy].		introduced in Section 6 of [I-D.ietf-geopriv-common-policy].
	4. Rule Transport		4. Rule Transport
	The XML data format of the GEOPRIV location object is specified in[I-		The XML data format of the GEOPRIV location object is specified
	D.ietf-geopriv-pidf-lo]. The definition of the location object there		in[RFC4119]. The definition of the location object there allows
	allows enhanced authorization policies associated to the location		enhanced authorization policies associated to the location object to
	object to be referenced via a URL in the 'ruleset-reference' element		be referenced via a URL in the 'ruleset-reference' element containing
	containing an URI that indicates where a rule set related to the		an URI that indicates where a rule set related to the location object
	location object can be found.		can be found.
	One of the transformations of the rule set is the removal of the rule		One of the transformations of the rule set is the removal of the rule
	set described here before transmission. Only the whole rule set can		set described here before transmission. Only the whole rule set can
	be removed and not individual elements such as only some conditions.		be removed and not individual elements such as only some conditions.
	Before transmitting the rules to the location recipient, unless		Before transmitting the rules to the location recipient, unless
	explicitly permitted by the authorization policy, the rule set MUST		explicitly permitted by the authorization policy, the rule set MUST
	be removed from the location object, since the rule set might		be removed from the location object, since the rule set might
	disclose which entities the rule maker trusts (see Section 8).		disclose which entities the rule maker trusts (see Section 8).
	5. Securing the Location Object		5. Securing the Location Object
	The GEOPRIV requirements document [RFC3693] addresses the minimal		The GEOPRIV requirements document [RFC3693] addresses the minimal
	security protection required for the LO, namely mutual end-point		security protection required for the LO, namely mutual end-point
	authentication, data object integrity, data object confidentiality		authentication, data object integrity, data object confidentiality
	and replay protection. As proposed in[I-D.ietf-geopriv-pidf-lo],		and replay protection. As proposed in[RFC4119], S/MIME SHOULD be
	S/MIME SHOULD be used. Protection for the location object also		used. Protection for the location object also includes an attached
	includes an attached rule set.		rule set.
	Protection is likely to be necessary against adversaries who		Protection is likely to be necessary against adversaries who
	eavesdrop on the communication between the location server and the		eavesdrop on the communication between the location server and the
	location recipient or the location generator and the location server,		location recipient or the location generator and the location server,
	who tamper with the location object or who replay previously recorded		who tamper with the location object or who replay previously recorded
	location objects. Securing the communication between rule maker and		location objects. Securing the communication between rule maker and
	location server depends on the protocol which is used to perform the		location server depends on the protocol which is used to perform the
	desired actions (e.g., https). The communication between the		desired actions (e.g., https). The communication between the
	location generator and the location server can also be secured using		location generator and the location server can also be secured using
	channel security.		channel security.
	skipping to change at page 10, line 17 ¶		skipping to change at page 10, line 17 ¶
	This section describes the location-specific conditions in a rule,		This section describes the location-specific conditions in a rule,
	namely the civic and geo-spatial location conditions. The XML		namely the civic and geo-spatial location conditions. The XML
	elements and attributes shown below are defined by the XML schema in		elements and attributes shown below are defined by the XML schema in
	Section 10.		Section 10.
	6.1. Civic Location Condition		6.1. Civic Location Condition
	The <civic-loc-condition> element matches if the current location of		The <civic-loc-condition> element matches if the current location of
	the target matches all the values specified in the child elements of		the target matches all the values specified in the child elements of
	this element. The <civic-loc-condition> is of the 'civicAddress'		this element. The <civic-loc-condition> is of the 'civicAddress'
	complex type defined in [I-D.ietf-geopriv-pidf-lo]. It includes a		complex type defined in [RFC4119]. It includes a number of fields,
	number of fields, including the country, expressed as a two-letter		including the country, expressed as a two-letter ISO 3166 code, and
	ISO 3166 code, and the administrative units A1 through A6 of		the administrative units A1 through A6 of [I-D.ietf-geopriv-dhcp-
	[I-D.ietf-geopriv-dhcp-civil]. This designation offers street-level		civil]. This designation offers street-level precision.
	precision.
	If the civic location of the target is not known, rules that contain		If the civic location of the target is not known, rules that contain
	a civic location condition never match. This case may occur, for		a civic location condition never match. This case may occur, for
	example, if location information has been removed by earlier		example, if location information has been removed by earlier
	transmitters of location information or if only the geospatial		transmitters of location information or if only the geospatial
	location is known.		location is known.
	If any of the elements <A1> through <A6> are specified, <country>		If any of the elements <A1> through <A6> are specified, <country>
	MUST also be specified. The schema does not enforce that the		MUST also be specified. The schema does not enforce that the
	specification uniquely identifies a particular location. For		specification uniquely identifies a particular location. For
	skipping to change at page 14, line 33 ¶		skipping to change at page 14, line 33 ¶
	1. the authorization policy related to the location object contains		1. the authorization policy related to the location object contains
	a rule with a <keep-rules-transformation> element,		a rule with a <keep-rules-transformation> element,
	2. at least one of the rules satisfying (1) matches, and		2. at least one of the rules satisfying (1) matches, and
	3. the combined value of this permission is 'true'.		3. the combined value of this permission is 'true'.
	In all other cases, the location server MUST remove all authorization		In all other cases, the location server MUST remove all authorization
	policy rules from the location object. The rules are referenced from		policy rules from the location object. The rules are referenced from
	PDIF-LO via the 'ruleset-reference' element either using a URI or a		PDIF-LO via the 'ruleset-reference' element either using a URI or a
	CID URI scheme as described in Section 2.2.2 of [I-D.ietf-geopriv-		CID URI scheme as described in Section 2.2.2 of [RFC4119].
	pidf-lo].
	The reference to the ruleset is removed and no rules are carried as		The reference to the ruleset is removed and no rules are carried as
	MIME bodies (in case of CID URIs).		MIME bodies (in case of CID URIs).
	8.4. Civic Location Transformation		8.4. Civic Location Transformation
	The civic location transformation can be specified by means of the		The civic location transformation can be specified by means of the
	<civic-loc-transformation> element to restrict the level of civic		<civic-loc-transformation> element to restrict the level of civic
	location information the LS is permitted to provide. From lowest to		location information the LS is permitted to provide. From lowest to
	highest level, the names of these levels are: 'null', 'country',		highest level, the names of these levels are: 'null', 'country',
	'region', 'city', 'building', 'full'. Each level is given by a set		'region', 'city', 'building', 'full'. Each level is given by a set
	of civic location data items such as <country> and <A1>, ..., <A6>,		of civic location data items such as <country> and <A1>, ..., <A6>,
	as defined in [I-D.ietf-geopriv-pidf-lo]. Each level includes all		as defined in [RFC4119]. Each level includes all elements included
	elements included by the lower levels.		by the lower levels.
	The 'country' level includes only the <country> element; the 'region'		The 'country' level includes only the <country> element; the 'region'
	level adds the <A1> element; the 'city' level adds the <A2> and <A3>		level adds the <A1> element; the 'city' level adds the <A2> and <A3>
	elements; the 'building' level and the 'full' level add further civic		elements; the 'building' level and the 'full' level add further civic
	location data as shown below:		location data as shown below:
	full		full
	{<country>, <A1>, <A2>, <A3>, <A4>, <A5>, <A6>, <PRD>, <POD>,		{<country>, <A1>, <A2>, <A3>, <A4>, <A5>, <A6>, <PRD>, <POD>,
	<STS>, <HNO>, <HNS>, <LMK>, <LOC>, <PC>, <NAM>, <FLR>, <ZIP>}		<STS>, <HNO>, <HNS>, <LMK>, <LOC>, <PC>, <NAM>, <FLR>, <ZIP>}
	|		|
	skipping to change at page 17, line 16 ¶		skipping to change at page 17, line 16 ¶
	This section gives two simple examples for authorization policy rules		This section gives two simple examples for authorization policy rules
	that make use of the civic and the geospatial location condition.		that make use of the civic and the geospatial location condition.
	9.1. Rule Example with Civic Location Condition		9.1. Rule Example with Civic Location Condition
	This example illustrates a single rule that employs the civic		This example illustrates a single rule that employs the civic
	location condition which matches if the current location of the		location condition which matches if the current location of the
	target is inside the area specified by the child elements of the		target is inside the area specified by the child elements of the
	<civic-loc-condition> element. The syntax of this content complies		<civic-loc-condition> element. The syntax of this content complies
	with the 'civicAddress' complex type defined in [I-D.ietf-geopriv-		with the 'civicAddress' complex type defined in [RFC4119]. In this
	pidf-lo]. In this example, requests match only if the Target is at		example, requests match only if the Target is at his main office in a
	his main office in a Siemens site in Munich.		Siemens site in Munich.
	The rule is valid for one year as specified by the <validity>		The rule is valid for one year as specified by the <validity>
	element. No actions are imposed on LSs. The <transformations>		element. No actions are imposed on LSs. The <transformations>
	section indicates that LSs are allowed to distribute the LOs with		section indicates that LSs are allowed to distribute the LOs with
	authorization policy included and the full set of civic location		authorization policy included and the full set of civic location
	information, and to pass latitude and longitude values of geospatial		information, and to pass latitude and longitude values of geospatial
	location information on at quite a high level of resolution. Since		location information on at quite a high level of resolution. Since
	the policy does not contain a rule with a <retention-transformation>,		the policy does not contain a rule with a <retention-transformation>,
	LSs have to delete LOs immediately upon service completion.		LSs have to delete LOs immediately upon service completion.
			<?xml version="1.0" encoding="UTF-8"?>
	<cp:ruleset		<cp:ruleset
	xmlns:cp="urn:ietf:params:xml:ns:common-policy"		xmlns:cp="urn:ietf:params:xml:ns:common-policy"
	xmlns:gp="urn:ietf:params:xml:ns:geopriv-policy"		xmlns:gp="urn:ietf:params:xml:ns:geopriv-policy"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<cp:rule id="AA56i09">		<cp:rule id="AA56i09">
	<cp:conditions>		<cp:conditions>
	<cp:validity>		<cp:validity>
	<cp:from>2004-11-01T00:00:00+01:00</cp:from>		<cp:from>2004-11-01T00:00:00+01:00</cp:from>
	skipping to change at page 20, line 49 ¶		skipping to change at page 21, line 5 ¶
	</cp:ruleset>		</cp:ruleset>
	The next ruleset indicates that the target has to be at an altitude		The next ruleset indicates that the target has to be at an altitude
	between 1500 and 4000 meters in order for this rule to match.		between 1500 and 4000 meters in order for this rule to match.
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<cp:ruleset		<cp:ruleset
	xmlns:cp="urn:ietf:params:xml:ns:common-policy"		xmlns:cp="urn:ietf:params:xml:ns:common-policy"
	xmlns:gp="urn:ietf:params:xml:ns:geopriv-policy"		xmlns:gp="urn:ietf:params:xml:ns:geopriv-policy"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	xsi:schemaLocation=
	"urn:ietf:params:xml:ns:common-policy cp02.xsd
	urn:ietf:params:xml:ns:geopriv-policy gp03.xsd">
	<cp:rule id="BB56A19">		<cp:rule id="BB56A19">
	<cp:conditions>		<cp:conditions>
	<cp:validity>		<cp:validity>
	<cp:from>2004-11-01T00:00:00+01:00</cp:from>		<cp:from>2004-11-01T00:00:00+01:00</cp:from>
	<cp:to>2005-11-01T00:00:00+01:00</cp:to>		<cp:until>2005-11-01T00:00:00+01:00</cp:until>
	</cp:validity>		</cp:validity>
	<gp:geospatial-loc-condition>		<gp:geospatial-loc-condition>
	<gp:altitude>		<gp:altitude>
	<cp:min>1500.0</cp:min>		<gp:min>1500.0</gp:min>
	<cp:max>4000.0</cp:max>		<gp:max>4000.0</gp:max>
	</gp:altitude>		</gp:altitude>
	</gp:geospatial-loc-condition>		</gp:geospatial-loc-condition>
	</cp:conditions>		</cp:conditions>
	<cp:transformations>		<cp:transformations>
	<gp:distribution-transformation>		<gp:distribution-transformation>
	true		true
	</gp:distribution-transformation>		</gp:distribution-transformation>
	skipping to change at page 22, line 17 ¶		skipping to change at page 22, line 17 ¶
	This section presents the XML schema that defines the geo policy		This section presents the XML schema that defines the geo policy
	language described in the previous sections. The policy markup		language described in the previous sections. The policy markup
	language introduced by this schema extends the common policy markup		language introduced by this schema extends the common policy markup
	language (see[I-D.ietf-geopriv-common-policy]) by introducing new		language (see[I-D.ietf-geopriv-common-policy]) by introducing new
	members of the 'condition' and 'transformation' substitution groups		members of the 'condition' and 'transformation' substitution groups
	whose heads (namely the elements <condition> and <transformation>)		whose heads (namely the elements <condition> and <transformation>)
	are specified by the common policy schema ([I-D.ietf-geopriv-common-		are specified by the common policy schema ([I-D.ietf-geopriv-common-
	policy]).		policy]).
	To express civic location conditions, it imports the 'civicAddress'		To express civic location conditions, it imports the 'civicAddress'
	complex type as defined in [I-D.ietf-geopriv-pidf-lo].		complex type as defined in [RFC4119].
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<xs:schema		<xs:schema
	targetNamespace="urn:ietf:params:xml:ns:geopriv-policy"		targetNamespace="urn:ietf:params:xml:ns:geopriv-policy"
	xmlns:gp="urn:ietf:params:xml:ns:geopriv-policy"		xmlns:gp="urn:ietf:params:xml:ns:geopriv-policy"
	xmlns:cp="urn:ietf:params:xml:ns:common-policy"		xmlns:cp="urn:ietf:params:xml:ns:common-policy"
	xmlns:cl="urn:ietf:params:xml:ns:pidf:geopriv10:civilLoc"		xmlns:cl="urn:ietf:params:xml:ns:pidf:geopriv10:civilLoc"
	xmlns:xs="http://www.w3.org/2001/XMLSchema"		xmlns:xs="http://www.w3.org/2001/XMLSchema"
	elementFormDefault="qualified"		elementFormDefault="qualified"
	attributeFormDefault="unqualified">		attributeFormDefault="unqualified">
	skipping to change at page 26, line 28 ¶		skipping to change at page 26, line 28 ¶
	12.2. Informative References		12.2. Informative References
	[GML] OpenGIS, "OpenGIS Geography Markup Language (GML)		[GML] OpenGIS, "OpenGIS Geography Markup Language (GML)
	Implementation Specification, Version 3.00, OGC 02 023r4",		Implementation Specification, Version 3.00, OGC 02 023r4",
	http://www.opengeospatial.org/docs/02-023r4.pdf,		http://www.opengeospatial.org/docs/02-023r4.pdf,
	January 2003.		January 2003.
	[I-D.ietf-geopriv-common-policy]		[I-D.ietf-geopriv-common-policy]
	Schulzrinne, H., "A Document Format for Expressing Privacy		Schulzrinne, H., "A Document Format for Expressing Privacy
	Preferences", draft-ietf-geopriv-common-policy-05 (work in		Preferences", draft-ietf-geopriv-common-policy-06 (work in
	progress), July 2005.		progress), October 2005.
	[I-D.ietf-geopriv-dhcp-civil]		[I-D.ietf-geopriv-dhcp-civil]
	Schulzrinne, H., "Dynamic Host Configuration Protocol		Schulzrinne, H., "Dynamic Host Configuration Protocol
	(DHCPv4 and DHCPv6) Option for Civic Addresses		(DHCPv4 and DHCPv6) Option for Civic Addresses
	Configuration Information",		Configuration Information",
	draft-ietf-geopriv-dhcp-civil-07 (work in progress),		draft-ietf-geopriv-dhcp-civil-09 (work in progress),
	September 2005.		January 2006.
	[I-D.ietf-geopriv-pidf-lo]
	Peterson, J., "A Presence-based GEOPRIV Location Object
	Format", draft-ietf-geopriv-pidf-lo-03 (work in progress),
	September 2004.
	[I-D.ietf-simple-xcap]		[I-D.ietf-simple-xcap]
	Rosenberg, J., "The Extensible Markup Language (XML)		Rosenberg, J., "The Extensible Markup Language (XML)
	Configuration Access Protocol (XCAP)",		Configuration Access Protocol (XCAP)",
	draft-ietf-simple-xcap-07 (work in progress), June 2005.		draft-ietf-simple-xcap-08 (work in progress),
			October 2005.
	[RFC2518] Goland, Y., Whitehead, E., Faizi, A., Carter, S., and D.		[RFC2518] Goland, Y., Whitehead, E., Faizi, A., Carter, S., and D.
	Jensen, "HTTP Extensions for Distributed Authoring --		Jensen, "HTTP Extensions for Distributed Authoring --
	WEBDAV", RFC 2518, February 1999.		WEBDAV", RFC 2518, February 1999.
	[RFC2778] Day, M., Rosenberg, J., and H. Sugano, "A Model for		[RFC2778] Day, M., Rosenberg, J., and H. Sugano, "A Model for
	Presence and Instant Messaging", RFC 2778, February 2000.		Presence and Instant Messaging", RFC 2778, February 2000.
	[RFC3825] Polk, J., Schnizlein, J., and M. Linsner, "Dynamic Host		[RFC3825] Polk, J., Schnizlein, J., and M. Linsner, "Dynamic Host
	Configuration Protocol Option for Coordinate-based		Configuration Protocol Option for Coordinate-based
	Location Configuration Information", RFC 3825, July 2004.		Location Configuration Information", RFC 3825, July 2004.
	Appendix A. Contributors		[RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object
			Format", RFC 4119, December 2005.
	We would like to thank Christian Guenther for his help with this
	document:
	Christian Guenther		Appendix A. Contributors
	Siemens
	Otto-Hahn-Ring 6
	Munich, Bavaria 81730
	Germany
	EMail: Christian.Guenther@siemens.com		We would like to thank Christian Guenther for his help with an
			earlier version of this document.
	Appendix B. Acknowledgments		Appendix B. Acknowledgments
	This document is informed by the discussions within the IETF GEOPRIV		This document is informed by the discussions within the IETF GEOPRIV
	working group, including discussions at the GEOPRIV interim meeting		working group, including discussions at the GEOPRIV interim meeting
	in Washington, D.C., in 2003.		in Washington, D.C., in 2003.
	We particularly want to thank Allison Mankin <mankin@psg.com>,		We particularly want to thank Allison Mankin <mankin@psg.com>,
	Randall Gellens <rg+ietf@qualcomm.com>, Andrew Newton		Randall Gellens <rg+ietf@qualcomm.com>, Andrew Newton
	<anewton@ecotroph.net>, Ted Hardie <hardie@qualcomm.com>, Jon		<anewton@ecotroph.net>, Ted Hardie <hardie@qualcomm.com>, Jon
	skipping to change at page 32, line 41 ¶		skipping to change at page 32, 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. 26 change blocks.
	64 lines changed or deleted		51 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/