draft-ietf-simple-xcap-list-usage-01.txt   draft-ietf-simple-xcap-list-usage-02.txt 
SIMPLE J. Rosenberg SIMPLE J. Rosenberg
Internet-Draft dynamicsoft Internet-Draft dynamicsoft
Expires: April 26, 2004 October 27, 2003 Expires: August 15, 2004 February 15, 2004
An Extensible Markup Language (XML) Configuration Access Protocol An Extensible Markup Language (XML) Format for Representing Resource
(XCAP) Usage for Resource Lists Lists
draft-ietf-simple-xcap-list-usage-01 draft-ietf-simple-xcap-list-usage-02
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 April 26, 2004. This Internet-Draft will expire on August 15, 2004.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract Abstract
This document describes a usage of the Extensible Markup Language In multimedia communications, presence and instant messaging systems,
(XML) Configuration Access Protocol (XCAP) for manipulating lists of there is a need to represent lists of Uniform Resource Identifiers
resources. These lists can be used as presence lists (also known as (URIs). These lists, which typically reside on a server, can be
buddy lists or rosters), but this specification does not restrict subscribed to, in order to learn the presence status of a group of
their usage to that. users. A Session Initiation Protocol (SIP) INVITE message can be sent
to them, causing the creation of a conference call. This
specification defines an Extensible Markup Language (XML) document
format for representing resource lists. Such a document can be
manipulated by clients using the XML Configuration Access Protocol
(XCAP), although other techniques are permitted.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Application Unique ID . . . . . . . . . . . . . . . . . . . 5 3. Structure of a Resource List . . . . . . . . . . . . . . . . . 5
4. Structure of a Resource List . . . . . . . . . . . . . . . . 6 4. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 7
5. Resource Interdependencies . . . . . . . . . . . . . . . . . 8 5. Example Document . . . . . . . . . . . . . . . . . . . . . . . 9
6. Additional Constraints . . . . . . . . . . . . . . . . . . . 9 6. Usage with XCAP . . . . . . . . . . . . . . . . . . . . . . . 10
7. Naming Conventions . . . . . . . . . . . . . . . . . . . . . 10 6.1 Application Unique ID . . . . . . . . . . . . . . . . . . . . 10
8. Authorization Policies . . . . . . . . . . . . . . . . . . . 11 6.2 MIME Type . . . . . . . . . . . . . . . . . . . . . . . . . . 10
9. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . 12 6.3 XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 10
10. Example Document . . . . . . . . . . . . . . . . . . . . . . 14 6.4 Additional Constraints . . . . . . . . . . . . . . . . . . . . 10
11. Security Considerations . . . . . . . . . . . . . . . . . . 15 6.5 Data Semantics . . . . . . . . . . . . . . . . . . . . . . . . 10
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . 16 6.6 Naming Conventions . . . . . . . . . . . . . . . . . . . . . . 10
12.1 XCAP Application Usage ID . . . . . . . . . . . . . . . . . 16 6.7 Resource Interdependencies . . . . . . . . . . . . . . . . . . 10
12.2 application/resource-lists+xml MIME Type . . . . . . . . . . 16 6.8 Authorization Policies . . . . . . . . . . . . . . . . . . . . 11
12.3 URN Sub-Namespace Registration for 7. Security Considerations . . . . . . . . . . . . . . . . . . . 12
urn:ietf:params:xml:ns:resource-lists . . . . . . . . . . . 17 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
Normative References . . . . . . . . . . . . . . . . . . . . 18 8.1 XCAP Application Usage ID . . . . . . . . . . . . . . . . . . 13
Informative References . . . . . . . . . . . . . . . . . . . 19 8.2 application/resource-lists+xml MIME Type . . . . . . . . . . . 13
Author's Address . . . . . . . . . . . . . . . . . . . . . . 19 8.3 URN Sub-Namespace Registration for
Intellectual Property and Copyright Statements . . . . . . . 20 urn:ietf:params:xml:ns:resource-lists . . . . . . . . . . . . 14
8.4 Resource List Schema Registration . . . . . . . . . . . . . . 15
Normative References . . . . . . . . . . . . . . . . . . . . . 16
Informative References . . . . . . . . . . . . . . . . . . . . 17
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 17
Intellectual Property and Copyright Statements . . . . . . . . 18
1. Introduction 1. Introduction
In many communications applications, it is neccesary for the network In multimedia communications, presence and instant messaging systems,
to have access to a list of resources that represent a group that the operations are frequently performed on lists of Uniform Resource
user would like to apply an action to. One such example is a presence Identifiers (URIs). One such example is a presence list [13]. These
list [13]. These lists are used by Session Initiation Protocol (SIP) lists are used by Session Initiation Protocol (SIP) for Instant
for Instant Messaging and Presence (SIMPLE) [9]Resource List Servers Messaging and Presence (SIMPLE) [9]Resource List Servers (RLS) [11]
(RLS) [11] for processing list subscriptions. Another example might for processing list subscriptions. A presence list can also be used
be list of recipients for an instant message, or a list of users to by a user agent that chooses to subscribe to each user in its
invite to a conference bridge. presence list, rather than using a list subscription. In such a case,
the client would read the list from local storage, and generate
subscriptions to each member.
Generally, these lists will need to be manipulated by the end users It is common for users to share presence lists. As an example, user A
of the system, and used by servers in the network. To support such may have three people in their list that they wish to tell user B
manipulations, the XML Configuration Access Protocol (XCAP) [7] has about. User A would like to send an email to user B with an
been defined. XCAP requires application usages to standardize several attachment describing these three people. Should user B open the
pieces of information, including an application unique ID (AUID), an attachment, the three people can be added to their own presence list.
XML schema, and various other pieces of information. This Doing this requires a standardized format for exchanging lists over
specification fulfills those requirements. email, instant messaging, and other communications protocols.
The XML schema defined here has several other usages outside of XCAP: There are other applications of resource lists besides presence
lists. Another example is a list of recipients for an instant
message, or a list of users to invite to a conference bridge.
1. A PC client application will need to know the users in the This specification describes a common format for representing such a
presence list, so that it can generate a subscription to each list, and for describing the set of actions which may be performed
one. This information represents user provisioned data for the against the list. Lists can be hierarchical, and can contain
application. Typically, this information is stored on local disk sub-lists referenced by a URI.
in a proprietary file format. By defining a standard format, the
same list can be used by a multiplicity of different client
applications, providing portability across them.
2. It is common for users to share presence lists. As an example, Resource list documents can be manipulated by clients using several
user A may have three people in their list that they wish to tell means. One such mechanism is the XML Configuration Access Protocol
user B about. User A would like to send an email to user B with (XCAP) [7]. This specification defines the details necessary for
an attachment describing these three people. Should user B open using XCAP to manage presence authorization documents.
the attachment, the three people can be added to their own
presence list. Doing this requires a standardized format for
exchanging lists over email, instant messaging, and other
communications protocols.
2. Terminology 2. Terminology
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. Structure of a Resource List
XCAP requires application usages to define a unique application usage
ID (AUID) in either the IETF tree or a vendor tree. This
specification defines the "resource-lists" AUID within the IETF tree,
via the IANA registration in Section 12.
4. Structure of a Resource List
A resource 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. Resource 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 resource 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 RFC 3688 [6]. This URN is:
urn:ietf:params:xml:ns:resource-lists urn:ietf:params:xml:ns:resource-lists
A resource list document begins with the root element tag A resource list document begins with the root element tag
``resource-lists''. It consists of any number of ``list'' "resource-lists". It consists of an optional "mandatory-ns" element
sub-elements, each of which is a resource list. Other elements from (defined in XCAP [7]), followed by any number of "list" sub-elements,
different namespaces MAY be present for the purposes of each of which is a resource list. Other elements from different
extensibility; elements or attributes from unknown namespaces MUST be namespaces MAY be present for the purposes of extensibility; elements
ignored. There are three attributes associated with this element. The or attributes from unknown namespaces MUST be ignored. There are
first, "name", MUST be present: three attributes associated with the "list" element. The first is
"name". This attribute is a descriptive name for the list. It MUST be
name: This attribute is a descriptive name for the list. It MUST unique amongst all other list elements within the same parent
be unique amongst all other list elements within the same parent element. It serves as a useful, but optional handle to identify a
element. list.
Each list element will also have boolean attributes which indicate a Each list element will also have boolean attributes which indicate a
specific action that may be made against that list. This specific action that may be made against that list. This
specification defines a single attribute - subscribeable - which specification defines a single attribute - "subscribeable" - which
indicates that the list may be subscribed to using the SIP event list indicates that the list may be subscribed to using the SIP event list
specification [11]. Extensions to this application usage MAY define specification [11]. This application usage does not provide any
additional boolean elements, each within a different namespace, for information on which users would be authorized to subscribe to the
the purposes of indicating other actions that may be peformed. When list, however.
an attribute is absent, it implies that the operation is not
supported. Extensions to this application usage MAY define additional boolean
elements, each within a different namespace, for the purposes of
indicating other actions that may be peformed. When an attribute is
absent, it implies that the operation is not supported.
The third other attribute, "uri" MAY be present. It provides a URI The third other attribute, "uri" MAY be present. It provides a URI
that can be used to access the list, for example, using the SIP event that can be used to access the list, for example, using the SIP event
notification extension for lists [11]. As a result, the URI MUST be notification extension for lists [11]. As a result, the URI MUST be
either a SIP URI or a pres URI [12]. either a SIP URI or a pres URI [12].
Each list element is composed of a sequence of entry elements, list Each "list" element is composed of a sequence of zero or more
elements, external elements. The ability of a list element to contain elements, each of which may be an "entry" element, a "list" element,
other list elements means that a resource list can be hierarchically an "entry-ref" element, or an "external" element. The ability of a
structured. An entry element describes a single presentity that is "list" element to contain other "list" elements means that a resource
part of the list. An external element contains a reference to a list list can be hierarchically structured. An "entry" element describes a
stored on another server. A list element can also contain elements single URI that is part of the list. An "entry-ref" element allows an
from other namespaces, for the purposes of extensibility. entry to be included by reference, rather than by value. The content
of "entry-ref" is a URI that points to an "entry" element in this
document or another. This URI MUST be an HTTP URI identifying an XCAP
resource. An "external" element contains a reference to a list stored
on another server. The content of this element MUST also be an HTTP
URI identifying an XCAP resource. A "list" element can also contain
elements from other namespaces, for the purposes of extensibility.
The entry element describes a single resource. The entry element has The "entry" element describes a single resource. The "entry" element
two attributes: has two attributes:
name: This mandatory attribute is a unique identifier amongst all name: This optional 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 access the uri: This mandatory attribute is a URI that is used to access the
resource. 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 "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 resource. Unlike the "name" attribute of the user, that describes the resource. Unlike the "name" attribute of the
entry element, the display-name has no uniqueness requirements. Other entry element, the "display-name" has no uniqueness requirements.
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. Resource Interdependencies
An XCAP server supporting this application usage need only worry
about a single data interdependency - the "uri" attribute of the list
element.
If the "uri" attribute is absent in a document written to an XCAP
server, but the "subscribeable" flag is true, the XCAP server MUST
allocate a URI for this list. This allocated URI MUST be globally
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
attribute of the document with this URI.
A server MUST NOT delete the "uri" attribute, however, should a
client change the subscribeable flag to false after the server has
allocated a URI.
6. Additional Constraints
There are no constraints on the document beyond those described in
the schema.
7. Naming Conventions
There are no naming conventions that need to be defined for this
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
a list within one of the documents managed by an XCAP server.
8. Authorization Policies
This application usage does not modify the default XCAP authorization
policy, which is that only a user can read, write or modify their own
documents. A server can allow priveleged users to modify documents
that they don't own, but the establishment and indication of such
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 4. XML Schema
The following is the XML schema definition of the resource 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 targetNamespace="urn:ietf:params:xml:ns:resource-lists" <xs:schema targetNamespace="urn:ietf:params:xml:ns:resource-lists"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xcap="urn:ietf:params:xml:ns:xcap-must-understand"
xmlns="urn:ietf:params:xml:ns:resource-lists" xmlns="urn:ietf:params:xml:ns:resource-lists"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified" attributeFormDefault="unqualified"> elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:import namespace="urn:ietf:params:xml:ns:xcap-must-understand"/>
<xs:element name="resource-lists"> <xs:element name="resource-lists">
<xs:complexType> <xs:complexType>
<xs:sequence> <xs:sequence>
<xs:element ref="xcap:mandatory-ns" minOccurs="0"/>
<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" minOccurs="0" maxOccurs="unbounded"> <xs:element name="list" minOccurs="0" maxOccurs="unbounded">
<xs:complexType> <xs:complexType>
<xs:complexContent> <xs:complexContent>
<xs:extension base="listType"/> <xs:extension base="listType"/>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
</xs:element> </xs:element>
<xs:element name="external" type="xs:anyURI" minOccurs="0" <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:element name="entry-ref" type="xs:anyURI" minOccurs="0"
minOccurs="0" maxOccurs="unbounded"/> maxOccurs="unbounded"/>
<xs:any namespace="##other" processContents="lax" 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="optional"/>
<xs:attribute name="uri" type="xs:anyURI" use="optional"/> <xs:attribute name="uri" type="xs:anyURI" use="optional"/>
<xs:attribute name="subscribeable" type="xs:boolean" use="optional"/> <xs:attribute name="subscribeable" type="xs:boolean" use="optional"/>
<xs:anyAttribute namespace="##other"/> <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" minOccurs="0"/>
<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="optional"/>
<xs:attribute name="uri" type="xs:anyURI" use="optional"/> <xs:attribute name="uri" type="xs:anyURI" use="required"/>
</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 5. 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"?> ]]>
<resource-lists xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<list name="friends" uri="sip:friends@example.com" subscribeable="true">
<entry name="Bill" uri="sip:bill@example.com">
<display-name>Bill Doe</display-name>
</entry>
<list name="close-friends" uri="sip:close-friends@example.com"
subscribeable="true">
<entry name="Joe" uri="sip:joe@example.com">
<display-name>Joe Smith</display-name>
</entry>
<entry name="Nancy" uri="sip:nancy@example.com">
<display-name>Nancy Gross</display-name>
</entry>
<external>http://www.example.org/xcap/resource-lists/users/a/foo
</external>
</list>
</list>
</resource-lists>
TODO: formally validate against schema. 6. Usage with XCAP
11. Security Considerations Resource list documents can be manipulated with XCAP. This section
provides the details necessary for such a usage.
6.1 Application Unique ID
XCAP requires application usages to define a unique application usage
ID (AUID) in either the IETF tree or a vendor tree. This
specification defines the "resource-lists" AUID within the IETF tree,
via the IANA registration in Section 8.
6.2 MIME Type
The MIME type for this document is "application/resource-lists+xml".
6.3 XML Schema
The XML Schema for this document is defined as the sole content of
Section 4.
6.4 Additional Constraints
None.
6.5 Data Semantics
Semantics for the document content are provided in Section 3.
6.6 Naming Conventions
There are no naming conventions that need to be defined for this
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
a list within one of the documents managed by an XCAP server.
6.7 Resource Interdependencies
An XCAP server supporting this application usage need only worry
about a single data interdependency - the "uri" attribute of the list
element.
If the "uri" attribute is absent in a document written to an XCAP
server, but the "subscribeable" flag is true, the XCAP server MUST
allocate a URI for this list. This allocated URI MUST be globally
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
attribute of the document with this URI.
A server MUST NOT delete the "uri" attribute, however, should a
client change the subscribeable flag to false after the server has
allocated a URI.
If the "uri" attribute is present in a document written to an XCAP
server, but the URI exists in another document managed by the server,
the document is considered invalid. A server MUST reject such a
request with a 409, and MAY include an XCAP error report in the body
indicating this condition. The server MAY suggest, using the "alt-ns"
element, alternate suggestions for a URI that is not currently
allocated.
6.8 Authorization Policies
This application usage does not modify the default XCAP authorization
policy, which is that only a user can read, write or modify their own
documents. A server can allow priveleged users to modify documents
that they don't own, but the establishment and indication of such
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.
7. 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 8. 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 8.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 [7]. according to the IANA procedures defined in [7].
Name of the AUID: resource-lists Name of the AUID: resource-lists
Description: A resource list application is any application that Description: A resource list application is any application that
needs access to a list of resources, identified by a URI, to which needs access to a list of resources, identified by a URI, to which
operations, such as subscriptions, can be applied. operations, such as subscriptions, can be applied.
12.2 application/resource-lists+xml MIME Type 8.2 application/resource-lists+xml MIME Type
MIME media type name: application MIME media type name: application
MIME subtype name: resource-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 7 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 [11] for been used to support subscriptions to lists of users [11] for
SIP-based presence [9]. SIP-based presence [9].
Additional Information: Additional Information:
skipping to change at page 17, line 15 skipping to change at page 14, line 15
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 8.3 URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:resource-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] RFC 3688 [6].
URI: The URI for this namespace is URI: The URI for this namespace is
urn:ietf:params:xml:ns:resource-lists. urn:ietf:params:xml:ns:resource-lists.
Registrant Contact: IETF, SIMPLE working group, (simple@ietf.org), Registrant Contact: IETF, SIMPLE working group, (simple@ietf.org),
Jonathan Rosenberg (jdrosen@jdrosen.net). Jonathan Rosenberg (jdrosen@jdrosen.net).
XML: XML:
BEGIN BEGIN
skipping to change at page 18, line 5 skipping to change at page 15, line 5
<title>Resource Lists Namespace</title> <title>Resource Lists Namespace</title>
</head> </head>
<body> <body>
<h1>Namespace for Resource Lists</h1> <h1>Namespace for Resource Lists</h1>
<h2>application/resource-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
8.4 Resource List Schema Registration
This section registers an XML schema per the procedures in [6].
URI: please assign.
Registrant Contact: IETF, SIMPLE working group, (simple@ietf.org),
Jonathan Rosenberg (jdrosen@jdrosen.net).
The XML for this schema can be found as the sole content of
Section 4.
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.
[2] Bray, T., Paoli, J., Sperberg-McQueen, C. and E. Maler, [2] Bray, T., Paoli, J., Sperberg-McQueen, C. and E. Maler,
"Extensible Markup Language (XML) 1.0 (Second Edition)", W3C REC "Extensible Markup Language (XML) 1.0 (Second Edition)", W3C
REC-xml-20001006, October 2000. FirstEdition REC-xml-20001006, October 2000.
[3] Moats, R., "URN Syntax", RFC 2141, May 1997. [3] Moats, R., "URN Syntax", RFC 2141, May 1997.
[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", BCP 81, RFC 3688, January
draft-mealling-iana-xmlns-registry-05 (work in progress), June 2004.
2003.
[7] Rosenberg, J., "The Extensible Markup Language (XML) [7] Rosenberg, J., "The Extensible Markup Language (XML)
Configuration Access Protocol (XCAP)", Configuration Access Protocol (XCAP)", draft-ietf-simple-xcap-01
draft-ietf-simple-xcap-00 (work in progress), June 2003. (work in progress), October 2003.
Informative References Informative References
[8] 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.
[9] 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.
skipping to change at page 19, line 35 skipping to change at page 17, line 35
[13] Rosenberg, J. and M. Isomaki, "Requirements for Manipulation of [13] Rosenberg, J. and M. Isomaki, "Requirements for Manipulation of
Data Elements in Session Initiation Protocol (SIP) for Instant Data Elements in Session Initiation Protocol (SIP) for Instant
Messaging and Presence Leveraging Extensions (SIMPLE) Systems", Messaging and Presence Leveraging Extensions (SIMPLE) Systems",
draft-ietf-simple-data-req-03 (work in progress), June 2003. 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 07054
US US
Phone: +1 973 952-5000 Phone: +1 973 952-5000
EMail: jdrosen@dynamicsoft.com EMail: jdrosen@dynamicsoft.com
URI: http://www.jdrosen.net URI: http://www.jdrosen.net
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to intellectual property or other rights that might be claimed to
skipping to change at page 20, line 29 skipping to change at page 18, line 29
be obtained from the IETF Secretariat. be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
skipping to change at page 21, line 7 skipping to change at page 19, line 7
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assignees. revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 

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