draft-ietf-xmpp-cpim-01.txt   draft-ietf-xmpp-cpim-02.txt 
Network Working Group P. Saint-Andre Network Working Group P. Saint-Andre
Internet-Draft Jabber Software Foundation Internet-Draft Jabber Software Foundation
Expires: December 28, 2003 T. Bamonti Expires: February 20, 2004 T. Bamonti
Jabber, Inc. Jabber, Inc.
June 29, 2003 August 22, 2003
XMPP CPIM Mapping XMPP CPIM Mapping
draft-ietf-xmpp-cpim-01 draft-ietf-xmpp-cpim-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 32 skipping to change at page 1, line 32
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 28, 2003. This Internet-Draft will expire on February 20, 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 mapping of the Extensible Messaging and This document describes a mapping of the Extensible Messaging and
Presence Protocol (XMPP) to the Common Presence and Instant Messaging Presence Protocol (XMPP) to the Common Presence and Instant Messaging
(CPIM) specifications. (CPIM) specifications.
skipping to change at page 2, line 33 skipping to change at page 2, line 33
3.2.7 CPIM DateTime Header . . . . . . . . . . . . . . . . . . . 9 3.2.7 CPIM DateTime Header . . . . . . . . . . . . . . . . . . . 9
3.2.8 Message Subject . . . . . . . . . . . . . . . . . . . . . 9 3.2.8 Message Subject . . . . . . . . . . . . . . . . . . . . . 9
3.2.9 CPIM Header Extensions . . . . . . . . . . . . . . . . . . 9 3.2.9 CPIM Header Extensions . . . . . . . . . . . . . . . . . . 9
3.2.10 CPIM Required Headers . . . . . . . . . . . . . . . . . . 10 3.2.10 CPIM Required Headers . . . . . . . . . . . . . . . . . . 10
3.2.11 MSGFMT MIME Content-type . . . . . . . . . . . . . . . . . 10 3.2.11 MSGFMT MIME Content-type . . . . . . . . . . . . . . . . . 10
3.2.12 MSGFMT MIME Content-ID . . . . . . . . . . . . . . . . . . 10 3.2.12 MSGFMT MIME Content-ID . . . . . . . . . . . . . . . . . . 10
3.2.13 Message Body . . . . . . . . . . . . . . . . . . . . . . . 10 3.2.13 Message Body . . . . . . . . . . . . . . . . . . . . . . . 10
3.2.14 XMPP Message Extensions . . . . . . . . . . . . . . . . . 11 3.2.14 XMPP Message Extensions . . . . . . . . . . . . . . . . . 11
3.3 Message Syntax Mapping from CPIM Specifications to XMPP . 11 3.3 Message Syntax Mapping from CPIM Specifications to XMPP . 11
3.3.1 From Address . . . . . . . . . . . . . . . . . . . . . . . 11 3.3.1 From Address . . . . . . . . . . . . . . . . . . . . . . . 11
3.3.2 To Address . . . . . . . . . . . . . . . . . . . . . . . . 12 3.3.2 To Address . . . . . . . . . . . . . . . . . . . . . . . . 11
3.3.3 CPIM Courtesy Copy . . . . . . . . . . . . . . . . . . . . 12 3.3.3 CPIM Courtesy Copy . . . . . . . . . . . . . . . . . . . . 12
3.3.4 XMPP Message Type . . . . . . . . . . . . . . . . . . . . 12 3.3.4 XMPP Message Type . . . . . . . . . . . . . . . . . . . . 12
3.3.5 CPIM DateTime Header . . . . . . . . . . . . . . . . . . . 12 3.3.5 CPIM DateTime Header . . . . . . . . . . . . . . . . . . . 12
3.3.6 Message Subject . . . . . . . . . . . . . . . . . . . . . 12 3.3.6 Message Subject . . . . . . . . . . . . . . . . . . . . . 12
3.3.7 CPIM Header Extensions . . . . . . . . . . . . . . . . . . 13 3.3.7 CPIM Header Extensions . . . . . . . . . . . . . . . . . . 13
3.3.8 CPIM Required Headers . . . . . . . . . . . . . . . . . . 13 3.3.8 CPIM Required Headers . . . . . . . . . . . . . . . . . . 13
3.3.9 MSGFMT MIME Content-type . . . . . . . . . . . . . . . . . 13 3.3.9 MSGFMT MIME Content-type . . . . . . . . . . . . . . . . . 13
3.3.10 MSGFMT MIME Content-ID . . . . . . . . . . . . . . . . . . 13 3.3.10 MSGFMT MIME Content-ID . . . . . . . . . . . . . . . . . . 13
3.3.11 Message Body . . . . . . . . . . . . . . . . . . . . . . . 14 3.3.11 Message Body . . . . . . . . . . . . . . . . . . . . . . . 14
4. Mapping of Presence . . . . . . . . . . . . . . . . . . . 15 4. Mapping of Presence . . . . . . . . . . . . . . . . . . . 15
skipping to change at page 3, line 11 skipping to change at page 3, line 11
4.2.5 CPIM DateTime Header . . . . . . . . . . . . . . . . . . . 17 4.2.5 CPIM DateTime Header . . . . . . . . . . . . . . . . . . . 17
4.2.6 CPIM Subject Header . . . . . . . . . . . . . . . . . . . 17 4.2.6 CPIM Subject Header . . . . . . . . . . . . . . . . . . . 17
4.2.7 CPIM Header Extensions . . . . . . . . . . . . . . . . . . 17 4.2.7 CPIM Header Extensions . . . . . . . . . . . . . . . . . . 17
4.2.8 CPIM Required Headers . . . . . . . . . . . . . . . . . . 18 4.2.8 CPIM Required Headers . . . . . . . . . . . . . . . . . . 18
4.2.9 PIDF MIME Content-type . . . . . . . . . . . . . . . . . . 18 4.2.9 PIDF MIME Content-type . . . . . . . . . . . . . . . . . . 18
4.2.10 PIDF MIME Content-ID . . . . . . . . . . . . . . . . . . . 18 4.2.10 PIDF MIME Content-ID . . . . . . . . . . . . . . . . . . . 18
4.2.11 XMPP Presence Type . . . . . . . . . . . . . . . . . . . . 18 4.2.11 XMPP Presence Type . . . . . . . . . . . . . . . . . . . . 18
4.2.12 XMPP Show Element . . . . . . . . . . . . . . . . . . . . 19 4.2.12 XMPP Show Element . . . . . . . . . . . . . . . . . . . . 19
4.2.13 XMPP Status Element . . . . . . . . . . . . . . . . . . . 20 4.2.13 XMPP Status Element . . . . . . . . . . . . . . . . . . . 20
4.2.14 PIDF Contact Element . . . . . . . . . . . . . . . . . . . 21 4.2.14 PIDF Contact Element . . . . . . . . . . . . . . . . . . . 21
4.2.15 Presence Priority . . . . . . . . . . . . . . . . . . . . 22 4.2.15 Presence Priority . . . . . . . . . . . . . . . . . . . . 21
4.2.16 PIDF Timestamp Element . . . . . . . . . . . . . . . . . . 22 4.2.16 PIDF Timestamp Element . . . . . . . . . . . . . . . . . . 22
4.2.17 XMPP Presence Extensions . . . . . . . . . . . . . . . . . 22 4.2.17 XMPP Presence Extensions . . . . . . . . . . . . . . . . . 22
4.3 Presence Syntax Mapping from CPIM Specifications to XMPP . 23 4.3 Presence Syntax Mapping from CPIM Specifications to XMPP . 22
4.3.1 From Address . . . . . . . . . . . . . . . . . . . . . . . 23 4.3.1 From Address . . . . . . . . . . . . . . . . . . . . . . . 22
4.3.2 To Address . . . . . . . . . . . . . . . . . . . . . . . . 23 4.3.2 To Address . . . . . . . . . . . . . . . . . . . . . . . . 23
4.3.3 CPIM Courtesy Copy . . . . . . . . . . . . . . . . . . . . 24 4.3.3 CPIM Courtesy Copy . . . . . . . . . . . . . . . . . . . . 23
4.3.4 CPIM DateTime Header . . . . . . . . . . . . . . . . . . . 24 4.3.4 CPIM DateTime Header . . . . . . . . . . . . . . . . . . . 23
4.3.5 CPIM Subject Header . . . . . . . . . . . . . . . . . . . 24 4.3.5 CPIM Subject Header . . . . . . . . . . . . . . . . . . . 24
4.3.6 CPIM Header Extensions . . . . . . . . . . . . . . . . . . 24 4.3.6 CPIM Header Extensions . . . . . . . . . . . . . . . . . . 24
4.3.7 CPIM Required Headers . . . . . . . . . . . . . . . . . . 24 4.3.7 CPIM Required Headers . . . . . . . . . . . . . . . . . . 24
4.3.8 PIDF MIME Content-type . . . . . . . . . . . . . . . . . . 25 4.3.8 PIDF MIME Content-type . . . . . . . . . . . . . . . . . . 24
4.3.9 PIDF MIME Content-ID . . . . . . . . . . . . . . . . . . . 25 4.3.9 PIDF MIME Content-ID . . . . . . . . . . . . . . . . . . . 24
4.3.10 PIDF Basic Presence Status . . . . . . . . . . . . . . . . 25 4.3.10 PIDF Basic Presence Status . . . . . . . . . . . . . . . . 25
4.3.11 PIDF Extended Status Information . . . . . . . . . . . . . 26 4.3.11 PIDF Extended Status Information . . . . . . . . . . . . . 26
4.3.12 PIDF Note Element . . . . . . . . . . . . . . . . . . . . 27 4.3.12 PIDF Note Element . . . . . . . . . . . . . . . . . . . . 26
4.3.13 PIDF Contact Element . . . . . . . . . . . . . . . . . . . 28 4.3.13 PIDF Contact Element . . . . . . . . . . . . . . . . . . . 27
4.3.14 Presence Priority . . . . . . . . . . . . . . . . . . . . 29 4.3.14 Presence Priority . . . . . . . . . . . . . . . . . . . . 28
4.3.15 PIDF Timestamp Element . . . . . . . . . . . . . . . . . . 29 4.3.15 PIDF Timestamp Element . . . . . . . . . . . . . . . . . . 28
5. XMPP-CPIM Gateway as Presence Service . . . . . . . . . . 30 5. XMPP-CPIM Gateway as Presence Service . . . . . . . . . . 29
5.1 Requesting a Subscription . . . . . . . . . . . . . . . . 30 5.1 Requesting a Subscription . . . . . . . . . . . . . . . . 29
5.2 Receiving a Subscription Request . . . . . . . . . . . . . 31 5.2 Receiving a Subscription Request . . . . . . . . . . . . . 30
5.3 Subscription Durations . . . . . . . . . . . . . . . . . . 32 5.3 Subscription Durations . . . . . . . . . . . . . . . . . . 31
5.4 The Notify Operation . . . . . . . . . . . . . . . . . . . 32 5.4 The Notify Operation . . . . . . . . . . . . . . . . . . . 31
5.4.1 Multiple Resources . . . . . . . . . . . . . . . . . . . . 32
5.4.2 Zero Resources . . . . . . . . . . . . . . . . . . . . . . 32
5.5 Unsubscribing . . . . . . . . . . . . . . . . . . . . . . 33 5.5 Unsubscribing . . . . . . . . . . . . . . . . . . . . . . 33
5.6 Cancelling a Subscription . . . . . . . . . . . . . . . . 33 5.6 Cancelling a Subscription . . . . . . . . . . . . . . . . 33
6. Mapping of Character Encodings . . . . . . . . . . . . . . 35 6. Mapping of Character Encodings . . . . . . . . . . . . . . 35
7. Security Considerations . . . . . . . . . . . . . . . . . 36 7. Security Considerations . . . . . . . . . . . . . . . . . 36
Normative References . . . . . . . . . . . . . . . . . . . 37 Normative References . . . . . . . . . . . . . . . . . . . 37
Informative References . . . . . . . . . . . . . . . . . . 38 Informative References . . . . . . . . . . . . . . . . . . 38
Authors' Addresses . . . . . . . . . . . . . . . . . . . . 38 Authors' Addresses . . . . . . . . . . . . . . . . . . . . 38
A. Revision History . . . . . . . . . . . . . . . . . . . . . 39 A. Revision History . . . . . . . . . . . . . . . . . . . . . 39
A.1 Changes from draft-ietf-xmpp-cpim-00 . . . . . . . . . . . 39 A.1 Changes from draft-ietf-xmpp-cpim-01 . . . . . . . . . . . 39
A.2 Changes from draft-ietf-xmpp-cpim-00 . . . . . . . . . . . 39
Intellectual Property and Copyright Statements . . . . . . 40 Intellectual Property and Copyright Statements . . . . . . 40
1. Introduction 1. Introduction
1.1 Overview 1.1 Overview
The Instant Messaging and Presence (IMPP) Working Group has defined The Instant Messaging and Presence (IMPP) Working Group has defined
an abstract framework for interoperability among instant messaging an abstract framework for interoperability among instant messaging
(IM) and presence systems that are compliant with RFC 2779 [1]. This (IM) and presence systems that are compliant with RFC 2779 [1]. This
framework is commonly called Common Presence and Instant Messaging or framework is commonly called Common Presence and Instant Messaging or
skipping to change at page 7, line 18 skipping to change at page 7, line 18
between an XMPP service and a non-XMPP service using a "Message/CPIM" between an XMPP service and a non-XMPP service using a "Message/CPIM"
object as the bearer of encapsulated text content in order to comply object as the bearer of encapsulated text content in order to comply
with the instant messaging semantics defined by CPIM [2]. with the instant messaging semantics defined by CPIM [2].
3.1 Identification of Instant Inboxes 3.1 Identification of Instant Inboxes
There is a one-to-one relationship between an XMPP entity and a CPIM There is a one-to-one relationship between an XMPP entity and a CPIM
instant inbox when the JID of the entity contains only a node instant inbox when the JID of the entity contains only a node
identifier and domain identifier, and the node identifier uniquely identifier and domain identifier, and the node identifier uniquely
corresponds to an IM user who possesses an account on an XMPP server. corresponds to an IM user who possesses an account on an XMPP server.
However, the syntax for addressing an instant inbox is specified as
including the 'im:' URI scheme, whereas an XMPP address does not
include that scheme, so any mapping between an instant inbox address
and a JID must add or remove the 'im:' URI scheme as appropriate.
3.2 Message Syntax Mapping from XMPP to CPIM Specifications 3.2 Message Syntax Mapping from XMPP to CPIM Specifications
This section defines the mapping of syntax primitives from XMPP This section defines the mapping of syntax primitives from XMPP
message stanzas to "Message/CPIM" objects with encapsulated text message stanzas to "Message/CPIM" objects with encapsulated text
content. content.
3.2.1 From Address 3.2.1 From Address
The 'from' attribute of an XMPP message stanza maps to the 'From' The 'from' attribute of an XMPP message stanza maps to the 'From'
skipping to change at page 15, line 17 skipping to change at page 15, line 17
This section describes how a gateway SHOULD map presence information This section describes how a gateway SHOULD map presence information
between an XMPP service and a non-XMPP service using a "Message/CPIM" between an XMPP service and a non-XMPP service using a "Message/CPIM"
object as the bearer of an encapsulated PIDF [5] object in order to object as the bearer of an encapsulated PIDF [5] object in order to
comply with the presence semantics defined by CPP [3]. comply with the presence semantics defined by CPP [3].
4.1 Identification of Presentities 4.1 Identification of Presentities
There is a one-to-one relationship between an XMPP entity and a CPP There is a one-to-one relationship between an XMPP entity and a CPP
presentity when the JID of the entity contains only a node identifier presentity when the JID of the entity contains only a node identifier
and domain identifier, and the node identifier uniquely corresponds and domain identifier, and the node identifier uniquely corresponds
to an IM user who possesses an account on an XMPP server. to an IM user who possesses an account on an XMPP server. However,
the syntax of presentities is specified as including the 'pres:' URI
scheme, whereas XMPP addresses do not include that scheme, so any
mapping between presentities and JIDs must add or remove the 'pres:'
URI scheme as appropriate.
4.2 Presence Syntax Mapping from XMPP to CPIM Specifications 4.2 Presence Syntax Mapping from XMPP to CPIM Specifications
This section defines the mapping of syntax primitives from XMPP This section defines the mapping of syntax primitives from XMPP
presence stanzas to "Message/CPIM" objects with encapsulated presence stanzas to "Message/CPIM" objects with encapsulated
"application/pidf+xml" objects. "application/pidf+xml" objects.
4.2.1 From Address 4.2.1 From Address
The 'from' attribute of an XMPP presence stanza maps to the 'From' The 'from' attribute of an XMPP presence stanza maps to the 'From'
skipping to change at page 28, line 27 skipping to change at page 27, line 16
<note>Wooing Juliet</note> <note>Wooing Juliet</note>
</tuple> </tuple>
</presence> </presence>
XMPP <status/> element XMPP <status/> element
<presence from='romeo@montague.net/orchard'> <presence from='romeo@montague.net/orchard'>
<show>dnd</show> <show>dnd</show>
<status>Wooing Juliet</status> <status>Wooing Juliet</status>
</presence> </presence>
A PIDF document with zero tuples MAY contain one or more <note/>
elements as direct children of the PIDF <presence/> element. There is
no mapping of such a PIDF document to an XMPP presence stanza; an
entity on the non-XMPP side of an XMPP-CPIM gateway SHOULD NOT send
such a PIDF document to an XMPP recipient if possible, and an
XMPP-CPIM gateway MUST NOT map such a PIDF document to an XMPP
presence stanza (see Zero Resources (Section 5.4.2)).
4.3.13 PIDF Contact Element 4.3.13 PIDF Contact Element
The core XMPP specification does not include syntax for specifying The core XMPP specification does not include syntax for specifying
the URL of a contact address, since the contact address is implicit the URL of a contact address, since the contact address is implicit
in the 'from' attribute of the XMPP presence stanza. Therefore, if an in the 'from' attribute of the XMPP presence stanza. Therefore, if an
XMPP-CPIM gateway receives a "Message/CPIM" object with encapsulated XMPP-CPIM gateway receives a "Message/CPIM" object with encapsulated
PIDF object that contains a <contact/> element, it SHOULD NOT pass PIDF object that contains a <contact/> element, it SHOULD NOT pass
the CDATA of the <contact/> element on to the XMPP recipient. the CDATA of the <contact/> element on to the XMPP recipient.
However, the gateway MAY map the 'priority' element as specified in However, the gateway MAY map the 'priority' element as specified in
the following section. the following section.
skipping to change at page 33, line 5 skipping to change at page 32, line 5
5.4 The Notify Operation 5.4 The Notify Operation
An XMPP-CPIM gateway invokes the CPP "notify operation" whenever the An XMPP-CPIM gateway invokes the CPP "notify operation" whenever the
presence information associated with an XMPP entity or CPP presentity presence information associated with an XMPP entity or CPP presentity
changes and there are subscribers to that information on the other changes and there are subscribers to that information on the other
side of the gateway. The syntax mapping for presence information side of the gateway. The syntax mapping for presence information
related to a notify operation is defined under Mapping for Presence related to a notify operation is defined under Mapping for Presence
(Section 4). (Section 4).
5.4.1 Multiple Resources
Semantically, PIDF contains the notion of multiple presence "tuples".
Normally, a PIDF document will contain at least one tuple but MAY
contain more than one tuple (or zero tuples, for which see next
section). In the terminology of XMPP, each tuple would map to
presence information for a separate resource. However, XMPP does not
include the ability to send presence information about more than one
resource at a time, since the resource that generates the presence
information is contained in the 'from' address of a presence stanza.
Therefore, an XMPP-CPIM gateway that acts as a presence service
SHOULD split a PIDF document that contains multiple tuples into
multiple XMPP presence stanzas, and SHOULD generate only one PIDF
document (with multiple tuples) if an XMPP user currently has
multiple connected resources.
In the interest of not multiplying XMPP stanzas beyond necessity, an
XMPP-CPIM gateway SHOULD generate an XMPP presence stanza only if the
presence information contained in a PIDF tuple communicates a change
in the availability status of the device or application associated
with that tuple ID.
In the interest of complying with the PIDF recommendation to provide
information about multiple "resources" in multiple tuples rather than
in multiple PIDF documents, an XMPP-CPIM gateway SHOULD include
information about all of an XMPP user's resources in one PIDF
document (with one tuple for each resource), even if the availability
status of only one resource has changed.
5.4.2 Zero Resources
A PIDF document may contain zero tuples. For example:
PIDF Document with Zero Tuples
<presence entity='pres:juliet@capulet.com'
xmlns='urn:ietf:params:xml:ns:pidf'/>
Because (1) the 'entity' attribute of a PIDF <presence/> element maps
to the <user@host> portion of an XMPP JID and (2) the 'id' attribute
of a PIDF <tuple/> element maps to the resource identifier portion of
an XMPP JID, a PIDF document that contains zero tuples would provide
presence information about a <user@host> rather than a <user@host/
resource> when mapped to XMPP. However, the notion of presence about
a user rather than a user's resources is meaningless in the XMPP
context. Therefore, an XMPP-CPIM gateway MUST NOT map a PIDF document
with zero tuples into an XMPP presence stanza, and MUST NOT generate
such a PIDF document when receiving a presence stanza from an XMPP
entity (i.e., all PIDF documents generated by the gateway MUST
contain at least one <tuple/> element).
5.5 Unsubscribing 5.5 Unsubscribing
If an XMPP entity wants to unsubscribe from the presence of a If an XMPP entity wants to unsubscribe from the presence of a
non-XMPP presentity through an XMPP-CPIM gateway, it MUST send a non-XMPP presentity through an XMPP-CPIM gateway, it MUST send a
presence stanza of type "unsubscribe" to the target presentity. The presence stanza of type "unsubscribe" to the target presentity. The
syntax mapping is as follows: syntax mapping is as follows:
o The XMPP 'from' attribute (node@domain) MUST be mapped to the CPP o The XMPP 'from' attribute (node@domain) MUST be mapped to the CPP
"watcher parameter" field (pres:node@domain). The XMPP-CPIM "watcher parameter" field (pres:node@domain). The XMPP-CPIM
gateway MUST append the "pres:" Presence URI scheme to the front gateway MUST append the "pres:" Presence URI scheme to the front
skipping to change at page 37, line 26 skipping to change at page 37, line 26
[4] Atkins, D. and G. Klyne, "Common Presence and Instant Messaging [4] Atkins, D. and G. Klyne, "Common Presence and Instant Messaging
Message Format", draft-ietf-impp-cpim-msgfmt-08 (work in Message Format", draft-ietf-impp-cpim-msgfmt-08 (work in
progress), January 2003. progress), January 2003.
[5] Fujimoto, S., Sugano, H., Klyne, G., Bateman, A., Carr, W. and [5] Fujimoto, S., Sugano, H., Klyne, G., Bateman, A., Carr, W. and
J. Peterson, "CPIM Presence Information Data Format", J. Peterson, "CPIM Presence Information Data Format",
draft-ietf-impp-cpim-pidf-08 (work in progress), May 2003. draft-ietf-impp-cpim-pidf-08 (work in progress), May 2003.
[6] Saint-Andre, P. and J. Miller, "XMPP Core", [6] Saint-Andre, P. and J. Miller, "XMPP Core",
draft-ietf-xmpp-core-15 (work in progress), June 2003. draft-ietf-xmpp-core-17 (work in progress), August 2003.
[7] Saint-Andre, P. and J. Miller, "XMPP Instant Messaging", [7] Saint-Andre, P. and J. Miller, "XMPP Instant Messaging",
draft-ietf-xmpp-im-14 (work in progress), June 2003. draft-ietf-xmpp-im-16 (work in progress), August 2003.
[8] Saint-Andre, P., "End-to-End Object Encryption in XMPP", [8] Saint-Andre, P., "End-to-End Object Encryption in XMPP",
draft-ietf-xmpp-e2e-04 (work in progress), June 2003. draft-ietf-xmpp-e2e-04 (work in progress), June 2003.
[9] Day, M., Rosenberg, J. and H. Sugano, "A Model for Presence and [9] Day, M., Rosenberg, J. and H. Sugano, "A Model for Presence and
Instant Messaging", RFC 2778, February 2000, <http:// Instant Messaging", RFC 2778, February 2000, <http://
www.ietf.org/rfc/rfc2778.txt>. www.ietf.org/rfc/rfc2778.txt>.
[10] Bradner, S., "Key words for use in RFCs to Indicate Requirement [10] 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 39, line 10 skipping to change at page 39, line 10
Tony Bamonti Tony Bamonti
Jabber, Inc. Jabber, Inc.
EMail: tbamonti@jabber.com EMail: tbamonti@jabber.com
Appendix A. Revision History Appendix A. Revision History
Note to RFC Editor: please remove this entire appendix, and the Note to RFC Editor: please remove this entire appendix, and the
corresponding entries in the table of contents, prior to publication. corresponding entries in the table of contents, prior to publication.
A.1 Changes from draft-ietf-xmpp-cpim-00 A.1 Changes from draft-ietf-xmpp-cpim-01
o Added subsection about handling presence notifications for
multiple XMPP resources and multiple PIDF tuples.
o Added subsection about PIDF documents that contain zero tuples.
o Further specified mapping between XMPP JIDs and CPIM instant
inboxes and presentities.
A.2 Changes from draft-ietf-xmpp-cpim-00
o Updated references. o Updated references.
o Made several small editorial changes. o Made several small editorial changes.
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
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
skipping to change at page 41, line 7 skipping to change at page 41, 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. 19 change blocks. 
27 lines changed or deleted 107 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/