[Members] [Fwd: Re: [xmppwg] New charter please]

Peter Saint-Andre stpeter at stpeter.im
Tue Mar 31 11:20:14 CDT 2009

We had a successful XMPP BOF at IETF 74 last week. It would be helpful
for XSF members to review the proposed charter and post to the
xmppwg at xmpp.org list with comments or even just a simple "+1" if you
think it looks sane. The IETF loves the fact that we have an active
developer community, so bringing some of that energy into the XMPP WG
would be a good thing.



-------- Original Message --------
Subject: Re: [xmppwg] New charter please
Date: Tue, 31 Mar 2009 10:17:24 -0600
From: Peter Saint-Andre <stpeter at stpeter.im>
To: XMPP Working Group <xmppwg at xmpp.org>
References: <C5F79B71.74BB%joe.hildebrand at webex.com>

On 3/31/09 10:05 AM, Joe Hildebrand wrote:
> On 3/31/09 9:58 AM, "Jack Moffitt" <jack at chesspark.com> wrote:
>> Yes, I think this latest charter draft is looking quite good and well focused.
> +1.  I like the new I18n language.

So that we have everything in one place, I'll post it again...


Extensible Messaging and Presence Protocol (xmpp2)


Area Director(s):

Area Advisor:

Mailing Lists:
General Discussion:xmppwg at xmpp.org
To Subscribe: xmppwg-request at xmpp.org
In Body: subscribe
Archive: http://mail.jabber.org/pipermail/xmppwg/

Description of Working Group:

The Extensible Messaging and Presence Protocol (XMPP) is an IETF
technology for the near-real-time exchange of messages and presence
notifications, where data is exchanged over Extensible Markup Language
(XML) streams. XMPP was originally formalized by the XMPP Working Group
in 2002-2004, resulting in publication of RFCs 3920-3923.

Implementation and deployment experience since that time has resulted
in errata, clarifications, and suggestions for improvement to the core
XMPP specifications (RFCs 3920 and 3921). Some technologies on which
XMPP depends (e.g., Transport Layer Security and the Simple
Authentication and Security Layer) have undergone modifications of their
own, which XMPP needs to track. Finally, the group needs to define a
sustainable solution to internationalization of XMPP addresses, since
the approach taken in RFC 3920 (based on stringprep profiles) is limited
to Unicode 3.2 characters. Both draft-saintandre-rfc3920bis-* and
draft-saintandre-rfc3921bis-* reflect community consensus achieved so
far regarding these modifications, but the group needs to complete this
work, especially with regard to internationalization. Because of the
scope of changes involved, it is envisioned that these specifications
will be cycled at Proposed Standard.

Although RFC 3923 defines an end-to-end signing and encryption
technology for use by XMPP systems, to date it has not been implemented.
A goal of the group is to develop an implementable method for end-to-end
encryption, preferably based on well known and widely deployed security

XMPP uses TLS for encryption and the Simple Authentication and Security
Layer (SASL) for authentication. In the case of a server-to-server
stream, XMPP is deployed using TLS and the SASL EXTERNAL mechanism,
where each peer presents an X.509 certificate. This model introduces
scaling challenges in multi-domain deployments because RFC 3920 requires
that a stream cannot be reused for more than one domain, thus
necessitating multiple TCP connections. The group will work to overcome
these challenges by defining an optional mechanism for using a single
connection with multiple identities. It is anticipated that most of the
work will consist of defining and providing requirements to the TLS and
SASL working groups.

Many of the core and extended features of XMPP have also been
implemented in technologies based on the Session Initiation Protocol
(SIP). To ensure interworking between XMPP systems and SIP systems, a
number of Internet-Drafts (draft-saintandre-sip-xmpp-*) have been
produced. The group will define a framework within which this work could
be completed.

In completing its work, the group will strive to retain backwards
compatibility with RFCs 3920 and 3921. However, changes that are not
backwards compatible might be accepted if the group determines that the
changes are required to meet the group's technical objectives and the
group clearly documents the reasons for making them.

Goals and Milestones:

- Deliver rfc3920bis and rfc3921bis to the IESG.

- Decide upon a direction for end-to-end encryption.

- Decide upon a direction for server-to-server connection reuse.

- Define a framework for SIP-XMPP interworking.

- Define a solution for end-to-end encryption.

- Define a solution for server-to-server connection reuse.


Peter Saint-Andre

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6751 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mail.jabber.org/pipermail/members/attachments/20090331/c769de86/attachment.bin 

More information about the Members mailing list