SIMPLE H. Schulzrinne Internet-Draft Columbia U. Expires:August 9,September 11, 2004 V. Gurbani Lucent P. Kyzivat Cisco J. Rosenberg dynamicsoftFebruary 9,March 13, 2004RPID -RPID: Rich Presence: Extensions to the Presence Information Data Formatdraft-ietf-simple-rpid-01(PIDF) draft-ietf-simple-rpid-02 Status of this MemoThis document is an Internet-DraftBy submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, andisany of which I become aware will be disclosed, infull conformanceaccordance withall provisions of Section 10 of RFC2026.RFC 3667. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http:// www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire onAugust 9,September 11, 2004. Copyright Notice Copyright (C) The Internet Society (2004). All Rights Reserved. Abstract The Rich Presence Information Data Format (RPID) adds elements to the Presence Information Data Format (PIDF) that provide additional information about the presentity and its contacts.This information can be translated into call routing behavior or be delivered to watchers, for example.The information is designed so that much of it can be derived automatically, e.g., from calendar files or user activity. This extension includes information about what the presentity is doing (the activity element), a grouping identifier for a tuple (the class element), the type of tuple (the contact-type element), whether a contact is idle (the idle element), the typle of place a presentity is in (the placetype element), whether the presentity is in a public or private space (the privacy element), the relationship of a tuple to another presentity (the relationship element), and the overall role of the presentity (the sphere element). Table of Contents 1. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology and Conventions . . . . . . . . . . . . . . . . .43 3. The Meaning of "open" and "closed" . . . . . . . . . . . . . .53 4. RPID Elements . . . . . . . . . . . . . . . . . . . . . . . .63 4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . .63 4.2ActivityActivities Element . . . . . . . . . . . . . . . . . . . . . .. 64 4.3 Class . . . . . . . . . . . . . . . . . . . . . . . . . . . .76 4.4 Contact-Type Element . . . . . . . . . . . . . . . . . . . . .86 4.5 Idle Element . . . . . . . . . . . . . . . . . . . . . . . . .86 4.6 Type of Place Element . . . . . . . . . . . . . . . . . . . .87 4.7 Privacy Element . . . . . . . . . . . . . . . . . . . . . . .98 4.8 Relationship Element . . . . . . . . . . . . . . . . . . . . .108 4.9 Sphere Element . . . . . . . . . . . . . . . . . . . . . . . .108 5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . .119 5.1 Presentity with Activity . . . . . . . . . . . . . . . . . . .119 6. XML Schema Definitions . . . . . . . . . . . . . . . . . . . .1310 6.1 urn:ietf:params:xml:ns:pidf:rpid-tuple . . . . . . . . . . . . 11 6.2 urn:ietf:params:xml:ns:pidf:status:rpid-status . . . . . . . . 11 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . .1613 7.1 URN Sub-Namespace Registration for'urn:ietf:params:xml:ns:pidf:rpid-status''urn:ietf:params:xml:ns:pidf:status:rpid-status' . . . . . . .. . . 1613 7.2 URN Sub-Namespace Registration for 'urn:ietf:params:xml:ns:pidf:rpid-tuple' . . . . . . . . . . .1714 7.3Place Type, Tuple Type, Activities, RelationshipsSchema Registration for Schema urn:ietf:params:xml:ns:pidf:rpid-tuple' . . . . . .17. . . . . 15 7.4 Schema Registration for Schema urn:ietf:params:xml:ns:pidf:status:rpid-status' . . . . . . . 15 7.5 Token Registrations . . . . . . . . . . . . . . . . . . . . . 15 8. Security Considerations . . . . . . . . . . . . . . . . . . .1816 Normative References . . . . . . . . . . . . . . . . . . . . .1916 Informative References . . . . . . . . . . . . . . . . . . . .2016 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . .2017 A. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .2218 Intellectual Property and Copyright Statements . . . . . . . .2319 1. ScopeThis extension does not replace media negotiation mechanisms definedThe Presence Information Data Format (PIDF) defines a basic format forSIP (e.g., SDP [8]), therefore media negotiation (e.g., choicerepresenting presence information for a presentity. That format defines a textual note, an indication ofvoiceavailability (open or closed) andvideo codecs) MUST be performed accordinga URI for communication. However, it is frequently useful toRFC 3264 [10]. This extensionconvey additional information about a user that needs to be interpreted by an automata, and isonly aimedtherefore not appropriate for placement in the note element of the PIDF document. This document defines extensions togivethewatchers hints aboutPIDF document format for conveying richer presence information. Generally, thepresentity's preferences, willingness and capabilitiesextensions have been chosen tocommunicate before watchers initiate SIP-based communication withprovide features common in existing presence systems at thepresentity.time of writing, in addition to elements that could readily be derived automatically from existing sources of presence, such as calendaring systems, or sources describing the user's current physical environment. 2. Terminology and Conventions This memo makes use of the vocabulary defined in the IMPP Model document[4].[5]. Terms such as CLOSED, INSTANT MESSAGE, OPEN, PRESENCE SERVICE, PRESENTITY, WATCHER, and WATCHER USER AGENT in the memo are used in the same meaning as defined therein. The key words MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be interpreted as described in BCPXX,14, RFC 2119 [1]. 3. The Meaning of "open" and "closed" PIDF describes the basic status values of "open" or "closed" only as "have meanings of general availability for other communications means". We define "closed" in our context as meaning that communication to the contact address will in all likelihood not succeed, is undesired or will not reach the intended party. (For example, a presentity may include a hotel phone number as a contact. After check-out, the phone number will still ring, but reach the chambermaid or the next guest. Thus, it would be declared "closed".) For "pres" contacts, "closed" means that no presence status information is available. 4. RPID Elements 4.1 Introduction Below, we describe the RPID elements in detail.<activity>, <idle> <placetype>, <privacy>, <relationship>,<activities>, <idle>, <placetype> and <privacy> extend the PIDF <status> element, while<class> and<class>, <contacttype> and <relationship> extend the PIDF <tuple> element. In general, it is highly unlikely that a presentity will publish or announce all of these elements at the same time. Rather, these elements were chosen to give the presentity maximum flexibility in deriving this information from existing sources, such as calendaring tools, device activity sensors or location trackers, as well as to manually configure this information. The namespace URIs for these elements defined by this specification are URNs [2], using the namespace identifier 'ietf' defined by[3][4] and extended by[5]: urn:ietf:params:xml:ns:pidf:rpid-status urn:ietf:params:xml:ns:pidf:rpid-tuple[6]: urn:ietf:params:xml:ns:pidf:status:rpid-status urn:ietf:params:xml:ns:pidf:status:rpid-tuple This document uses a separate namespace for extending the PIDF 'status' namespace, in accordance with Section 4.2.5 of [7]. All elements described in this document are optional. The elements <activity>, <placetype>, <privacy> and <sphere> MAY be qualified with the 'since' and 'until' attributes to describe the absolute time when the element assumed this value and the absolute time until which is element is expected to be valid. The 'since' time MUST be in the past, the 'until' time in the future relative to the time of publication of the presence information and, if available, the PIDF 'timestamp' element. 4.2ActivityActivities Element The<activity> indication<activities> element describes what the presentity is currently doing. This can be quite helpful to the watcher in judging how appropriate a communication attempt is and which means of communications is most likely to succeed and not annoy the presentity. The activity indications correspond roughly to the category field in calendar entries, such as Section 4.8.1.2 of RFC2445.2445 [10]. An activityindicationenumeration consists of one or more values drawn from the list below, any other token string or IANA-registered values (Section Section 7).Communities of interest such as a profession or an organization may define additional activity labels for their internal use.Depending on the presentity intent, all but the"available""permanent-absence" indication can be used with either status OPEN or CLOSED.Available: The presentity is available for communication. On-the-phone:on-the-phone: The presentity is talking on the telephone. This activity is included since it can often be derived automatically.Away:away: The presentity is physically away from the device location. This activity was included since it can often be derived automatically from security systems, energy management systems or entry badge systems.Appointment:appointment: The presentity has a calendarappointment. Holiday:appointment, without specifying exactly of what type. This activity is indicated if more detailed information is not available or the presentity choses not to reveal more information. holiday: This is a scheduled national or local holiday. This information can typically be derived automatically from calendars.Meal:meal: The presentity is scheduled for a meal. This activity category can often be generated automatically from a calendar.Meeting:meeting: A meeting is a sub-class of an appointment. This activity category can often be generated automatically from a calendar.Steering:steering: The presentity is controlling a vehicle, ship or plane.In-transit:in-transit: The presentity is riding in a vehicle, such as a car, but not steering.Alternatively, the presentity MAY offerThe 'placetype' element provides more specificinformation. Travel:information about the type of conveyance the presentity is using. travel: The presentity is on a business or personal trip, but not necessarily in-transit. This category can often be generated automatically from a calendar.Vacation:vacation: Leisure travel. This activity category can often be generated automatically from a calendar.Sleeping:sleeping: This activity category can often be generated automatically from a calendar, local time information or biometric data.Busy:busy: User is busy, without further details.ThisWhile this activitycategorywould typically beindicated manually. Permanent-absence:associated with a status of CLOSED, a presentity may declare itself busy to discourage communication, but indicate that it still can be reached if needed. permanent-absence: Presentity will not return for the foreseeable future, e.g., because it is no longer working for the company. This activity is associated with a status of CLOSED. The <activity> element MAY be qualified with the'from''since' and 'until' attributesto describe the time when theas described in Section 4. The <activities> elementassumed this value andcan be used with tuples of all values of <contact-type>. For tuples consisting of multiple physical devices, i.e., of <contact-type> 'service' or 'presentity', these components can engage in multiple types of activities, particularly if qualified by a <relationship> element. In those cases, thetime until which is<activities> elementis expected to be valid.enumerates all unique values as child <activity> elements. The'from' time MUST<activities> element can bein the past, the 'until' time in the future relativeextended by adding elements from other namespaces, e.g., tothe publication of the presence information.reflect activities appropriate for a particular occupation. 4.3 Class The 'class' attribute describes the class of the tuple. Multiple tuples can have the same class name within a presence document. The naming of classes is left to the presentity. The presentity can use this information to group similar tuples or to convey information that the presence agent can use for filtering. 4.4 Contact-Type Element The <contacttype> element describes the type of the tuple. A tuple can represent a communication facility ("device"), a face-to-face communication tuple ("in-person"), a set of devices offering a common service ("service"), or a whole presentity ("presentity"). Additional types can be registered with IANA. 4.5 Idle ElementTheFor tuples representing a single device, i.e., having a <contact-type> of 'device', the <idle> element records the absolute time and date the communication device was last used. This provides an indication as to how likely a user is to answerthewhen contacting that device. A device that has not been used in a while may still be OPEN, but a watcher may choose to first contact a device that is both OPEN and has been used more recently. Note that the idle time refers to the whole device, notmarked as idle.just the particular service. For example, a tuple describing an instant messaging device expresses the last time that the PC or PDA was used, not the last time an instant message has been sent. For tuples representing a 'presentity' or 'service' with multiple devices, the device with the most recent usage, i.e., the shortest idle time, determines the idle time for the whole tuple. The use of 'idle' for tuples with contact-type 'in-person' is not defined. The <idle> element can be empty if the presentity wants to indicate that the device has not been used for a while, but does not want to reveal the preciseduration:duration, as in: <idle/> The <idle> element SHOULD be included in the presence document if the idle time exceeds a user-setable threshold, with a RECOMMENDED default value of 10 minutes. Configuration MUST include the option to omit the timestamp. 4.6 Type of Place Element The <placetype> element describes the type of place the presentity is currently at. This offers the watcher an indication what kind of communication is likely to be appropriate. We define an initial set of values below: home: The presentity is in a private or residential setting, not necessarily the personal residence of the presentity, e.g., including hotel or a friend's home. office: The presentity is in a business setting, such as an office. quiet: The presentity is in a place such as a library, restaurant, place-of-worship, or theater that discourages noise, conversation and other distractions. public: The presentity is in a public area such as a shopping mall, street, park, public building, train station, airport or in public conveyance such as a bus, train, plane or ship.Alternatively,This general description encompasses the moredetailed indications below may be provided.precise descriptors 'street', 'public-transport', 'aircraft', 'ship', 'bus', 'train', 'airport', 'mall' and 'outdoors' below. street: Walking in a street. public-transport: Any form of public transport, including aircraft, bus, train or ship. aircraft: The presentity is in a plane, helicopter or balloon. ship: Water vessel, boat. bus: Public or charter bus. train: The presentity is traveling in a train, monorail, maglev, cablecar.car or similar conveyance. airport: Airport, heliport or similar location. station: Bus or train station. mall: Shopping mall or shopping area. outdoors: General outdoors area, such as a park or city streets. This list can be augmented by free-text values or additional IANA-registered values (Section Section 7). The <placetype> elementMAYcan bequalifiedused with tuples of all values of <contact-type>. For tuples consisting of multiple physical devices, i.e., of <contact-type> 'service' or 'presentity', these devices can be in multiple types of places. In those cases, the'from' and 'until' attributes to describe the time when the element assumed this value and the time until which is<placetype> elementis expected to be valid.enumerates all unique values as a token list. The'from' time MUST<placetype> element MAY bein the past,qualified with the 'since' and 'until'timeattributes as described inthe future relative to the publication of the presence information.Section 4. 4.7 Privacy Element The 'privacy' element indicates whether third parties may be able to hear or view parts of the communication. public: Others may be able to see or hear the communications. private: Inappropriate individuals are not likely to see or hear the communications.quiet: The presentity is in a place such as a library, restaurant, place-of-worship, or theater that discourages noise, conversation and other distractions.This indication is not limited to voice communications. For example, a presentity might label her privacy as "quiet" when giving a talk, since it would be inappropriate if an instant message popped up on the laptop screen that is being projected for the audience. The'activity''placetype' element MAY be qualified with the'from''since' and 'until' attributesto describe the time when the element assumed this value and the time until which is element is expected to be valid. The 'from' time MUST be in the past, the 'until' timeas described inthe future relative to the publication of the presence information.Section 4. 4.8 Relationship Element The <relationship> element extends <tuple> and designates the type of relationship an alternate contact has with the presentity. This element is provided only if the tuple refers to somebody other than the presentity. Relationship values include "family", "associate" (e.g., for a colleague), "assistant", "supervisor". Other free-text values and additional IANA-registered values (SectionSection7) can be used as well. If a relationship is indicated, the RPID <status> values describe the <contact>, not the presentity. The <contact> element for tuples labeled with a relationship can contain either a communication URI such as "im", "sip"/"sips", "h323", "tel" or "mailto", or a presence URI, such as "pres" or "sip". 4.9 Sphere Element The <sphere> element designates the current state and role that the presentity plays. For example, it might describe whether the presentity is in a work mode or at home or participating in activities related to some other organization such as the IETF or a church. This document does not define names for these spheres except for two common ones, "work" and "home". Spheres are likely to be used for two purposes: they allow the presentity to easily turn on or off certain rules that depend on what groups of people should be made aware of the presentity's status. For example, if the presentity is a Boy Scout leader, he might set the sphere to 'scouting' and then have a rule set that allows other scout masters in his troup to see his presence status. As soon as he switches his status to 'work' or 'home' or some other sphere, the fellow scouts would lose access. The <sphere> element can be used with tuples of all values of <contact-type>. For tuples representing multiple physical devices, <contact-type> 'service' or 'presentity', these devices can be controlled by people in multiple different spheres. In those cases, the <sphere> element enumerates all unique values as a token list. The <sphere> element MAY be qualified with the 'since' and 'until' attributes as described in Section 4. 5. Examples 5.1 Presentity with Activity <?xml version="1.0" encoding="UTF-8"?> <presence xmlns="urn:ietf:params:xml:ns:pidf"xmlns:es="urn:ietf:params:xml:ns:pidf:rpid-status"xmlns:ep="urn:ietf:params:xml:ns:pidf:status:rpid-status" xmlns:et="urn:ietf:params:xml:ns:pidf:rpid-tuple" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" entity="pres:someone@example.com"><note>I'm in a boring meeting</note><tupleid="7c8dqui"> <et:class>assistant</et:class> <et:contact-type>presentity</et:contact-type>id="c8dqui"> <status> <basic>open</basic><contact>sip:secretary@example.com</contact><ep:relationship>assistant</ep:relationship> </status> <et:class>assistant</et:class> <et:contact-type>presentity</et:contact-type> <contact>sip:secretary@example.com</contact> <note>My secretary</note> </tuple> <tupleid="18x765"> <et:class>sip</et:class> <et:contact-type>service</et:contact-type>id="x765"> <status> <basic>open</basic><ep:activity>meeting</ep:meeting><ep:activity> <ep:activity>meeting</ep:activity></ep:activity> <ep:placetype until="2003-01-27T17:30:00Z">office</ep:placetype> <ep:privacy>quiet</ep:privacy> <ep:idle>2003-01-27T10:43:00Z</ep:idle> </status> <et:class>sip</et:class> <et:contact-type>service</et:contact-type> <contact priority="0.8">sip:someone@example.com</contact> <timestamp>2001-10-27T16:49:29Z</timestamp> </tuple> <tupleid="35bs9r"> <et:class>phone</et:class> <et:contact-type>device</et:contact-type>id="bs9r"> <status> <basic>open</basic> <ep:privacy>quiet</ep:privacy> </status> <contact priority="0.8">im:someone@mobilecarrier.net</contact> <timestamp>2001-10-27T16:49:29Z</timestamp> </tuple> <tupleid="8eg92n"> <et:class>mail</et:class> <et:contact-type>device</et:contact-type>id="eg92n"> <status> <basic>open</basic> </status> <et:class>mail</et:class> <nn:blah>blah</nn:blah> <et:contact-type>device</et:contact-type> <contact priority="1.0">mailto:someone@example.com</contact> <note>I'm in a boring meeting</note> </tuple> </presence> 6. XML Schema Definitions 6.1 urn:ietf:params:xml:ns:pidf:rpid-tuple <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns="urn:ietf:params:xml:ns:pidf:rpid-tuple" xmlns:pidf="urn:ietf:params:xml:ns:pidf" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"> <!-- This import brings in the XML language attribute xml:lang--> <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"/> <xs:annotation> <xs:documentation xml:lang="en"> Describes RPID tuple extensions for PIDF. </xs:documentation> </xs:annotation> <xs:element name="contact-type"> <xs:simpleType> <xs:restriction base="xs:token"> <xs:enumeration value="device"/> <xs:enumeration value="in-person"/> <xs:enumeration value="service"/> <xs:enumeration value="presentity"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="class" type="xs:token"/> <xs:element name="relationship" type="xs:token"/> </xs:schema> 6.2 urn:ietf:params:xml:ns:pidf:status:rpid-status <?xml version="1.0" encoding="UTF-8"?> <!-- edited with XMLSPY v2004 rel. 3 U (http://www.xmlspy.com) by Henning Schulzrinne (Columbia University) --> <xs:schema xmlns="urn:ietf:params:xml:ns:pidf:status:rpid-status" xmlns:pidf="urn:ietf:params:xml:ns:pidf" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"> <!-- This import brings in the XML language attribute xml:lang--> <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"/> <xs:annotation> <xs:documentation xml:lang="en"> Describes RPID status extensions for PIDF. </xs:documentation> </xs:annotation> <xs:attributeGroup name="SinceUntil"> <xs:attribute name="since" type="xs:dateTime"/> <xs:attribute name="until" type="xs:dateTime"/> </xs:attributeGroup> <xs:simpleType name="tokenlist"> <xs:list itemType="xs:token"/> </xs:simpleType> <xs:element name="activities"> <xs:complexType> <xs:sequence> <xs:element name="activity"type="activity_t"/> <xs:simpleType name="activityToken">minOccurs="0" maxOccurs="unbounded"> <xs:simpleType> <xs:restriction base="xs:token"> <xs:enumeration value="holiday"/> <xs:enumeration value="on-the-phone"/> <xs:enumeration value="away"/> <xs:enumeration value="appointment"/> <xs:enumeration value="meal"/> <xs:enumeration value="meeting"/> <xs:enumeration value="steering"/> <xs:enumeration value="in-transit"/> <xs:enumeration value="travel"/> <xs:enumeration value="vacation"/> <xs:enumeration value="sleeping"/> <xs:enumeration value="busy"/> <xs:enumeration value="permanent-absence"/> </xs:restriction> </xs:simpleType><xs:complexType name="activity_t"> <xs:sequence> <xs:element name="activity" type="activityToken"/></xs:element> <xs:any maxOccurs="unbounded"/> </xs:sequence><xs:attribute name="from" type="xs:dateTime"/></xs:complexType> </xs:element> <xs:element name="placetype"> <xs:complexType> <xs:simpleContent> <xs:extensionbase="xs:token"> <xs:attribute name="from" type="xs:dateTime"/> <xs:attribute name="until" type="xs:dateTime"/>base="tokenlist"> <xs:attributeGroup ref="SinceUntil"/> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element><xs:simpleType name="privacy_t"> <xs:restriction base="xs:token"> <xs:enumeration value="private"/> <xs:enumeration value="public"/> <xs:enumeration value="quiet"/> </xs:restriction> </xs:simpleType><xs:element name="privacy"> <xs:complexType> <xs:simpleContent> <xs:extensionbase="privacy_t"> <xs:attribute name="from" type="xs:dateTime"/> <xs:attribute name="until" type="xs:dateTime"/>base="tokenlist"> <xs:attributeGroup ref="SinceUntil"/> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element><xs:simpleType name="sphereToken"> <xs:restriction base="xs:token"> </xs:restriction> </xs:simpleType> <xs:complexType name="sphere_t"> <xs:sequence> <xs:element name="sphere" type="sphereToken"/> </xs:sequence> </xs:complexType><xs:element name="sphere"> <xs:complexType><xs:complexContent><xs:simpleContent> <xs:extensionbase="sphere_t"> <xs:attribute name="from" type="xs:dateTime"/> <xs:attribute name="until" type="xs:dateTime"/>base="tokenlist"> <xs:attributeGroup ref="SinceUntil"/> </xs:extension></xs:complexContent></xs:simpleContent> </xs:complexType> </xs:element> <xs:elementname="relationship" type="xs:token"/> <xs:element name="idle"name="idle"> <xs:complexType> <xs:attribute name="since" type="xs:dateTime"/> </xs:complexType> </xs:element> </xs:schema> 7. IANA Considerations This document calls for IANA to: o register two new XML namespace URNs per[5];[6]; o establish registry for activity categories (SectionSection 4.2,4.2), place types (SectionSection4.6), and relationships (SectionSection4.8). Note that this document does not need a new content type. It inherits the content type from[6],[7], namelyapplication/cpim-pidf+xml.application/pidf+xml. 7.1 URN Sub-Namespace Registration for'urn:ietf:params:xml:ns:pidf:rpid-status''urn:ietf:params:xml:ns:pidf:status:rpid-status' URI:urn:ietf:params:xml:ns:rpid-statusurn:ietf:params:xml:ns:pidf:status:rpid-status Description: This is the XML namespace for XML elements defined byRFCXXXXRFC&rfc.number [RFC editor: replace with RFC number]; to describe rich presence information extensions for the status element in the PIDF presence document format in theapplication/cpim-pidf+xmlapplication/pidf+xml content type. Registrant Contact: IETF, SIMPLE working group, simple@ietf.org, Henning Schulzrinne, hgs@cs.columbia.edu XML: BEGIN <?xml version="1.0"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> <html xmlns="http://www.w3.org/1999/xhtml <head> <meta http-equiv="content-type" content="text/html;charset=iso-8859-1"/><title>RPID --<title>RPID: Rich Presence: Extensions to the Presence Information Data Formatfor Presence</title>(PIDF)</title> </head> <body> <h1>Namespace for rich presence extension (status)</h1><h2>application/pidf+xml</h2><h2>urn:ietf:params:xml:ns:pidf:status:rpid-status</h2> <p>See <a href="URL of publishedRFC">RFCXXXX</a>.</p>RFC">RFC&rfc.number; [RFC editor: replace with RFC number]</a>.</p> </body> </html> END 7.2 URN Sub-Namespace Registration for 'urn:ietf:params:xml:ns:pidf:rpid-tuple'urn:ietf:params:xml:ns:rpid-tupleURI: urn:ietf:params:xml:ns:pidf:rpid-tuple Description: This is the XML namespace for XML elements defined by RFCXXXX [RFC editor: replace with RFC number] to describe rich presence information extensions for the tuple element in the PIDF presence document format in theapplication/cpim-pidf+xmlapplication/pidf+xml content type. Registrant Contact: IETF, SIMPLE working group, simple@ietf.org, Henning Schulzrinne, hgs@cs.columbia.edu. XML: BEGIN <?xml version="1.0"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> <html xmlns="http://www.w3.org/1999/xhtml <head> <meta http-equiv="content-type" content="text/html;charset=iso-8859-1"/><title>RPID --<title>RPID: Rich Presence: Extensions to the Presence Information Data Formatfor Presence</title>(PIDF)</title> </head> <body> <h1>Namespace for rich presence extension (tuple)</h1><h2>application/pidf+xml</h2><h2>urn:ietf:params:xml:ns:pidf:rpid-tuple</h2> <p>See <a href="URL of publishedRFC">RFCXXXX</a>.</p>RFC">RFC&rfc.number; [RFC editor: replace with RFC number]</a>.</p> </body> </html> END 7.3Place Type, Tuple Type, Activities, RelationshipsSchema Registration for Schema urn:ietf:params:xml:ns:pidf:rpid-tuple' URI: please assign Registrant Contact: IESG XML: See Section 6.1 7.4 Schema Registration for Schema urn:ietf:params:xml:ns:pidf:status:rpid-status' URI: please assign Registrant Contact: IESG XML: See Section 6.2 7.5 Token Registrations This document creates new IANA registries foractivities, tuple types, place types and relationships.RPID tokens: contact-type: See Section 4.4 placetype: See Section 4.6 privacy: See Section 4.7 relationship: See Section 4.8 All are XML tokens. Registered tokens must be documented at the time of registration, as most descriptions are expected to be brief.The SIMPLE working group, or, if no longer available,Following the policies outline in RFC 2434 [3], these tokens are assigned after Expert Review by theSIPSIMPLE working groupshould be consulted prioror its designated successor. Each registration must include the name of the token and a brief description similar toregistration.the ones offered in for the initial registrations contained this document. 8. Security Considerations The security considerations in[6][7] apply, as well as[7].[8]. Compared to PIDF, this presence document format reveals additional information that can be highly sensitive. Beyond traditional security measures to protect confidentiality and integrity, systems should offer a means to selectively reveal information to particular watchers and to inspect the information that is being published, particularly if it is generated automatically from other sources, such as calendars or sensors. Normative References [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [2] Moats, R., "URN Syntax", RFC 2141, May 1997. [3] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998. [4] Moats, R., "A URN Namespace for IETF Documents", RFC 2648, August 1999.[4][5] Day, M., Rosenberg, J. and H. Sugano, "A Model for Presence and Instant Messaging", RFC 2778, February 2000.[5][6] Mealling, M., "The IETF XML Registry",draft-mealling-iana-xmlns-registry-05 (work in progress), June 2003. [6]BCP 81, RFC 3688, January 2004. [7] Sugano, H. and S. Fujimoto, "Presence Information Data Format (PIDF)", draft-ietf-impp-cpim-pidf-08 (work in progress), May 2003.[7][8] Rosenberg, J., "A Presence Event Package for the Session Initiation Protocol (SIP)", draft-ietf-simple-presence-10 (work in progress), January 2003. Informative References[8][9] Handley, M. and V. Jacobson, "SDP: Session Description Protocol", RFC 2327, April 1998.[9][10] Dawson, F. and Stenerson, D., "Internet Calendaring and Scheduling Core Object Specification (iCalendar)", RFC 2445, November 1998.[10][11] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with Session Description Protocol (SDP)", RFC 3264, June 2002.[11][12] Lennox, J., Wu, X. and H. Schulzrinne, "CPL: A Language for User Control of Internet Telephony Services", draft-ietf-iptel-cpl-08 (work in progress), August 2003.[12][13] Dawson, F., Reddy, S., Royer, D. and E. Plamondon, "iCalendar DTD Document (xCal)", draft-ietf-calsch-many-xcal-02 (work in progress), July 2002. Authors' Addresses Henning Schulzrinne Columbia University Department of Computer Science 450 Computer Science Building New York, NY 10027 US Phone: +1 212 939 7042 EMail: hgs+simple@cs.columbia.edu URI: http://www.cs.columbia.edu Vijay Gurbani Lucent 2000 Naperville Rd. Room 6G-440 Naperville, IL 60566-7033 US EMail: vkg@lucent.com Paul Kyzivat Cisco Systems BXB500 C2-2 1414 Massachusetts Avenue Boxborough, MA 01719 US EMail: pkzivat@cisco.com Jonathan Rosenberg dynamicsoft 600 Lanidex Plaza Parsippany, NJ 07054-2711 US EMail: jdrosen@dynamicsoft.com Appendix A. Acknowledgements The document reflects the discussion on the SIMPLE mailing list, with contributions from many individuals. Markus Isomaki, Hisham Khartabil, Jon Peterson and Brian Rosen provided detailed comments and suggestions. Xiaotao Wu assisted with schema testing. Intellectual Property Statement The IETF takes no position regarding the validity or scope of anyintellectual propertyIntellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available;neithernor does it represent that it has made any independent effort to identify any such rights. Information on the IETF's procedures with respect to rights instandards-track and standards-related documentationIETF Documents can be found inBCP-11.BCP 78 and BCP 79. Copies ofclaims of rightsIPR disclosures madeavailable for publicationto the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights byimplementorsimplementers or users of this specification can be obtained from the IETFSecretariat.on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rightswhichthat may cover technology that may be required topracticeimplement this standard. Please address the information to the IETFExecutive Director. Full Copyright Statement Copyright (C) The Internet Society (2004). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purposeat ietf-ipr@ietf.org. Disclaimer ofdeveloping Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assignees.Validity This document and the information contained hereinisare provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCEDISCLAIMSDISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Copyright Statement Copyright (C) The Internet Society (2004). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society.