| TOC |
|
This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 20, 2004.
Copyright (C) The Internet Society (2003). All Rights Reserved.
This memo defines a method for end-to-end object signing and encryption in the Extensible Messaging and Presence Protocol (XMPP).
| TOC |
| TOC |
This memo define a method for end-to-end signing and encryption in the Extensible Messaging and Presence Protocol (XMPP). (For information about XMPP, see [XMPP-CORE] and [XMPP-IM].) The method defined herein enables a sender to encrypt and/or sign an instant message sent to a specific recipient, encrypt and/or sign presence information that is directed to a specific user, and sign presence information that is broadcasted to a specific user. This memo thereby helps the XMPP specifications meet the requirements defined in [IMP-REQS].
This document inherits terminology defined in [SMIME], [IMP-MODEL], [CMS], and [XMPP-CORE].
The capitalized key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [TERMS].
The authors welcome discussion and comments related to the topics presented in this document. The preferred forum is the <xmppwg@jabber.org> mailing list, for which archives and subscription information are available at <http://www.jabber.org/cgi-bin/mailman/listinfo/xmppwg/>.
This document is in full compliance with all provisions of Section 10 of RFC 2026. Parts of this specification use the term "jabber" for identifying namespaces and other protocol syntax. Jabber[tm] is a registered trademark of Jabber, Inc. Jabber, Inc. grants permission to the IETF for use of the Jabber trademark in association with this specification and its successors, if any.
| TOC |
For the purposes of this memo, we stipulate the following requirements:
| TOC |
In order to encrypt a message, a sending entity MUST use the following procedure:
Example 1: Sender generates "Message/CPIM" object:
Content-type: Message/CPIM
From: Juliet Capulet <im:juliet@example.com>
To: Romeo Montague <im:romeo@example.net>
DateTime: 2003-05-14T11:45:36Z
Subject: Imploring
Content-type: text/plain; charset=utf-8
Content-ID: <1234567890@example.com>
Wherefore art thou, Romeo?
Example 2: Sender generates signed message (the 'from' address on the XMPP message stanza is stamped by sender's server):
<message to='romeo@example.net/orchard' type='chat'>
<e2e xmlns='urn:ietf:params:xml:ns:xmpp-e2e'>
<![CDATA[
Content-Type: multipart/signed; boundary=next;
micalg=sha1;
protocol=application/pkcs7-signature
--next
Content-type: Message/CPIM
From: Juliet Capulet <im:juliet@example.com>
To: Romeo Montague <im:romeo@example.net>
DateTime: 2003-05-14T23:45:36Z
Subject: Imploring
Content-type: text/plain; charset=utf-8
Content-ID: <1234567890@example.com>
Wherefore art thou, Romeo?
--next
Content-Type: application/pkcs7-signature
[signed body part]
--next--
]]>
</e2e>
</message>
| TOC |
In order to encrypt presence information, a sending entity MUST use the following procedure:
Example 3: Sender generates "application/pidf+xml" object:
<?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:im="urn:ietf:params:xml:ns:pidf:im"
entity="pres:juliet@example.com">
<tuple id="h40zny"
<status>
<basic>open</basic>
<im:im>away</im:im>
</status>
<note xml:lang="en">retired to the chamber</note>
<timestamp>2003-05-14T23:53:11Z</timestamp>
</tuple>
</presence>
Example 4: Sender generates signed presence (the 'from' address on the XMPP presence stanza is stamped by sender's server):
<presence to='romeo@example.net/orchard'>
<e2e xmlns='urn:ietf:params:xml:ns:xmpp-e2e'>
<![CDATA[
Content-Type: multipart/signed; boundary=next;
micalg=sha1;
protocol=application/pkcs7-signature
--next
Content-type: application/pidf+xml
Content-ID: <2345678901@example.com>
<xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:im="urn:ietf:params:xml:ns:pidf:im"
entity="pres:juliet@example.com">
<tuple id="hr0zny">
<status>
<basic>open</basic>
<im:im>away</im:im>
</status>
<note xml:lang="en">retired to the chamber</note>
<timestamp>2003-05-14T23:53:11Z</timestamp>
</tuple>
</presence>
--next
Content-Type: application/pkcs7-signature
[signed body part]
--next--
]]>
</e2e>
</presence>
| TOC |
The foregoing sections of this memo describe how to secure "least common denominator" messaging and presence data of the kind that can be directly translated into the MSGFMT or PIDF formats. However, XMPP possesses a third base-level stanza type (<iq/>) in addition to <message/> and <presence/>, as well as the ability to include extended XML data within arbitrary child elements of the three core stanza types. Therefore it would be desirable to secure such data if possible.
Because [MSGFMT] specifies the ability to encapsulate any MIME type, the approach taken in this memo is to include arbitrary XMPP data in a new MIME type, "application/xmpp+xml". The root element for this MIME type is <xmpp/>, and the root element MUST contain one and only one child element, corresponding to one of the XMPP stanza types (i.e., message, presence, or iq) if the default namespace is 'jabber:client' or 'jabber:server' as defined in [XMPP-CORE].
The following examples illustrate the structure of the "application/xmpp+xml" MIME type.
Example 5: Message stanza with extended data contained in "application/xmpp+xml" MIME type:
<?xml version='1.0' encoding='UTF-8'?>
<xmpp xmlns='jabber:client'>
<message
from='iago@example.com/pda'
to='emilia@example.com/cell'>
<body>
I told him what I thought, and told no more
Than what he found himself was apt and true.
</body>
<evil xmlns='http://jabber.org/protocol/evil'/>
</message>
</xmpp>
Example 6: Presence stanza with extended data contained in "application/xmpp+xml" MIME type:
<?xml version='1.0' encoding='UTF-8'?>
<xmpp xmlns='jabber:client'>
<presence from='iago@example.com/pda'>
<show>dnd</show>
<status>Fomenting dissension</status>
<evil xmlns='http://jabber.org/protocol/evil'/>
</presence>
</xmpp>
Example 7: IQ stanza with extended data contained in "application/xmpp+xml" MIME type:
<?xml version='1.0' encoding='UTF-8'?>
<xmpp xmlns='jabber:client'>
<iq type='result'
from='iago@example.com/pda'
to='emilia@example.com/cell'
id='evil1'>
<query xmlns='jabber:iq:version'>
<name>Stabber</name>
<version>666</version>
<os>FiendOS</os>
</query>
<evil xmlns='http://jabber.org/protocol/evil'/>
</iq>
</xmpp>
| TOC |
S/MIME v3 does not specify how to obtain a certificate from a certificate authority, but instead mandates that every sending agent must already have a certificate. The PKIX Working Group has, at the time of this writing, produced two separate standards for certificate enrollment: [CMP] and [CMC]. Which method to use for certificate enrollment is outside the scope of this memo.
A receiving agent MUST provide some certificate retrieval mechanism in order to gain access to certificates for recipients of digital envelopes. This memo does not cover how S/MIME agents handle certificates, only what they do after a certificate has been validated or rejected. S/MIME certification issues are covered in [CERT].
At a minimum, for initial S/MIME deployment, a user agent could automatically generate a message to an intended recipient requesting that recipient's certificate in a signed return message. Receiving and sending agents SHOULD also provide a mechanism to allow a user to "store and protect" certificates for correspondents in such a way so as to guarantee their later retrieval.
End-entity certificates used in the context of this memo SHOULD a valid instant messaging address. The address SHOULD be one of the following:
The value of the JID contained in the XMPP 'from' attribute SHOULD match the JID provided in the signer's certificate, with the exception that the resource identifier portion of the JID contained in the 'from' attribute MAY be ignored for matching purposes.
Receiving agents MUST recognize XMPP addresses (JIDs) in the subjectAltName field.
Receiving agents SHOULD check that sending JID matches a JID provided in the signer's certificate, with the exception that the resource identifier portion of the JID contained in the 'from' attribute MAY be ignored for matching purposes. A receiving agent SHOULD provide some explicit alternate processing of the message if this comparison fails, which may be to display a message that shows the recipient the addresses in the certificate or other certificate details.
The subject alternative name extension is used in S/MIME as the preferred means to convey the JID that corresponds to the entity for this certificate. Any JIDs present SHOULD be encoded using the otherName CHOICE of the subjectAltName type, where the type-id is "xmpp" and the value is the bare JID of the entity.
According to various S/MIME specifications for message wrapping, [CMS] objects MAY optionally be wrapped in MIME to dynamically support 7-bit transport. Because it is expected that XMPP will not be used to interface with older 7-bit systems, this outer wrapping is NOT REQUIRED for XMPP transport, and generally SHOULD NOT be applied in a homogeneous XMPP environment or in an environment that supports XMPP-CPIM gateways.
Sending agents SHOULD attach a signature to each encrypted message or presence stanza, but are NOT REQUIRED to do so.
Sending agents are NOT REQUIRED to include the sender's certificate along with each encrypted message or presence stanza.
At a minimum, all implementations MUST support the following CMS algorithms as defined in [CMS-ALG]:
- for digest:
- DIGEST-MD5
- for signing:
- RSA
- for content encryption:
- Triple-DES CBC
| TOC |
A common method for achieving interoperability between two disparate services is through the use of a "gateway" that interprets the protocols of each service and translates them into the protocols of the other. The CPIM specifications (specifically [MSGFMT] and [PIDF] define the common profiles to be used for interoperability between instant messaging and presence services that comply with [IMP-REQS]. In the case of communications between an XMPP service and a non-XMPP service, we can visualize this relationship as follows:
+-------------+ +-------------+ +------------+
| | | | | |
| XMPP | | XMPP-CPIM | | Non-XMPP |
| Service | <----> | Gateway | <----> | Service |
| | | | | |
+-------------+ +-------------+ +------------+
The end-to-end encryption method defined herein enables the exchange of encrypted and/or signed instant messages and presence through an XMPP-CPIM gateway. In particular:
The wrapped S/MIME object MUST be immutable and MUST NOT be modified by an XMPP-CPIM gateway.
| TOC |
This entire memo discusses security. Detailed security considerations for instant messaging and presence protocols are given in [IMP-REQS] (Sections 5.1 through 5.4), and for XMPP in particular are given in [XMPP-CORE] (Sections 12.1 through 12.6).
The end-to-end security method defined here MAY result in exchanging secured instant messages and presence information through a gateway that implements the CPIM specifications. Such a gateway MUST be compliant with the minimum security requirements of the instant messaging and presence protocols with which it interfaces.
| TOC |
To: ietf-types@iana.org
Subject: Registration of MIME media type application/xmpp+xml
- MIME media type name: application
- MIME subtype name: xmpp+xml
- Required parameters: (none)
- Optional parameters: charset
- Indicates the character encoding of the enclosed XML; the default encoding is UTF-8.
- Encoding considerations:
- Contains XML, which can employ 8-bit characters, depending on the character encoding used.
- Security considerations:
- Contains a message, presence information, or IQ (request-response) data in XMPP, which may be considered private. Appropriate precautions should be adopted to limit disclosure of this information.
- Interoperability considerations: (none)
- Specification:
- XXXX
- Applications which use this media type:
- XMPP-compliant instant messaging and presence systems.
- Additional information: (none)
- Person and email address to contact for further information:
- IETF, XMPP Working Group, <xmppwg@jabber.org>
- Intended usage:
- COMMON
- Author/Change controller:
- IETF, XMPP Working Group
A URN sub-namespace for signed and encrypted content in the Extensible Messaging and Presence Protocol (XMPP) is defined as follows. (This namespace name adheres to the format defined in [XML-REG].)
- URI:
- urn:ietf:params:xml:ns:xmpp-e2e
- Specification:
- XXXX
- Description:
- This is the XML namespace name for signed and encrypted content in the Extensible Messaging and Presence Protocol as defined by XXXX.
- Registrant Contact:
- IETF, XMPP Working Group, <xmppwg@jabber.org>
| TOC |
| TOC |
| [XML-REG] | Mealling, M., "The IANA XML Registry", draft-mealling-iana-xmlns-registry-05 (work in progress), June 2003. |
| [XMPP-CPIM] | Saint-Andre, P., "Mapping the Extensible Messaging and Presence Protocol (XMPP) to Common Presence and Instant Messaging (CPIM)", draft-ietf-xmpp-cpim-03 (work in progress), November 2003. |
| TOC |
| Peter Saint-Andre | |
| Jabber Software Foundation | |
| EMail: | stpeter@jabber.org |
| TOC |
The following XML schema is descriptive, not normative.
<?xml version='1.0' encoding='UTF-8'?>
<xs:schema
xmlns:xs='http://www.w3.org/2001/XMLSchema'
targetNamespace='urn:ietf:params:xml:ns:xmpp-e2e'
xmlns='urn:ietf:params:xml:ns:xmpp-e2e'
elementFormDefault='qualified'>
<xs:element name='e2e' type='xs:string'/>
</xs:schema>
| TOC |
Note to RFC Editor: please remove this entire appendix, and the corresponding entries in the table of contents, prior to publication.
| TOC |
The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director.
Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Funding for the RFC Editor function is currently provided by the Internet Society.