< draft-ietf-simple-rpid-02.txt		draft-ietf-simple-rpid-03.txt >
	SIMPLE H. Schulzrinne		SIMPLE H. Schulzrinne
	Internet-Draft Columbia U.		Internet-Draft Columbia U.
	Expires: September 11, 2004 V. Gurbani		Expires: September 18, 2004 V. Gurbani
	Lucent		Lucent
	P. Kyzivat		P. Kyzivat
	Cisco		Cisco
	J. Rosenberg		J. Rosenberg
	dynamicsoft		dynamicsoft
	March 13, 2004		March 20, 2004
	RPID: Rich Presence: Extensions to the Presence Information Data		RPID: Rich Presence Extensions to the Presence Information Data
	Format (PIDF)		Format (PIDF)
	draft-ietf-simple-rpid-02		draft-ietf-simple-rpid-03
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, I certify that any applicable		By submitting this Internet-Draft, I certify that any applicable
	patent or other IPR claims of which I am aware have been disclosed,		patent or other IPR claims of which I am aware have been disclosed,
	and any of which I become aware will be disclosed, in accordance with		and any of which I become aware will be disclosed, in accordance with
	RFC 3667.		RFC 3667.
	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 other		Task Force (IETF), its areas, and its working groups. Note that other
	skipping to change at page 1, line 39 ¶		skipping to change at page 1, line 39 ¶
	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 http://
	www.ietf.org/ietf/1id-abstracts.txt.		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 September 11, 2004.		This Internet-Draft will expire on September 18, 2004.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2004). All Rights Reserved.		Copyright (C) The Internet Society (2004). All Rights Reserved.
	Abstract		Abstract
	The Rich Presence Information Data Format (RPID) adds elements to the		The Rich Presence Information Data Format (RPID) adds elements to the
	Presence Information Data Format (PIDF) that provide additional		Presence Information Data Format (PIDF) that provide additional
	information about the presentity and its contacts. The information		information about the presentity and its contacts. The information
	skipping to change at page 2, line 47 ¶		skipping to change at page 2, line 47 ¶
	'urn:ietf:params:xml:ns:pidf:status:rpid-status' . . . . . . . 13		'urn:ietf:params:xml:ns:pidf:status:rpid-status' . . . . . . . 13
	7.2 URN Sub-Namespace Registration for		7.2 URN Sub-Namespace Registration for
	'urn:ietf:params:xml:ns:pidf:rpid-tuple' . . . . . . . . . . . 14		'urn:ietf:params:xml:ns:pidf:rpid-tuple' . . . . . . . . . . . 14
	7.3 Schema Registration for Schema		7.3 Schema Registration for Schema
	urn:ietf:params:xml:ns:pidf:rpid-tuple' . . . . . . . . . . . 15		urn:ietf:params:xml:ns:pidf:rpid-tuple' . . . . . . . . . . . 15
	7.4 Schema Registration for Schema		7.4 Schema Registration for Schema
	urn:ietf:params:xml:ns:pidf:status:rpid-status' . . . . . . . 15		urn:ietf:params:xml:ns:pidf:status:rpid-status' . . . . . . . 15
	7.5 Token Registrations . . . . . . . . . . . . . . . . . . . . . 15		7.5 Token Registrations . . . . . . . . . . . . . . . . . . . . . 15
	8. Security Considerations . . . . . . . . . . . . . . . . . . . 16		8. Security Considerations . . . . . . . . . . . . . . . . . . . 16
	Normative References . . . . . . . . . . . . . . . . . . . . . 16		Normative References . . . . . . . . . . . . . . . . . . . . . 16
	Informative References . . . . . . . . . . . . . . . . . . . . 16		Informative References . . . . . . . . . . . . . . . . . . . . 17
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 17		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 17
	A. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18		A. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18
	Intellectual Property and Copyright Statements . . . . . . . . 19		Intellectual Property and Copyright Statements . . . . . . . . 19
	1. Scope		1. Scope
	The Presence Information Data Format (PIDF) defines a basic format		The Presence Information Data Format (PIDF) defines a basic format
	for representing presence information for a presentity. That format		for representing presence information for a presentity. That format
	defines a textual note, an indication of availability (open or		defines a textual note, an indication of availability (open or
	closed) and a URI for communication. However, it is frequently		closed) and a URI for communication. However, it is frequently
	skipping to change at page 7, line 17 ¶		skipping to change at page 7, line 17 ¶
	The <placetype> element describes the type of place the presentity is		The <placetype> element describes the type of place the presentity is
	currently at. This offers the watcher an indication what kind of		currently at. This offers the watcher an indication what kind of
	communication is likely to be appropriate. We define an initial set		communication is likely to be appropriate. We define an initial set
	of values below:		of values below:
	home: The presentity is in a private or residential setting, not		home: The presentity is in a private or residential setting, not
	necessarily the personal residence of the presentity, e.g.,		necessarily the personal residence of the presentity, e.g.,
	including hotel or a friend's home.		including hotel or a friend's home.
	office: The presentity is in a business setting, such as an office.		office: The presentity is in a business setting, such as an office.
			industrial: The presentity is in an industrial setting, such as a
			manufacturing floor or powerplant.
	quiet: The presentity is in a place such as a library, restaurant,		quiet: The presentity is in a place such as a library, restaurant,
	place-of-worship, or theater that discourages noise, conversation		place-of-worship, or theater that discourages noise, conversation
	and other distractions.		and other distractions.
			noisy: The presentity is in a place with lots of background noise.
	public: The presentity is in a public area such as a shopping mall,		public: The presentity is in a public area such as a shopping mall,
	street, park, public building, train station, airport or in public		street, park, public building, train station, airport or in public
	conveyance such as a bus, train, plane or ship. This general		conveyance such as a bus, train, plane or ship. This general
	description encompasses the more precise descriptors 'street',		description encompasses the more precise descriptors 'street',
	'public-transport', 'aircraft', 'ship', 'bus', 'train', 'airport',		'public-transport', 'aircraft', 'ship', 'bus', 'train', 'airport',
	'mall' and 'outdoors' below.		'mall' and 'outdoors' below.
	street: Walking in a street.		street: Walking in a street.
	public-transport: Any form of public transport, including aircraft,		public-transport: Any form of public transport, including aircraft,
	bus, train or ship.		bus, train or ship.
	aircraft: The presentity is in a plane, helicopter or balloon.		aircraft: The presentity is in a plane, helicopter or balloon.
	skipping to change at page 16, line 9 ¶		skipping to change at page 16, line 9 ¶
	privacy: See Section 4.7		privacy: See Section 4.7
	relationship: See Section 4.8		relationship: See Section 4.8
	All are XML tokens. Registered tokens must be documented at the time		All are XML tokens. Registered tokens must be documented at the time
	of registration, as most descriptions are expected to be brief.		of registration, as most descriptions are expected to be brief.
	Following the policies outline in RFC 2434 [3], these tokens are		Following the policies outline in RFC 2434 [3], these tokens are
	assigned after Expert Review by the SIMPLE working group or its		assigned after Expert Review by the SIMPLE working group or its
	designated successor. Each registration must include the name of the		designated successor. Each registration must include the name of the
	token and a brief description similar to the ones offered in for the		token and a brief description similar to the ones offered in for the
	initial registrations contained this document.		initial registrations contained this document:
			Name of token: XML token describing the contact type, place type,
			privacy or relationship.
			Description: Brief description indicating the meaning of the token.
	8. Security Considerations		8. Security Considerations
	The security considerations in [7] apply, as well as [8]. Compared to		The security considerations in [7] apply, as well as [8]. Compared to
	PIDF, this presence document format reveals additional information		PIDF, this presence document format reveals additional information
	that can be highly sensitive. Beyond traditional security measures to		that can be highly sensitive. Beyond traditional security measures to
	protect confidentiality and integrity, systems should offer a means		protect confidentiality and integrity, systems should offer a means
	to selectively reveal information to particular watchers and to		to selectively reveal information to particular watchers and to
	inspect the information that is being published, particularly if it		inspect the information that is being published, particularly if it
	is generated automatically from other sources, such as calendars or		is generated automatically from other sources, such as calendars or
End of changes. 9 change blocks.
	7 lines changed or deleted		14 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/