< draft-guenther-geopriv-policy-caps-01.txt		draft-guenther-geopriv-policy-caps-02.txt >
	Geopriv C. Guenther		Geopriv C. Guenther
	Internet-Draft H. Tschofenig		Internet-Draft H. Tschofenig
	Expires: April 25, 2005 Siemens		Expires: October 27, 2005 Siemens
	October 25, 2004		April 25, 2005
	An Extensible Markup Language (XML) Representation for Expressing		An Extensible Markup Language (XML) Representation for Expressing
	Geographic Location Information Policy Capabilities		Geographic Location Information Policy Capabilities
	draft-guenther-geopriv-policy-caps-01.txt		draft-guenther-geopriv-policy-caps-02.txt
	Status of this Memo		Status of this Memo
	This document is an Internet-Draft and is subject to all provisions		This document is an Internet-Draft and is subject to all provisions
	of section 3 of RFC 3667. By submitting this Internet-Draft, each		of Section 3 of RFC 3667. By submitting this Internet-Draft, each
	author represents that any applicable patent or other IPR claims of		author represents that any 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 is aware have been or will be disclosed, and any of
	which he or she become aware will be disclosed, in accordance with		which he or she become aware will be disclosed, in accordance with
	RFC 3668.		RFC 3668.
	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		other groups may also distribute working documents as Internet-
	Internet-Drafts.		Drafts.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	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 25, 2005.		This Internet-Draft will expire on October 27, 2005.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2004).		Copyright (C) The Internet Society (2005).
	Abstract		Abstract
	This specification defines a set of Extensible Markup Language (XML)		This specification defines a set of Extensible Markup Language (XML)
	elements for expressing geographic location information policy		elements for expressing geographic location information policy
	capabilities.		capabilities.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
	3. Structure of Geopriv Policy Capabilities . . . . . . . . . . . 5		3. Structure of Geopriv Policy Capabilities . . . . . . . . . . . 5
	4. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 6		4. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 6
	5. Example Document . . . . . . . . . . . . . . . . . . . . . . . 7		5. Example Document . . . . . . . . . . . . . . . . . . . . . . . 7
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 8		6. Security Considerations . . . . . . . . . . . . . . . . . . . 8
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
	7.1 Namespace Registration . . . . . . . . . . . . . . . . . . 9		7.1 Namespace Registration . . . . . . . . . . . . . . . . . . 9
	7.2 Supported Geopriv Permissions Schema Registration . . . . 9		7.2 Geopriv Policy Capabilities Schema Registration . . . . . 9
	8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11		8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12		9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
	9.1 Normative References . . . . . . . . . . . . . . . . . . . . 12		9.1 Normative References . . . . . . . . . . . . . . . . . . . 11
	9.2 Informative References . . . . . . . . . . . . . . . . . . . 12		9.2 Informative References . . . . . . . . . . . . . . . . . . 11
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 13		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 12
	Intellectual Property and Copyright Statements . . . . . . . . 14		Intellectual Property and Copyright Statements . . . . . . . . 13
	1. Introduction		1. Introduction
	Authorization policies are an important component of presence		Authorization policies are an important component of presence
	[RFC2778]. They allow the presentity to grant access to specific		[RFC2778]. They allow the presentity to grant access to specific
	pieces of information to watchers. Authorization policies haven been		pieces of information to watchers. Authorization policies have been
	designed to be extensible. For this reason		designed to be extensible. For this reason [I-D.rosenberg-simple-
	[I-D.rosenberg-simple-common-policy-caps] defines a generic		common-policy-caps] defines a generic Extensible Markup Language
	Extensible Markup Language (XML) based format for representing policy		(XML) based format for representing policy capabilities. That format
	capabilities. That format applies to many policy types, including		applies to many policy types, including location and presence. This
	location and presence. This specification extends that one by		specification extends that one by defining policy capabilities
	defining policy capabilities specific to geographic location		specific to geographic location information. Those policy
	information. Those policy capabilities correspond to the conditions,		capabilities correspond to the conditions, actions and
	actions and transformations defined in [I-D.ietf-geopriv-policy].		transformations defined in [I-D.ietf-geopriv-policy].
	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].
	Furthermore, the terminology defined in [I-D.ietf-geopriv-policy] is
	used.
	3. Structure of Geopriv Policy Capabilities		3. Structure of Geopriv Policy Capabilities
	The structure of common policy capability documents is defined in		The structure of common policy capability documents is defined in
	[I-D.rosenberg-simple-common-policy-caps]. In that specification,		[I-D.rosenberg-simple-common-policy-caps]. In that specification,
	each policy capability document has three components - a list of		each policy capability document has three components - a list of
	supported conditions, a list of supported actions, and a list of		supported conditions, a list of supported actions, and a list of
	supported transformations. This specification merely extends that		supported transformations. This specification merely extends that
	document with the conditions, actions and transformations defined in		document with the conditions, actions and transformations defined in
	[I-D.ietf-geopriv-policy]. It does so by defining the following		[I-D.ietf-geopriv-policy]. It does so by defining the following
	empty elements:		empty elements:
	o civil-loc-condition		civic-loc-condition
	o geospatial-loc-condition		geospatial-loc-condition
	o civil-loc-transformation		distribution-transformation
	o set-retention		retention-tranformation
	o set-distribution		keep-rules-transformation
	o keep-rules		civic-loc-transformation
	o longitude-resolution		geospatial-loc-transformation
	o latitude-resolution
	o altitude-resolution
	o provide-timezone
	Each of these elements indicates whether the respective attribute in		Each of these elements indicates whether the respective attribute in
	[I-D.ietf-geopriv-policy] is supported. All of these elements are		[I-D.ietf-geopriv-policy] is supported. All of these elements are
	defined within the namespace:		defined within the namespace:
	urn:ietf:params:xml:ns:supported-geopriv-permissions		urn:ietf:params:xml:ns:geopriv-policy-capabilities
	4. XML Schema		4. XML Schema
	<?xml version="1.0" encoding="UTF-8"?>
	<xs:schema		<xs:schema
	targetNamespace=		targetNamespace=
	"urn:ietf:params:xml:ns:supported-geopriv-permissions"		"urn:ietf:params:xml:ns:geopriv-policy-capabilities"
	xmlns:sgp=		xmlns="urn:ietf:params:xml:ns:geopriv-policy-capabilities"
	"urn:ietf:params:xml:ns:supported-geopriv-permissions"		xmlns:pc="urn:ietf:params:xml:ns:policy-capabilities"
	xmlns:sp=		xmlns:xs="http://www.w3.org/2001/XMLSchema"
	"urn:ietf:params:xml:ns:supported-permissions"		elementFormDefault="qualified"
	xmlns:xs=		attributeFormDefault="unqualified">
	"http://www.w3.org/2001/XMLSchema"
	elementFormDefault="qualified"
	attributeFormDefault="unqualified">
	<xs:import namespace="urn:ietf:params:xml:ns:supported-permissions"		<xs:import namespace=
	schemaLocation="supported-permissions.xsd"/>		"urn:ietf:params:xml:ns:policy-capabilities" />
	<xs:element name="civil-loc-condition"		<xs:element name="civic-loc-condition"
	substitutionGroup="sp:condition"/>		type="pc:emptyType" />
	<xs:element name="geospatial-loc-condition"
	substitutionGroup="sp:condition"/>
	<xs:element name="civil-loc-transformation"		<xs:element name="geospatial-loc-condition"
	substitutionGroup="sp:transformation"/>		type="pc:emptyType"/>
	<xs:element name="set-retention"
	substitutionGroup="sp:transformation"/>		<xs:element name="distribution-transformation"
	<xs:element name="set-distribution"		type="pc:emptyType" />
	substitutionGroup="sp:transformation"/>
	<xs:element name="keep-rules"		<xs:element name="retention-tranformation"
	substitutionGroup="sp:transformation"/>		type="pc:emptyType" />
	<xs:element name="longitude-resolution"
	substitutionGroup="sp:transformation"/>		<xs:element name="keep-rules-transformation"
	<xs:element name="latitude-resolution"		type="pc:emptyType" />
	substitutionGroup="sp:transformation"/>
	<xs:element name="altitude-resolution"		<xs:element name="civic-loc-transformation"
	substitutionGroup="sp:transformation"/>		type="pc:emptyType"/>
	<xs:element name="provide-timezone"
	substitutionGroup="sp:transformation"/>		<xs:element name="geospatial-loc-transformation">
			<xs:complexType>
			<xs:sequence>
			<xs:element name="lat-resolution"
			type="pc:emptyType" minOccurs="0" />
			<xs:element name="lon-resolution"
			type="pc:emptyType" minOccurs="0" />
			<xs:element name="alt-resolution"
			type="pc:emptyType" minOccurs="0" />
			</xs:sequence>
			</xs:complexType>
			</xs:element>
	</xs:schema>		</xs:schema>
	5. Example Document		5. Example Document
	The following document indicates that the identity, validity, and		The following document indicates that the identity and validity
	sphere conditions are supported, each of which is defined in		conditions are supported, each of which is defined in [I-D.ietf-
	[I-D.ietf-geopriv-common-policy]. It also indicates that the		geopriv-common-policy], while no support of sphere conditions is
	geolocation-specific condition named geospatial-loc-condition is		indicated. Furthermore, the example indicates that the geolocation-
	supported. Support of the geolocation-specific transformations named		specific condition named civic-loc-condition is supported. With
	civil-loc-transformation, longitude-resolution and		respect to transformations, the example gives the indication that the
	latitude-resolution is indicated by the three child elements of the		geolocation-specific transformations named keep-rules-transformation
	<transformations> element:		is supported. This is also the case for geospatial-loc-
			transformations, namely, for latitude and longitude values, but not
			for altitude values:
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<supported-permissions		<policy-capabilities
	xmlns="urn:ietf:params:xml:ns:supported-permissions"		xmlns="urn:ietf:params:xml:ns:policy-capabilities"
	xmlns:sgp="urn:ietf:params:xml:ns:supported-geopriv-permissions"		xmlns:gpc="urn:ietf:params:xml:ns:geopriv-policy-capabilities"
	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:supported-permissions
	supported-permissions.xsd
	urn:ietf:params:xml:ns:supported-geopriv-permissions
	supported-geopriv-permissions.xsd">
	<conditions>		<conditions>
	<identity/>		<identity/>
	<validity/>		<validity/>
	<sphere/>		<gpc:civic-loc-condition/>
	<sgp:geospatial-loc-condition/>		</conditions>
	</conditions>
	<actions>		<actions>
	</actions>		</actions>
	<transformations>		<transformations>
	<sgp:civil-loc-transformation/>		<gpc:keep-rules-transformation/>
	<sgp:longitude-resolution/>		<gpc:geospatial-loc-transformation>
	<sgp:latitude-resolution/>		<gpc:lat-resolution/>
	</transformations>		<gpc:lon-resolution/>
			</gpc:geospatial-loc-transformation>
			</transformations>
	</supported-permissions>		</policy-capabilities>
	6. Security Considerations		6. Security Considerations
	This specification does not introduce any new security considerations		This specification does not introduce any new security considerations
	beyond those discussed in [I-D.rosenberg-simple-common-policy-caps].		beyond those discussed in [I-D.rosenberg-simple-common-policy-caps].
	7. IANA Considerations		7. IANA Considerations
	This section registers a new XML namespace and a new XML schema with		This section registers a new XML namespace and a new XML schema with
	IANA.		IANA.
	7.1 Namespace Registration		7.1 Namespace Registration
	URI: urn:ietf:params:xml:ns:supported-geopriv-permissions		URI: urn:ietf:params:xml:ns:geopriv-policy-capabilities
	Registrant Contact: IETF Geopriv Working Group, Christian Guenther		Registrant Contact: IETF Geopriv Working Group, Christian Guenther
	(christian.guenther@siemens.com), Hannes Tschofenig		(christian.guenther@siemens.com), Hannes Tschofenig
	(hannes.tschofenig@siemens.com).		(hannes.tschofenig@siemens.com).
	XML:		XML:
	BEGIN		BEGIN
	<?xml version="1.0"?>		<?xml version="1.0"?>
	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"		<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
	"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">		"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
	<html xmlns="http://www.w3.org/1999/xhtml">		<html xmlns="http://www.w3.org/1999/xhtml">
	<head>		<head>
	<meta http-equiv="content-type"		<meta http-equiv="content-type"
	content="text/html;charset=iso-8859-1"/>		content="text/html;charset=iso-8859-1"/>
	<title>Supported Geopriv Permissions</title>		<title>Geopriv Policy Capabilities</title>
	</head>		</head>
	<body>		<body>
	<h1>Namespace for Supported Geopriv Permissions</h1>		<h1>Namespace for Geopriv Policy Capabilities</h1>
	<h2>urn:ietf:params:xml:ns:supported-geopriv-permissions</h2>		<h2>urn:ietf:params:xml:ns:geopriv-policy-capabilities</h2>
	<p>See <a href="[[[URL of published RFC]]]">RFCXXXX		<p>See <a href="[[[URL of published RFC]]]">RFCXXXX</a>.</p>
	[NOTE TO IANA/RFC-EDITOR:
	Please replace XXXX with the RFC number of this
	specification.]
	</a>.</p>
	</body>		</body>
	</html>		</html>
	END		END
	7.2 Supported Geopriv Permissions Schema Registration		7.2 Geopriv Policy Capabilities Schema Registration
	URI: Please assign.		URI: Please assign.
	Registrant Contact: IETF Geopriv Working Group, Christian Guenther		Registrant Contact: IETF Geopriv Working Group, Christian Guenther
	(christian.guenther@siemens.com), Hannes Tschofenig		(christian.guenther@siemens.com), Hannes Tschofenig
	(hannes.tschofenig@siemens.com).		(hannes.tschofenig@siemens.com).
	XML: The XML schema to be registered is contained in section Section		XML: The XML schema to be registered is contained in section
	4. Its first line is		Section 4. Its first line is
	<?xml version="1.0" encoding="UTF-8"?>		<xs:schema
	and its last line is		and its last line is
	</xs:schema>		</xs:schema>
	8. Acknowledgments		8. Acknowledgments
	The authors would like to thank Jonathan Rosenberg whose Presence		The authors would like to thank Jonathan Rosenberg whose Presence
	Policy Capabilities document [I-D.rosenberg-simple-pres-policy-caps]		Policy Capabilities document [I-D.rosenberg-simple-pres-policy-caps]
	served as template for this document.		served as template for this document.
	9. References		9. References
	9.1 Normative References		9.1 Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", March 1997.		Requirement Levels", March 1997.
	[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", February 2000.		Presence and Instant Messaging", February 2000.
	[RFC3688] Mealling, M., "The IETF XML Registry", January 2004.		[RFC3688] Mealling, M., "The IETF XML Registry", January 2004.
	9.2 Informative References		9.2 Informative References
	[I-D.ietf-geopriv-common-policy]		[I-D.ietf-geopriv-common-policy]
	Schulzrinne, H., "A Document Format for Expressing Privacy		Schulzrinne, H., Morris, J., Tschofenig, H., Polk, J., and
	Preferences", draft-ietf-geopriv-common-policy-02 (work in		J. Rosenberg, "A Document Format for Expressing Privacy
	progress), October 2004.		Preferences", draft-ietf-geopriv-common-policy-04 (work in
			progress), February 2005, <reference.I-D.ietf-geopriv-
			common-policy.xml>.
	[I-D.ietf-geopriv-policy]		[I-D.ietf-geopriv-policy]
	Schulzrinne, H., "A Document Format for Expressing Privacy		Schulzrinne, H., Morris, J., Tschofenig, H., Cuellar, J.,
	Preferences for Location Information",		and J. Polk, "Geopriv Policy",
	draft-ietf-geopriv-policy-03 (work in progress), October		draft-ietf-geopriv-policy-05 (work in progress),
	2004.		November 2004, <reference.I-D.ietf-geopriv-policy-05.txt>.
	[I-D.ietf-simple-presence-rules]
	Rosenberg, J., "Presence Authorization Rules",
	draft-ietf-simple-presence-rules-00 (work in progress),
	May 2004.
	[I-D.rosenberg-simple-common-policy-caps]		[I-D.rosenberg-simple-common-policy-caps]
	Rosenberg, J., "An Extensible Markup Language (XML)		Rosenberg, J., "An Extensible Markup Language (XML)
	Representation for Expressing Policy Capabilities",		Representation for Expressing Policy Capabilities",
	draft-rosenberg-simple-common-policy-caps-01 (work in		draft-rosenberg-simple-common-policy-caps-02 (work in
	progress), July 2004.		progress), February 2005, <reference.I-D.rosenberg-simple-
			common-policy-caps.txt>.
	[I-D.rosenberg-simple-pres-policy-caps]		[I-D.rosenberg-simple-pres-policy-caps]
	Rosenberg, J., "An Extensible Markup Language (XML)		Rosenberg, J., "An Extensible Markup Language (XML)
	Representation for Expressing Presence Policy		Representation for Expressing Presence Policy
	Capabilities", draft-rosenberg-simple-pres-policy-caps-01		Capabilities", draft-rosenberg-simple-pres-policy-caps-02
	(work in progress), July 2004.		(work in progress), February 2005, <reference.I-
			D.rosenberg-simple-pres-policy-caps.txt>.
	Authors' Addresses		Authors' Addresses
	Christian Guenther		Christian Guenther
	Siemens		Siemens
	Otto-Hahn-Ring 6		Otto-Hahn-Ring 6
	Munich, Bayern 81739		Munich, Bavaria 81739
	Germany		Germany
	EMail: christian.guenther@siemens.com		Email: christian.guenther@siemens.com
	Hannes Tschofenig		Hannes Tschofenig
	Siemens		Siemens
	Otto-Hahn-Ring 6		Otto-Hahn-Ring 6
	Munich, Bayern 81739		Munich, Bavaria 81739
	Germany		Germany
	EMail: hannes.tschofenig@siemens.com		Email: hannes.tschofenig@siemens.com
	Intellectual Property Statement		Intellectual Property Statement
	The IETF takes no position regarding the validity or scope of any		The IETF takes no position regarding the validity or scope of any
	Intellectual Property Rights or other rights that might be claimed to		Intellectual Property Rights or other rights that might be claimed to
	pertain to the implementation or use of the technology described in		pertain to the implementation or use of the technology described in
	this document or the extent to which any license under such rights		this document or the extent to which any license under such rights
	might or might not be available; nor does it represent that it has		might or might not be available; nor does it represent that it has
	made any independent effort to identify any such rights. Information		made any independent effort to identify any such rights. Information
	on the procedures with respect to rights in RFC documents can be		on the procedures with respect to rights in RFC documents can be
	skipping to change at page 14, line 41 ¶		skipping to change at page 13, 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 (2004). This document is subject		Copyright (C) The Internet Society (2005). 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. 39 change blocks.
	140 lines changed or deleted		132 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/