< draft-guenther-geopriv-policy-caps-00.txt		draft-guenther-geopriv-policy-caps-01.txt >
	Geopriv C. Guenther		Geopriv C. Guenther
	Internet-Draft H. Tschofenig		Internet-Draft H. Tschofenig
	Expires: January 9, 2005 Siemens		Expires: April 25, 2005 Siemens
	July 11, 2004		October 25, 2004
	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-00.txt		draft-guenther-geopriv-policy-caps-01.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-Drafts.		Internet-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 http://		The list of current Internet-Drafts can be accessed at
	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 January 9, 2005.		This Internet-Draft will expire on April 25, 2005.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2004). All Rights Reserved.		Copyright (C) The Internet Society (2004).
	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 Supported Geopriv Permissions Schema Registration . . . . 9
	8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10		8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11		9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
	9.1 Normative References . . . . . . . . . . . . . . . . . . . . 11		9.1 Normative References . . . . . . . . . . . . . . . . . . . . 12
	9.2 Informative References . . . . . . . . . . . . . . . . . . . 11		9.2 Informative References . . . . . . . . . . . . . . . . . . . 12
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 12		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 13
	Intellectual Property and Copyright Statements . . . . . . . . 13		Intellectual Property and Copyright Statements . . . . . . . . 14
	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 haven been
	designed to be extensible. For this reason		designed to be extensible. For this reason
	[I-D.rosenberg-simple-common-policy-caps] defines a generic		[I-D.rosenberg-simple-common-policy-caps] defines a generic
	Extensible Markup Language (XML) based format for representing policy		Extensible Markup Language (XML) based format for representing policy
	capabilities. That format applies to many policy types, including		capabilities. That format applies to many policy types, including
	skipping to change at page 5, line 16 ¶		skipping to change at page 5, line 16 ¶
	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:
	civil-loc-condition		o civil-loc-condition
	geospatial-loc-condition		o geospatial-loc-condition
	civil-loc-transformation		o civil-loc-transformation
	set-retention		o set-retention
	set-distribution		o set-distribution
	keep-rules		o keep-rules
	longitude-resolution		o longitude-resolution
	latitude-resolution		o latitude-resolution
	altitude-resolution		o altitude-resolution
	provide-timezone		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:supported-geopriv-permissions
	4. XML Schema		4. XML Schema
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	skipping to change at page 9, line 31 ¶		skipping to change at page 9, line 31 ¶
	"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>Supported Geopriv Permissions</title>
	</head>		</head>
	<body>		<body>
	<h1>Namespace for Supported Geopriv Permissions</h1>		<h1>Namespace for Supported Geopriv Permissions</h1>
	<h2>urn:ietf:params:xml:ns:supported-geopriv-permissions</h2>		<h2>urn:ietf:params:xml:ns:supported-geopriv-permissions</h2>
	<p>See <a href="[[[URL of published RFC]]]">RFCXXXX</a>.</p>		<p>See <a href="[[[URL of published RFC]]]">RFCXXXX
			[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 Supported Geopriv Permissions 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).
	skipping to change at page 11, line 20 ¶		skipping to change at page 12, line 20 ¶
	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., "A Document Format for Expressing Privacy
	J. Rosenberg, "A Document Format for Expressing Privacy		Preferences", draft-ietf-geopriv-common-policy-02 (work in
	Preferences", draft-ietf-geopriv-common-policy-01 (work in		progress), October 2004.
	progress), July 2004,
	<reference.I-D.ietf-geopriv-common-policy.xml>.
	[I-D.ietf-geopriv-policy]		[I-D.ietf-geopriv-policy]
	Schulzrinne, H., Morris, J., Tschofenig, H., Cuellar, J.		Schulzrinne, H., "A Document Format for Expressing Privacy
	and J. Polk, "Geopriv Policy",		Preferences for Location Information",
	draft-ietf-geopriv-policy-01 (work in progress), February		draft-ietf-geopriv-policy-03 (work in progress), October
	2004, <reference.I-D.ietf-geopriv-policy-01.txt>.		2004.
			[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-00 (work in		draft-rosenberg-simple-common-policy-caps-01 (work in
	progress), February 2004,		progress), July 2004.
	<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-00		Capabilities", draft-rosenberg-simple-pres-policy-caps-01
	(work in progress), February 2004,		(work in progress), July 2004.
	<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, Bayern 81739
	Germany		Germany
	EMail: christian.guenther@siemens.com		EMail: christian.guenther@siemens.com
End of changes. 12 change blocks.
	41 lines changed or deleted		46 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/