< draft-guenther-geopriv-policy-caps-02.txt		draft-guenther-geopriv-policy-caps-03.txt >
	Geopriv C. Guenther		Geopriv C. Guenther
	Internet-Draft H. Tschofenig		Internet-Draft H. Tschofenig
	Expires: October 27, 2005 Siemens		Expires: April 23, 2006 Siemens
	April 25, 2005		October 20, 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-02.txt		draft-guenther-geopriv-policy-caps-03.txt
	Status of this Memo		Status of this Memo
	This document is an Internet-Draft and is subject to all provisions		By submitting this Internet-Draft, each author represents that any
	of Section 3 of RFC 3667. By submitting this Internet-Draft, each		applicable patent or other IPR claims of which he or she is aware
	author represents that any applicable patent or other IPR claims of		have been or will be disclosed, and any of which he or she becomes
	which he or she is aware have been or will be disclosed, and any of		aware will be disclosed, in accordance with Section 6 of BCP 79.
	which he or she become aware will be disclosed, in accordance with
	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 Internet-		other groups may also distribute working documents as 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 October 27, 2005.		This Internet-Draft will expire on April 23, 2006.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2005).		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 Geopriv Policy Capabilities Schema Registration . . . . . 9		7.2. Geopriv Policy Capabilities Schema Registration . . . . . 9
	8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10		8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11		9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
	9.1 Normative References . . . . . . . . . . . . . . . . . . . 11		9.1. Normative References . . . . . . . . . . . . . . . . . . . 11
	9.2 Informative References . . . . . . . . . . . . . . . . . . 11		9.2. Informative References . . . . . . . . . . . . . . . . . . 11
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 12		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12
	Intellectual Property and Copyright Statements . . . . . . . . 13		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 have been		pieces of information to watchers. Authorization policies have been
	designed to be extensible. For this reason [I-D.rosenberg-simple-		designed to be extensible. For this reason [I-D.ietf-simple-common-
	common-policy-caps] defines a generic Extensible Markup Language		policy-caps] defines a generic Extensible Markup Language (XML) based
	(XML) based format for representing policy capabilities. That format		format for representing policy capabilities. That format applies to
	applies to many policy types, including location and presence. This		many policy types, including location and presence. This
	specification extends that one by defining policy capabilities		specification extends that one by defining policy capabilities
	specific to geographic location information. Those policy		specific to geographic location information. Those policy
	capabilities correspond to the conditions, actions and		capabilities correspond to the conditions, 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].
	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.ietf-simple-common-policy-caps]. In that specification, each
	each policy capability document has three components - a list of		policy capability document has three components - a list of supported
	supported conditions, a list of supported actions, and a list of		conditions, a list of supported actions, and a list of supported
	supported transformations. This specification merely extends that		transformations. This specification merely extends that document
	document with the conditions, actions and transformations defined in		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:
	civic-loc-condition		civic-loc-condition
	geospatial-loc-condition		geospatial-loc-condition
	distribution-transformation		distribution-transformation
	retention-tranformation		retention-tranformation
	keep-rules-transformation		keep-rules-transformation
	civic-loc-transformation		civic-loc-transformation
	geospatial-loc-transformation		geospatial-loc-transformation
	skipping to change at page 8, line 8 ¶		skipping to change at page 8, line 8 ¶
	<gpc:lat-resolution/>		<gpc:lat-resolution/>
	<gpc:lon-resolution/>		<gpc:lon-resolution/>
	</gpc:geospatial-loc-transformation>		</gpc:geospatial-loc-transformation>
	</transformations>		</transformations>
	</policy-capabilities>		</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.ietf-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:geopriv-policy-capabilities		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"
	skipping to change at page 9, line 36 ¶		skipping to change at page 9, line 36 ¶
	<title>Geopriv Policy Capabilities</title>		<title>Geopriv Policy Capabilities</title>
	</head>		</head>
	<body>		<body>
	<h1>Namespace for Geopriv Policy Capabilities</h1>		<h1>Namespace for Geopriv Policy Capabilities</h1>
	<h2>urn:ietf:params:xml:ns:geopriv-policy-capabilities</h2>		<h2>urn:ietf:params:xml:ns:geopriv-policy-capabilities</h2>
	<p>See <a href="[[[URL of published RFC]]]">RFCXXXX</a>.</p>		<p>See <a href="[[[URL of published RFC]]]">RFCXXXX</a>.</p>
	</body>		</body>
	</html>		</html>
	END		END
	7.2 Geopriv Policy Capabilities 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		XML: The XML schema to be registered is contained in section
	Section 4. Its first line is		Section 4. Its first line is
	<xs:schema		<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.ietf-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., Morris, J., Tschofenig, H., Polk, J., and		Schulzrinne, H., Morris, J., Tschofenig, H., Polk, J., and
	J. Rosenberg, "A Document Format for Expressing Privacy		J. Rosenberg, "A Document Format for Expressing Privacy
	Preferences", draft-ietf-geopriv-common-policy-04 (work in		Preferences", draft-ietf-geopriv-common-policy-04 (work in
	progress), February 2005, <reference.I-D.ietf-geopriv-		progress), February 2005.
	common-policy.xml>.
	[I-D.ietf-geopriv-policy]		[I-D.ietf-geopriv-policy]
	Schulzrinne, H., Morris, J., Tschofenig, H., Cuellar, J.,		Schulzrinne, H., Tschofenig, H., Morris, J., Cuellar, J.,
	and J. Polk, "Geopriv Policy",		and J. Polk, "Geopriv Policy",
	draft-ietf-geopriv-policy-05 (work in progress),		draft-ietf-geopriv-policy-06 (work in progress),
	November 2004, <reference.I-D.ietf-geopriv-policy-05.txt>.		July 2005.
	[I-D.rosenberg-simple-common-policy-caps]		[I-D.ietf-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-02 (work in		draft-ietf-simple-common-policy-caps-00 (work in
	progress), February 2005, <reference.I-D.rosenberg-simple-		progress), July 2005.
	common-policy-caps.txt>.
	[I-D.rosenberg-simple-pres-policy-caps]		[I-D.ietf-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-02		Capabilities", draft-ietf-simple-pres-policy-caps-00 (work
	(work in progress), February 2005, <reference.I-		in progress), July 2005.
	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, Bavaria 81739		Munich, Bavaria 81739
	Germany		Germany
	Email: christian.guenther@siemens.com		Email: christian.guenther@siemens.com
End of changes. 21 change blocks.
	44 lines changed or deleted		39 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/