draft-ietf-simple-xcap-list-usage-00.txt   draft-ietf-simple-xcap-list-usage-01.txt 
SIMPLE J. Rosenberg SIMPLE J. Rosenberg
Internet-Draft dynamicsoft Internet-Draft dynamicsoft
Expires: December 22, 2003 June 23, 2003 Expires: April 26, 2004 October 27, 2003
An Extensible Markup Language (XML) Configuration Access Protocol An Extensible Markup Language (XML) Configuration Access Protocol
(XCAP) Usage for Presence Lists (XCAP) Usage for Resource Lists
draft-ietf-simple-xcap-list-usage-00 draft-ietf-simple-xcap-list-usage-01
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
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
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
skipping to change at page 1, line 31 skipping to change at page 1, line 31
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 December 22, 2003. This Internet-Draft will expire on April 26, 2004.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract Abstract
This document describes a usage of the Extensible Markup Language This document describes a usage of the Extensible Markup Language
(XML) Configuration Access Protocol (XCAP) for manipulating lists of (XML) Configuration Access Protocol (XCAP) for manipulating lists of
presentities (also known as buddy lists or rosters). It does so by resources. These lists can be used as presence lists (also known as
specifying an XML Schema that contains a list of presentities that a buddy lists or rosters), but this specification does not restrict
user is interested in watching. their usage to that.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Application Unique ID . . . . . . . . . . . . . . . . . . . 5 3. Application Unique ID . . . . . . . . . . . . . . . . . . . 5
4. Structure of a Presence List . . . . . . . . . . . . . . . . 6 4. Structure of a Resource List . . . . . . . . . . . . . . . . 6
5. Computed Data . . . . . . . . . . . . . . . . . . . . . . . 8 5. Resource Interdependencies . . . . . . . . . . . . . . . . . 8
6. Additional Constraints . . . . . . . . . . . . . . . . . . . 9 6. Additional Constraints . . . . . . . . . . . . . . . . . . . 9
7. Naming Conventions . . . . . . . . . . . . . . . . . . . . . 10 7. Naming Conventions . . . . . . . . . . . . . . . . . . . . . 10
8. Authorization Policies . . . . . . . . . . . . . . . . . . . 11 8. Authorization Policies . . . . . . . . . . . . . . . . . . . 11
9. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . 12 9. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . 12
10. Example Document . . . . . . . . . . . . . . . . . . . . . . 13 10. Example Document . . . . . . . . . . . . . . . . . . . . . . 14
11. Security Considerations . . . . . . . . . . . . . . . . . . 14 11. Security Considerations . . . . . . . . . . . . . . . . . . 15
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . 15 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . 16
12.1 XCAP Application Usage ID . . . . . . . . . . . . . . . . . 15 12.1 XCAP Application Usage ID . . . . . . . . . . . . . . . . . 16
12.2 application/presence-lists+xml MIME Type . . . . . . . . . . 15 12.2 application/resource-lists+xml MIME Type . . . . . . . . . . 16
12.3 URN Sub-Namespace Registration for 12.3 URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:presence-lists . . . . . . . . . . . 16 urn:ietf:params:xml:ns:resource-lists . . . . . . . . . . . 17
Normative References . . . . . . . . . . . . . . . . . . . . 17 Normative References . . . . . . . . . . . . . . . . . . . . 18
Informative References . . . . . . . . . . . . . . . . . . . 18 Informative References . . . . . . . . . . . . . . . . . . . 19
Author's Address . . . . . . . . . . . . . . . . . . . . . . 18 Author's Address . . . . . . . . . . . . . . . . . . . . . . 19
Intellectual Property and Copyright Statements . . . . . . . 19 Intellectual Property and Copyright Statements . . . . . . . 20
1. Introduction 1. Introduction
The Session Initiation Protocol (SIP) for Instant Messaging and In many communications applications, it is neccesary for the network
Presence (SIMPLE) specifications allow a user, called a watcher, to to have access to a list of resources that represent a group that the
subscribe to another user, called a presentity [7], in order to learn user would like to apply an action to. One such example is a presence
their presence information [8]. In many cases, a watcher will be list [13]. These lists are used by Session Initiation Protocol (SIP)
interested in not just a single presentity, but a list of for Instant Messaging and Presence (SIMPLE) [9]Resource List Servers
presentities. Such a list of presentities is called a presence list. (RLS) [11] for processing list subscriptions. Another example might
be list of recipients for an instant message, or a list of users to
When a user wants to subscribe to their presence list, the procedures invite to a conference bridge.
in [8] require the watcher to create and manage a subscription for
each presentity in their list. For large lists, the bandwidth
required to do this can be a problem, particularly for wireless
networks. An extension to the SIP events framework [9] has been
defined. The extension allows a watcher to subscribe to a list of
resources, using a single subscription [10]. This mechanism assumes
that a server, called the Resource List Server (RLS) has a copy of
the presence list that the user wishes to subscribe to. By using
protocols such as the XML Configuration Access Protocol (XCAP) [12],
a client can place this list on the server, and manipulate it as
needed.
XCAP requires application usages to standardize several pieces of Generally, these lists will need to be manipulated by the end users
information, including an application unique ID (AUID), an XML of the system, and used by servers in the network. To support such
schema, and various other pieces of information. This specification manipulations, the XML Configuration Access Protocol (XCAP) [7] has
fulfills those requirements. been defined. XCAP requires application usages to standardize several
pieces of information, including an application unique ID (AUID), an
XML schema, and various other pieces of information. This
specification fulfills those requirements.
The XML schema defined here has several other usages outside of XCAP: The XML schema defined here has several other usages outside of XCAP:
1. A PC client application will need to know the users in the 1. A PC client application will need to know the users in the
presence list, so that it can generate a subscription to each presence list, so that it can generate a subscription to each
one. This information represents user provisioned data for the one. This information represents user provisioned data for the
application. Typically, this information is stored on local disk application. Typically, this information is stored on local disk
in a proprietary file format. By defining a standard format, the in a proprietary file format. By defining a standard format, the
same list can be used by a multiplicity of different client same list can be used by a multiplicity of different client
applications, providing portability across them. applications, providing portability across them.
skipping to change at page 5, line 9 skipping to change at page 5, line 9
In this document, the key words "MUST", "MUST NOT", "REQUIRED", In this document, the key words "MUST", "MUST NOT", "REQUIRED",
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
and "OPTIONAL" are to be interpreted as described in RFC 2119 [1] and and "OPTIONAL" are to be interpreted as described in RFC 2119 [1] and
indicate requirement levels for compliant implementations. indicate requirement levels for compliant implementations.
3. Application Unique ID 3. Application Unique ID
XCAP requires application usages to define a unique application usage XCAP requires application usages to define a unique application usage
ID (AUID) in either the IETF tree or a vendor tree. This ID (AUID) in either the IETF tree or a vendor tree. This
specification defines the "presence-lists" AUID within the IETF tree, specification defines the "resource-lists" AUID within the IETF tree,
via the IANA registration in Section 12. via the IANA registration in Section 12.
4. Structure of a Presence List 4. Structure of a Resource List
A presence list is an XML [2] document that MUST be well-formed and A resource list is an XML [2] document that MUST be well-formed and
SHOULD be valid. Presence list documents MUST be based on XML 1.0 and SHOULD be valid. Resource list documents MUST be based on XML 1.0 and
MUST be encoded using UTF-8. This specification makes use of XML MUST be encoded using UTF-8. This specification makes use of XML
namespaces for identifying presence list documents and document namespaces for identifying resource list documents and document
fragments. The namespace URI for elements defined by this fragments. The namespace URI for elements defined by this
specification is a URN [3], using the namespace identifier 'ietf' specification is a URN [3], using the namespace identifier 'ietf'
defined by [5] and extended by [6]. This URN is: defined by [5] and extended by [6]. This URN is:
urn:ietf:params:xml:ns:presence-lists urn:ietf:params:xml:ns:resource-lists
A presence list document begins with the root element tag A resource list document begins with the root element tag
``presence-lists''. It consists of any number of ``list'' ``resource-lists''. It consists of any number of ``list''
sub-elements, each of which is a presence list. Other elements from sub-elements, each of which is a resource list. Other elements from
different namespaces MAY be present for the purposes of different namespaces MAY be present for the purposes of
extensibility; elements or attributes from unknown namespaces MUST be extensibility; elements or attributes from unknown namespaces MUST be
ignored. There are three attributes associated with this element. The ignored. There are three attributes associated with this element. The
first two, "name", and "subscribable" MUST be present: first, "name", MUST be present:
name: This attribute is a descriptive name for the list. It MUST name: This attribute is a descriptive name for the list. It MUST
be unique amongst all other list elements within the same parent be unique amongst all other list elements within the same parent
element. element.
subscribable: This boolean attribute indicates whether or not the Each list element will also have boolean attributes which indicate a
list is subscribable or not. specific action that may be made against that list. This
specification defines a single attribute - subscribeable - which
The other attribute, "uri" MAY be present: indicates that the list may be subscribed to using the SIP event list
specification [11]. Extensions to this application usage MAY define
uri: This attribute provides a URI that can be used to subscribe additional boolean elements, each within a different namespace, for
to the list, using the SIP event notification extension for lists the purposes of indicating other actions that may be peformed. When
[10]. As a result, the URI MUST be either a SIP URI or a pres URI an attribute is absent, it implies that the operation is not
[11]. [[OPEN ISSUE: Do we want this to be a comma separated list, supported.
so that a presence list can have any number of valid aliases?]]
[[OPEN ISSUE: We also need to define policy about who is allowed to The third other attribute, "uri" MAY be present. It provides a URI
subscribe to the list. We can either integrate that into the list that can be used to access the list, for example, using the SIP event
definition described here, or handle that as a separate policy notification extension for lists [11]. As a result, the URI MUST be
specification. The SEACAP proposal kept them together. I believe now either a SIP URI or a pres URI [12].
that they should be kept separate.]]
Each list element is composed of a sequence of entry elements or list Each list element is composed of a sequence of entry elements, list
elements. The ability of a list element to contain other list elements, external elements. The ability of a list element to contain
elements means that a presence list can be hierarchically structured. other list elements means that a resource list can be hierarchically
An entry element describes a single presentity that is part of the structured. An entry element describes a single presentity that is
list. A list element can also contain elements from other namespaces, part of the list. An external element contains a reference to a list
for the purposes of extensibility. stored on another server. A list element can also contain elements
from other namespaces, for the purposes of extensibility.
The entry element describes a single presentity. The entry element The entry element describes a single resource. The entry element has
has two attributes: two attributes:
name: This mandatory attribute is a unique identifier amongst all name: This mandatory attribute is a unique identifier amongst all
other entry elements of the same parent. other entry elements of the same parent.
uri: This optional attribute is a URI that is used to subscribe to uri: This optional attribute is a URI that is used to access the
the presentity. It MUST be either a SIP or pres URI. resource. It MUST be either a SIP or pres URI.
The entry element contains a sequence of other elements. Only one The entry element contains a sequence of other elements. Only one
such element is defined at this time, which is the display-name. This such element is defined at this time, which is the display-name. This
element provides a UTF-8 encoded string, meant for consumption by the element provides a UTF-8 encoded string, meant for consumption by the
user, that describes the presentity. Unlike the "name" attribute of user, that describes the resource. Unlike the "name" attribute of the
the entry element, the display-name has no uniqueness requirements. entry element, the display-name has no uniqueness requirements. Other
[[OPEN ISSUE: Do we need this in addition to the name attribute?]]. elements from other namespaces MAY be included. This is meant to
Other elements from other namespaces MAY be included. This is meant support the inclusion of other information about the entry, such as a
to support the inclusion of other information about the entry, such phone number or postal address.
as a phone number or postal address.
5. Computed Data 5. Resource Interdependencies
An XCAP server supporting this application usage need only worry An XCAP server supporting this application usage need only worry
about a single piece of computed data - the "uri" attribute of the about a single data interdependency - the "uri" attribute of the list
list element. element.
If the "uri" attribute is absent in a document written to an XCAP If the "uri" attribute is absent in a document written to an XCAP
server, but the "subscribable" flag is true, the XCAP server MUST server, but the "subscribeable" flag is true, the XCAP server MUST
allocate a URI for this list. This allocated URI MUST be globally allocate a URI for this list. This allocated URI MUST be globally
unique, and MUST route to an RLS which will handle list subscriptions unique, and MUST route to an RLS which will handle list subscriptions
for the list defined by the document. The server MUST set the uri for the list defined by the document. The server MUST set the uri
attribute of the document with this URI. attribute of the document with this URI.
A server MUST NOT delete the "uri" attribute, however, should a A server MUST NOT delete the "uri" attribute, however, should a
client change the subscribable flag to false after the server has client change the subscribeable flag to false after the server has
allocated a URI. allocated a URI.
6. Additional Constraints 6. Additional Constraints
There are no constraints on the document beyond those described in There are no constraints on the document beyond those described in
the schema. the schema.
7. Naming Conventions 7. Naming Conventions
There are no naming conventions that need to be defined for this There are no naming conventions that need to be defined for this
application usage. A subscription to a presence list will be to a application usage. A subscription to a resource list will be to a
specific URI. That URI will be one of the "uri" attributes defined in specific URI. That URI will be one of the "uri" attributes defined in
a list within one of the documents managed by an XCAP server. a list within one of the documents managed by an XCAP server.
8. Authorization Policies 8. Authorization Policies
This application usage does not modify the default XCAP authorization This application usage does not modify the default XCAP authorization
policy, which is that only a user can read, write or modify their own policy, which is that only a user can read, write or modify their own
documents. A server can allow priveleged users to modify documents documents. A server can allow priveleged users to modify documents
that they don't own, but the establishment and indication of such that they don't own, but the establishment and indication of such
policies is outside the scope of this document. policies is outside the scope of this document. It is anticipated
that a future application usage will define which users are allowed
to modify a list resource.
9. XML Schema 9. XML Schema
The following is the XML schema definition of the presence list: The following is the XML schema definition of the resource list:
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" <xs:schema targetNamespace="urn:ietf:params:xml:ns:resource-lists"
elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema"
attributeFormDefault="unqualified"> xmlns="urn:ietf:params:xml:ns:resource-lists"
<xs:element name="presence-lists"> elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:element name="resource-lists">
<xs:complexType> <xs:complexType>
<xs:sequence> <xs:sequence>
<xs:element name="list" type="listType" minOccurs="0" <xs:element name="list" type="listType" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
</xs:element> </xs:element>
<xs:complexType name="listType"> <xs:complexType name="listType">
<xs:sequence maxOccurs="unbounded"> <xs:sequence maxOccurs="unbounded">
<xs:choice> <xs:choice>
<xs:element name="list" type="listType" minOccurs="0" <xs:element name="list" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:complexContent>
<xs:extension base="listType"/>
</xs:complexContent>
</xs:complexType>
</xs:element>
<xs:element name="external" type="xs:anyURI" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
<xs:element name="entry" type="entryType" minOccurs="0" <xs:element name="entry" type="entryType" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
<xs:any namespace="##other" processContents="lax" <xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</xs:choice> </xs:choice>
</xs:sequence> </xs:sequence>
<xs:attribute name="name" type="xs:string" use="required"/> <xs:attribute name="name" type="xs:string" use="required"/>
<xs:attribute name="uri" type="xs:anyURI" use="optional"/> <xs:attribute name="uri" type="xs:anyURI" use="optional"/>
<xs:attribute name="subscribable" type="xs:boolean" use="required" /> <xs:attribute name="subscribeable" type="xs:boolean" use="optional"/>
<xs:anyAttribute namespace="##other"/>
</xs:complexType> </xs:complexType>
<xs:complexType name="entryType"> <xs:complexType name="entryType">
<xs:sequence> <xs:sequence>
<xs:element name="display-name" type="display-nameType"/> <xs:element name="display-name" type="display-nameType"/>
<xs:any namespace="##other" processContents="lax" <xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:attribute name="name" type="xs:string" use="required"/> <xs:attribute name="name" type="xs:string" use="required"/>
<xs:attribute name="uri" type="xs:anyURI" use="optional"/> <xs:attribute name="uri" type="xs:anyURI" use="optional"/>
</xs:complexType> </xs:complexType>
<xs:simpleType name="display-nameType"> <xs:simpleType name="display-nameType">
<xs:restriction base="xs:string"/> <xs:restriction base="xs:string"/>
</xs:simpleType> </xs:simpleType>
</xs:schema> </xs:schema>
10. Example Document 10. Example Document
The following is an example of a document compliant to the schema: The following is an example of a document compliant to the schema:
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<presence-lists xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <resource-lists xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<list name="friends" uri="sip:friends@example.com" subscribable="true"> <list name="friends" uri="sip:friends@example.com" subscribeable="true">
<entry name="Bill" uri="sip:bill@example.com"> <entry name="Bill" uri="sip:bill@example.com">
<display-name>Bill Doe</display-name> <display-name>Bill Doe</display-name>
</entry> </entry>
<list name="close-friends" uri="sip:close-friends@example.com" <list name="close-friends" uri="sip:close-friends@example.com"
subscribable="true"> subscribeable="true">
<entry name="Joe" uri="sip:joe@example.com"> <entry name="Joe" uri="sip:joe@example.com">
<display-name>Joe Smith</display-name> <display-name>Joe Smith</display-name>
</entry> </entry>
<entry name="Nancy" uri="sip:nancy@example.com"> <entry name="Nancy" uri="sip:nancy@example.com">
<display-name>Nancy Gross</display-name> <display-name>Nancy Gross</display-name>
</entry> </entry>
<external>http://www.example.org/xcap/resource-lists/users/a/foo
</external>
</list> </list>
</list> </list>
</presence-lists> </resource-lists>
TODO: formally validate against schema.
11. Security Considerations 11. Security Considerations
The configuration information defined by this application usage is The configuration information defined by this application usage is
particularly sensitive. It represents the principle set of people particularly sensitive. It represents the principle set of people
with whom a user would like to communicate. As a result, clients with whom a user would like to communicate. As a result, clients
SHOULD use TLS when contacting servers in order to fetch this SHOULD use TLS when contacting servers in order to fetch this
information. Note that this does not represent a change in information. Note that this does not represent a change in
requirement strength from XCAP. requirement strength from XCAP.
12. IANA Considerations 12. IANA Considerations
There are several IANA considerations associated with this There are several IANA considerations associated with this
specification. specification.
12.1 XCAP Application Usage ID 12.1 XCAP Application Usage ID
This section registers a new XCAP Application Usage ID (AUID) This section registers a new XCAP Application Usage ID (AUID)
according to the IANA procedures defined in [12]. according to the IANA procedures defined in [7].
Name of the AUID: presence-lists Name of the AUID: resource-lists
Description: A presence list application is a usage of the SIP Description: A resource list application is any application that
events framework (RFC 3265) [9] along with its list extension needs access to a list of resources, identified by a URI, to which
[10], for subscribing to a list of presentities (RFC2778) [7] operations, such as subscriptions, can be applied.
stored at a server.
12.2 application/presence-lists+xml MIME Type 12.2 application/resource-lists+xml MIME Type
MIME media type name: application MIME media type name: application
MIME subtype name: presence-lists+xml MIME subtype name: resource-lists+xml
Mandatory parameters: none Mandatory parameters: none
Optional parameters: Same as charset parameter application/xml as Optional parameters: Same as charset parameter application/xml as
specified in RFC 3023 [4]. specified in RFC 3023 [4].
Encoding considerations: Same as encoding considerations of Encoding considerations: Same as encoding considerations of
application/xml as specified in RFC 3023 [4]. application/xml as specified in RFC 3023 [4].
Security considerations: See Section 10 of RFC 3023 [4] and Security considerations: See Section 10 of RFC 3023 [4] and
Section 11 of this specification. Section 11 of this specification.
Interoperability considerations: none. Interoperability considerations: none.
Published specification: This document. Published specification: This document.
Applications which use this media type: This document type has Applications which use this media type: This document type has
been used to support subscriptions to lists of users [10] for been used to support subscriptions to lists of users [11] for
SIP-based presence [8]. SIP-based presence [9].
Additional Information: Additional Information:
Magic Number: None Magic Number: None
File Extension: .pl or .xml File Extension: .rl or .xml
Macintosh file type code: "TEXT" Macintosh file type code: "TEXT"
Personal and email address for further information: Jonathan Personal and email address for further information: Jonathan
Rosenberg, jdrosen@jdrosen.net Rosenberg, jdrosen@jdrosen.net
Intended usage: COMMON Intended usage: COMMON
Author/Change controller: The IETF. Author/Change controller: The IETF.
12.3 URN Sub-Namespace Registration for 12.3 URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:presence-lists urn:ietf:params:xml:ns:resource-lists
This section registers a new XML namespace, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
[6] [6]
URI: The URI for this namespace is URI: The URI for this namespace is
urn:ietf:params:xml:ns:presence-lists. urn:ietf:params:xml:ns:resource-lists.
Registrant Contact: IETF, SIMPLE working group, Registrant Contact: IETF, SIMPLE working group, (simple@ietf.org),
(simple@mailman.dynamicsoft.com), Jonathan Rosenberg Jonathan Rosenberg (jdrosen@jdrosen.net).
(jdrosen@jdrosen.net).
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>Presence Lists Namespace</title> <title>Resource Lists Namespace</title>
</head> </head>
<body> <body>
<h1>Namespace for Presence Lists</h1> <h1>Namespace for Resource Lists</h1>
<h2>application/presence-lists+xml</h2> <h2>application/resource-lists+xml</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
Normative References Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
skipping to change at page 18, line 5 skipping to change at page 18, line 26
[4] Murata, M., St. Laurent, S. and D. Kohn, "XML Media Types", RFC [4] Murata, M., St. Laurent, S. and D. Kohn, "XML Media Types", RFC
3023, January 2001. 3023, January 2001.
[5] Moats, R., "A URN Namespace for IETF Documents", RFC 2648, [5] Moats, R., "A URN Namespace for IETF Documents", RFC 2648,
August 1999. August 1999.
[6] Mealling, M., "The IETF XML Registry", [6] Mealling, M., "The IETF XML Registry",
draft-mealling-iana-xmlns-registry-05 (work in progress), June draft-mealling-iana-xmlns-registry-05 (work in progress), June
2003. 2003.
[7] Rosenberg, J., "The Extensible Markup Language (XML)
Configuration Access Protocol (XCAP)",
draft-ietf-simple-xcap-00 (work in progress), June 2003.
Informative References Informative References
[7] Day, M., Rosenberg, J. and H. Sugano, "A Model for Presence and [8] Day, M., Rosenberg, J. and H. Sugano, "A Model for Presence and
Instant Messaging", RFC 2778, February 2000. Instant Messaging", RFC 2778, February 2000.
[8] Rosenberg, J., "A Presence Event Package for the Session [9] Rosenberg, J., "A Presence Event Package for the Session
Initiation Protocol (SIP)", draft-ietf-simple-presence-10 (work Initiation Protocol (SIP)", draft-ietf-simple-presence-10 (work
in progress), January 2003. in progress), January 2003.
[9] Roach, A., "Session Initiation Protocol (SIP)-Specific Event [10] Roach, A., "Session Initiation Protocol (SIP)-Specific Event
Notification", RFC 3265, June 2002. Notification", RFC 3265, June 2002.
[10] Rosenberg, J., Roach, A. and B. Campbell, "A Session Initiation [11] Roach, A., Rosenberg, J. and B. Campbell, "A Session Initiation
Protocol (SIP) Event Notification Extension for Resource Protocol (SIP) Event Notification Extension for Resource
Lists", draft-ietf-simple-event-list-04 (work in progress), Lists", draft-ietf-simple-event-list-04 (work in progress),
June 2003. June 2003.
[11] Peterson, J., "Common Profile for Presence (CPP)", [12] Peterson, J., "Common Profile for Presence (CPP)",
draft-ietf-impp-pres-03 (work in progress), May 2003. draft-ietf-impp-pres-04 (work in progress), October 2003.
[12] Rosenberg, J., "The Extensible Markup Language (XML) [13] Rosenberg, J. and M. Isomaki, "Requirements for Manipulation of
Configuration Access Protocol (XCAP)", Data Elements in Session Initiation Protocol (SIP) for Instant
draft-rosenberg-simple-xcap-00 (work in progress), May 2003. Messaging and Presence Leveraging Extensions (SIMPLE) Systems",
draft-ietf-simple-data-req-03 (work in progress), June 2003.
Author's Address Author's Address
Jonathan Rosenberg Jonathan Rosenberg
dynamicsoft dynamicsoft
600 Lanidex Plaza 600 Lanidex Plaza
Parsippany, NJ 07052 Parsippany, NJ 07052
US US
Phone: +1 973 952-5000 Phone: +1 973 952-5000
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/