2.1.12 Extensible Messaging and Presence Protocol (xmpp)
Last Modified: 2003-06-16
Pete Resnick <firstname.lastname@example.org>
Lisa Dusseault <email@example.com>
Applications Area Director(s):
Ned Freed <firstname.lastname@example.org>
Ted Hardie <email@example.com>
Applications Area Advisor:
Ted Hardie <firstname.lastname@example.org>
General Discussion: email@example.com
To Subscribe: firstname.lastname@example.org
In Body: subscribe
Description of Working Group:
XMPP is an open, XML-based protocol for near real-time extensible
messaging and presence. It is the core protocol of the Jabber Instant
Messaging and Presence technology which is currently deployed on
thousands of servers across the Internet and is used by millions of
people worldwide. The XMPP working group shall adapt the XMPP for use
as an IETF Instant Messaging and Presence technology.
The working group will use XMPP (as described in draft-miller-xmpp-*)
as the basis of its work. The final specifications will be consistent
as much as practical with both the requirements given in RFC2779 and
the interoperability details in the final version of the CPIM
specification (draft-ietf-impp-cpim). Note: If a requirement of
RFC2779 or the final CPIM specification cannot be met, the working
group will document why this requirement cannot be met.
A major goal of the working group will be to extend the current XMPP
protocols to provide finished support for RFC 2779-compliant security
mechanisms, including authentication, privacy, access control and
end-to-end as well as hop-by-hop message security.
Mandatory-to-implement security mechanisms will be specified as
needed in order to guarantee secure protocol interoperability.
The working group shall also add support for internationalization and
localization to XMPP.
Instant messaging differs from email primarily by requiring
relatively short delivery latency guarantees and, typically, less
robust transport service. In addition, instant messaging includes the
notion of presence information so authorized users can determine if
their correspondents are available.
BCP 41 will be the basis for working group consideration of the
transport implications of the XMPP design with respect to network
Although not encouraged, non-backwards-compatible changes to the
basis specifications will be acceptable if the working group
determines that the changes are required to meet the group's
technical objectives and the group clearly documents the reasons for
There are facilities, such as chat rooms, shared white-boards and
similar services that are not currently discussed in RFC2778 and
RFC2779. When designing security mechanisms, the working group will
keep in mind that XMPP may be extended or adapted to facilitate these
additional services, so that design decisions can be made that will
not preclude providing these services in the future.
Goals and Milestones:
|Done|| ||Prepare revised specifications reflecting issues and
solutions identified by the working group |
|Done|| ||Meet at the 55th IETF to discuss current drafts |
|Done|| ||Prepare final core protocol draft ready for working group
last call |
|Done|| ||Prepare final instant messaging draft ready for working
group last call |
|Feb 03|| ||Prepare final CPIM compliance draft ready for working group
last call |
|Mar 03|| ||Submit revised specifications to the IESG for consideration
as standards-track publications |
No Request For Comments
Current Meeting Report
MUSTxmpp minutes from ietf57
Date: Monday, July 14th
Chairs: Lisa Dusseault/Pete Resnick
Scribe: Marshall Rose
1. Dusseault - Agenda
2. Saint-Andre - End-to-End encryption
Uses S/MIME with 3 containers: message/cpim,
application/pidf+xml, and application/xmpp+xml.
Enrollment issues are out-of-scope (cf., the pkix working group).
JID included in subjectAltName extension (otherName/xmpp) to allow the
same cert to be used for email/xmpp.
- Saint-Andre to ask Ned Freed to review
- Saint-Andre to include subscribe state chart in next revision of the im
3. Saint-Andre - CPIM mapping
A detailed mapping between the two.
Issue: which entities (clients, servers) are required to implement
Ted Hardie notes that the core document is independent of the im
document, even though im is the prototypical example used throughout the
core document. Perhaps an extensibility document for non-im
applications making use of the xmpp core is needed.
- all: please review mapping document, only a few people have read it.
4. Resnick - Moving Forward
Ted Hardie notes that the IESG will likely resolve the status of the
latest impp output by Thursday, August 7th.
WG last call for the 4 core documents ends in two weeks; any
following comments will have to be submitted during IESG last call.
XMPP WG Discussion