draft-ietf-xmpp-e2e-07.txt   draft-ietf-xmpp-e2e-08.txt 
XMPP Working Group P. Saint-Andre XMPP Working Group P. Saint-Andre
Internet-Draft Jabber Software Foundation Internet-Draft Jabber Software Foundation
Expires: June 29, 2004 December 30, 2003 Expires: November 25, 2004 May 27, 2004
End-to-End Object Encryption in the Extensible Messaging and Presence End-to-End Object Encryption in the Extensible Messaging and Presence
Protocol (XMPP) Protocol (XMPP)
draft-ietf-xmpp-e2e-07 draft-ietf-xmpp-e2e-08
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 June 29, 2004. This Internet-Draft will expire on November 25, 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 memo defines a method for end-to-end object signing and This memo defines a method for end-to-end object signing and
encryption in the Extensible Messaging and Presence Protocol (XMPP). encryption in the Extensible Messaging and Presence Protocol (XMPP).
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Securing Messages . . . . . . . . . . . . . . . . . . . . . . 5 3. Securing Messages . . . . . . . . . . . . . . . . . . . . . . 4
4. Securing Presence . . . . . . . . . . . . . . . . . . . . . . 6 4. Securing Presence . . . . . . . . . . . . . . . . . . . . . . 6
5. Securing Arbitrary XMPP Data . . . . . . . . . . . . . . . . . 8 5. Securing Arbitrary XMPP Data . . . . . . . . . . . . . . . . . 8
6. Rules for S/MIME Generation and Handling . . . . . . . . . . . 9 6. Rules for S/MIME Generation and Handling . . . . . . . . . . . 10
7. Secure Communications Through a Gateway . . . . . . . . . . . 12 7. Secure Communications Through a Gateway . . . . . . . . . . . 13
8. Security Considerations . . . . . . . . . . . . . . . . . . . 13 8. urn:ietf:params:xml:xmpp-e2e Namespace . . . . . . . . . . . . 13
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 9. application/xmpp+xml Media Type . . . . . . . . . . . . . . . 14
Normative References . . . . . . . . . . . . . . . . . . . . . 14 10. Security Considerations . . . . . . . . . . . . . . . . . . . 14
Informative References . . . . . . . . . . . . . . . . . . . . 16 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 16 Normative References . . . . . . . . . . . . . . . . . . . . . 15
A. Schema for urn:ietf:params:xml:ns:xmpp-e2e . . . . . . . . . . 16 Informative References . . . . . . . . . . . . . . . . . . . . 17
B. Revision History . . . . . . . . . . . . . . . . . . . . . . . 17 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 17
Intellectual Property and Copyright Statements . . . . . . . . 19 A. Schema for urn:ietf:params:xml:ns:xmpp-e2e . . . . . . . . . . 18
B. Revision History . . . . . . . . . . . . . . . . . . . . . . . 18
Intellectual Property and Copyright Statements . . . . . . . . 20
1. Introduction 1. Introduction
This memo define a method for end-to-end signing and encryption in This memo define a method for end-to-end signing and encryption in
the Extensible Messaging and Presence Protocol (XMPP). (For the Extensible Messaging and Presence Protocol (XMPP). (For
information about XMPP, see [XMPP-CORE] and [XMPP-IM].) The method information about XMPP, see [XMPP-CORE] and [XMPP-IM].) The method
defined herein enables a sender to encrypt and/or sign an instant specified herein enables a sender to encrypt and/or sign an instant
message sent to a specific recipient, encrypt and/or sign presence 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 directed to a specific user, and sign presence
information that is broadcasted to a specific user. This memo information that is broadcasted to a specific user. This memo
thereby helps the XMPP specifications meet the requirements defined thereby helps the XMPP specifications meet the requirements specified
in [IMP-REQS]. in [IMP-REQS].
1.1 Terminology 1.1 Terminology
This document inherits terminology defined in [SMIME], [IMP-MODEL], This document inherits terminology defined in [SMIME], [IMP-MODEL],
[CMS], and [XMPP-CORE]. [CMS], and [XMPP-CORE].
The capitalized key words "MUST", "MUST NOT", "REQUIRED", "SHALL", The capitalized key words "MUST", "MUST NOT", "REQUIRED", "SHALL",
"SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
[TERMS]. [TERMS].
1.2 Discussion Venue 1.2 Discussion Venue
The authors welcome discussion and comments related to the topics The authors welcome discussion and comments related to the topics
presented in this document. The preferred forum is the presented in this document. The preferred forum is the
<xmppwg@jabber.org> mailing list, for which archives and subscription <xmppwg@jabber.org> mailing list, for which archives and subscription
information are available at <http://www.jabber.org/cgi-bin/mailman/ information are available at <<http://www.jabber.org/cgi-bin/mailman/
listinfo/xmppwg/>. listinfo/xmppwg/>>.
1.3 Intellectual Property Notice
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.
2. Requirements 2. Requirements
For the purposes of this memo, we stipulate the following For the purposes of this memo, we stipulate the following
requirements: requirements:
1. The method defined MUST address encryption and signing 1. The method defined MUST address encryption and signing
requirements for minimal instant messaging and presence only, as requirements for minimal instant messaging and presence only, as
those are defined in [IMP-REQS]. The method is NOT REQUIRED to those are defined in [IMP-REQS]. The method is NOT REQUIRED to
support non-IM applications of XMPP, nor to support advanced support non-IM applications of XMPP, nor to support advanced
skipping to change at page 5, line 26 skipping to change at page 4, line 50
4. In order to enable interoperable implementations, sending and 4. In order to enable interoperable implementations, sending and
receiving applications MUST implement the algorithms defined receiving applications MUST implement the algorithms defined
under Section 6.9. under Section 6.9.
3. Securing Messages 3. Securing Messages
In order to encrypt a message, a sending entity MUST use the In order to encrypt a message, a sending entity MUST use the
following procedure: following procedure:
1. Generate a "Message/CPIM" object as defined in [MSGFMT]. 1. Generate a "Message/CPIM" object as defined in [MSGFMT].
2. Encrypt and/or sign both the headers and content of the "Message/ 2. Encrypt and/or sign both the headers and content of the "Message/
CPIM" object as specified in Requirement 3 of Section 2 above. CPIM" object as specified in Requirement 3 of Section 2 above.
3. Provide the resulting multipart [SMIME] object (see [MULTI]) 3. Provide the resulting multipart [SMIME] object (see [MULTI])
within a CDATA section of an <e2e/> child of a <message/> stanza, within a CDATA section of an <e2e/> child of a <message/> stanza,
where the <e2e/> element is qualified by the where the <e2e/> element is qualified by the
'urn:ietf:params:xml:ns:xmpp-e2e' namespace. 'urn:ietf:params:xml:ns:xmpp-e2e' namespace as specified more
fully in Section 8 below.
Example 1: Sender generates "Message/CPIM" object: Example 1: Sender generates "Message/CPIM" object:
Content-type: Message/CPIM Content-type: Message/CPIM
From: Juliet Capulet <im:juliet@example.com> From: Juliet Capulet <im:juliet@example.com>
To: Romeo Montague <im:romeo@example.net> To: Romeo Montague <im:romeo@example.net>
DateTime: 2003-12-09T11:45:36.66Z DateTime: 2003-12-09T11:45:36.66Z
Subject: Imploring Subject: Imploring
skipping to change at page 8, line 22 skipping to change at page 9, line 8
common denominator" messaging and presence data of the kind that can common denominator" messaging and presence data of the kind that can
be directly translated into the MSGFMT or PIDF formats. However, be directly translated into the MSGFMT or PIDF formats. However,
XMPP possesses a third base-level stanza type (<iq/>) in addition to XMPP possesses a third base-level stanza type (<iq/>) in addition to
<message/> and <presence/>, as well as the ability to include <message/> and <presence/>, as well as the ability to include
extended XML data within arbitrary child elements of the three core extended XML data within arbitrary child elements of the three core
stanza types. Therefore it would be desirable to secure such data if stanza types. Therefore it would be desirable to secure such data if
possible. possible.
Because [MSGFMT] specifies the ability to encapsulate any MIME type, Because [MSGFMT] specifies the ability to encapsulate any MIME type,
the approach taken in this memo is to include arbitrary XMPP data in 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 an XML media type named "application/xmpp+xml" as specified more
MIME type is <xmpp/>, and the root element MUST contain one and only fully in Section 9 below.
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/ The following examples illustrate the structure of the "application/
xmpp+xml" MIME type. xmpp+xml" MIME type.
Example 5: Message stanza with extended data contained in Example 5: Message stanza with extended data contained in
"application/xmpp+xml" MIME type: "application/xmpp+xml" MIME type:
<?xml version='1.0' encoding='UTF-8'?> <?xml version='1.0' encoding='UTF-8'?>
<xmpp xmlns='jabber:client'> <xmpp xmlns='jabber:client'>
<message <message
skipping to change at page 13, line 12 skipping to change at page 13, line 49
presence document from the non-XMPP service that is addressed to a presence document from the non-XMPP service that is addressed to a
user on the XMPP service, it MUST remove the non-XMPP "wrapper" user on the XMPP service, it MUST remove the non-XMPP "wrapper"
(if any) in order to reveal the multipart S/MIME object, wrap the (if any) in order to reveal the multipart S/MIME object, wrap the
object in an XMPP message or presence "wrapper" (including the object in an XMPP message or presence "wrapper" (including the
<e2e> and </e2e> tags), and then route the XMPP stanza to the XMPP <e2e> and </e2e> tags), and then route the XMPP stanza to the XMPP
service. service.
The wrapped S/MIME object MUST be immutable and MUST NOT be modified The wrapped S/MIME object MUST be immutable and MUST NOT be modified
by an XMPP-CPIM gateway. by an XMPP-CPIM gateway.
8. Security Considerations 8. urn:ietf:params:xml:xmpp-e2e Namespace
The <e2e xmlns='urn:ietf:params:xml:ns:xmpp-e2e'/> element is a
wrapper for an XML CDATA section (as specified in Section 2.7 of
[XML]) that contains a "Message/CPIM", "application/pidf+xml", or
"application/xmpp+xml" object. Thus the
'urn:ietf:params:xml:xmpp-e2e' namespace has no inherent semantics,
and the semantics of the encapsulated object are defined by one of
the following specifications:
o [MSGFMT] for "Message/CPIM"
o [PIDF] for "application/pidf+xml"
o [XMPP-CORE] for "application/xmpp+xml"
Although the "application/xmpp+xml" media type is specified in this
document, the <xmpp/> element is simply a wrapper for a <message/>,
<presence/>, or <iq/> stanza, where the semantics of those stanza
types are specified in [XMPP-CORE].
Given that the 'urn:ietf:params:xml:ns:xmpp-e2e' namespace has no
inherent semantics and specifies a using protocol only, versioning is
the responsibility of the protocols that define the encapsulated
objects ([MSGFMT], [PIDF], and [XMPP-CORE]).
9. application/xmpp+xml Media Type
The "application/xmpp+xml" media type adheres to the guidelines
specified in [XML-MEDIA]. 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 character encoding
for this XML media type MUST be UTF-8, in accordance with Section
11.5 of [XMPP-CORE].
10. Security Considerations
This entire memo discusses security. Detailed security This entire memo discusses security. Detailed security
considerations for instant messaging and presence protocols are given considerations for instant messaging and presence protocols are given
in [IMP-REQS] (Sections 5.1 through 5.4), and for XMPP in particular 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). are given in [XMPP-CORE] (Sections 12.1 through 12.6). In addition,
all of the security considerations specified in [XML-MEDIA] apply to
the "application/xmpp+xml" media type.
The end-to-end security method defined here MAY result in exchanging The end-to-end security method defined here MAY result in exchanging
secured instant messages and presence information through a gateway secured instant messages and presence information through a gateway
that implements the CPIM specifications. Such a gateway MUST be that implements the CPIM specifications. Such a gateway MUST be
compliant with the minimum security requirements of the instant compliant with the minimum security requirements of the instant
messaging and presence protocols with which it interfaces. messaging and presence protocols with which it interfaces.
9. IANA Considerations 11. IANA Considerations
9.1 Content-type Registration for "application/xmpp+xml" 11.1 XML Namespace Name for e2e Data in XMPP
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: IESG, <iesg@ietf.org>
11.2 Content-type Registration for "application/xmpp+xml"
To: ietf-types@iana.org To: ietf-types@iana.org
Subject: Registration of MIME media type application/xmpp+xml Subject: Registration of MIME media type application/xmpp+xml
MIME media type name: application MIME media type name: application
MIME subtype name: xmpp+xml MIME subtype name: xmpp+xml
Required parameters: (none) Required parameters: (none)
Optional parameters: (charset) Same as charset parameter of
Optional parameters: charset Indicates the character encoding of the application/xml as specified in RFC 3023; per Section 11.5 of
enclosed XML; the default encoding is UTF-8. [draft-ietf-xmpp-core-24], the charset must be UTF-8.
Encoding considerations: Same as encoding considerations of
Encoding considerations: Contains XML, which can employ 8-bit application/xml as specified in RFC 3023; per Section 11.5 of
characters, depending on the character encoding used. [draft-ietf-xmpp-core-24], the encoding must be UTF-8.
Security considerations: All of the security considerations specified
Security considerations: Contains a message, presence information, or in RFC 3023 and [draft-ietf-xmpp-core-24] apply to this XML media
IQ (request-response) data in XMPP, which may be considered type. Refer to Section 10 of XXXX.
private. Appropriate precautions should be adopted to limit
disclosure of this information.
Interoperability considerations: (none) Interoperability considerations: (none)
Specification: XXXX Specification: XXXX
Applications which use this media type: XMPP-compliant instant Applications which use this media type: XMPP-compliant instant
messaging and presence systems. messaging and presence systems.
Additional information: (none) Additional information: (none)
Person and email address to contact for further information: IESG,
Person and email address to contact for further information: IETF, <iesg@ietf.org>
XMPP Working Group, <xmppwg@jabber.org>
Intended usage: COMMON Intended usage: COMMON
Author/Change controller: IETF, XMPP Working Group Author/Change controller: IETF, XMPP Working Group
9.2 XML Namespace Name for e2e Data in XMPP
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>
Normative References Normative References
[CERT] Ramsdell, B., "S/MIME Version 3 Certificate Handling", RFC [CERT] Ramsdell, B., "S/MIME Version 3 Certificate Handling", RFC
2632, June 1999. 2632, June 1999.
[CMC] Blaze, M., Ioannidis, J. and A. Keromytis, "DSA and RSA [CMC] Blaze, M., Ioannidis, J. and A. Keromytis, "DSA and RSA
Key and Signature Encoding for the KeyNote Trust Key and Signature Encoding for the KeyNote Trust
Management System", RFC 2792, March 2000. Management System", RFC 2792, March 2000.
[CMP] Adams, C. and S. Farrell, "Internet X.509 Public Key [CMP] Adams, C. and S. Farrell, "Internet X.509 Public Key
skipping to change at page 16, line 10 skipping to change at page 17, line 19
RFC 2633, June 1999. RFC 2633, June 1999.
[TERMS] Bradner, S., "Key words for use in RFCs to Indicate [TERMS] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[X509] Housley, R., Polk, W., Ford, W. and D. Solo, "Internet [X509] Housley, R., Polk, W., Ford, W. and D. Solo, "Internet
X.509 Public Key Infrastructure Certificate and X.509 Public Key Infrastructure Certificate and
Certificate Revocation List (CRL) Profile", RFC 3280, Certificate Revocation List (CRL) Profile", RFC 3280,
April 2002. April 2002.
[XML] Bray, T., Paoli, J., Sperberg-McQueen, C. and E. Maler,
"Extensible Markup Language (XML) 1.0 (2nd ed)", W3C
REC-xml, October 2000, <http://www.w3.org/TR/REC-xml>.
[XML-MEDIA]
Murata, M., St. Laurent, S. and D. Kohn, "XML Media
Types", RFC 3023, January 2001.
[XMPP-CORE] [XMPP-CORE]
Saint-Andre, P., "XMPP Core", draft-ietf-xmpp-core-21 Saint-Andre, P., "XMPP Core", draft-ietf-xmpp-core-24
(work in progress), December 2003. (work in progress), May 2004.
[XMPP-IM] Saint-Andre, P., "XMPP Instant Messaging", [XMPP-IM] Saint-Andre, P., "XMPP Instant Messaging",
draft-ietf-xmpp-im-20 (work in progress), December 2003. draft-ietf-xmpp-im-22 (work in progress), May 2004.
Informative References Informative References
[XML-REG] Mealling, M., "The IANA XML Registry", [XML-REG] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
draft-mealling-iana-xmlns-registry-05 (work in progress), January 2004.
June 2003.
[XMPP-CPIM] [XMPP-CPIM]
Saint-Andre, P., "Mapping the Extensible Messaging and Saint-Andre, P., "Mapping the Extensible Messaging and
Presence Protocol (XMPP) to Common Presence and Instant Presence Protocol (XMPP) to Common Presence and Instant
Messaging (CPIM)", draft-ietf-xmpp-cpim-03 (work in Messaging (CPIM)", draft-ietf-xmpp-cpim-05 (work in
progress), November 2003. progress), May 2004.
Author's Address Author's Address
Peter Saint-Andre Peter Saint-Andre
Jabber Software Foundation Jabber Software Foundation
EMail: stpeter@jabber.org EMail: stpeter@jabber.org
Appendix A. Schema for urn:ietf:params:xml:ns:xmpp-e2e Appendix A. Schema for urn:ietf:params:xml:ns:xmpp-e2e
skipping to change at page 17, line 10 skipping to change at page 18, line 26
<xs:element name='e2e' type='xs:string'/> <xs:element name='e2e' type='xs:string'/>
</xs:schema> </xs:schema>
Appendix B. Revision History Appendix B. 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.
B.1 Changes from draft-ietf-xmpp-e2e-06 B.1 Changes from draft-ietf-xmpp-e2e-07
o Specified use of SHA-1 for digest and AES for content encryption. o Clarified relationship of the 'urn:ietf:params:xml:ns:xmpp-e2e'
namespace to its encapsulated objects, including versioning, and
placed this content in its own section.
o Clarified nature of "application/xmpp+xml" media type and placed
this content in its own section.
o Added reference to RFC 3023 and modified XML media type
registration to adhere to the guidelines specified therein.
o Changed XML params registrant to IESG, per RFC 3688.
o Updated other references.
o Specified order of signing then encrypting. B.2 Changes from draft-ietf-xmpp-e2e-06
o Specified use of SHA-1 for digest and AES for content encryption.
o Specified order of signing then encrypting.
o Specified format and checking of timestamps. o Specified format and checking of timestamps.
o Clarified use of subjectAltName field, where the GeneralName o Clarified use of subjectAltName field, where the GeneralName
content is a URI of the form im:user@host and pres:user@host. content is a URI of the form im:user@host and pres:user@host.
o Clarified circumstances under which certificates should be o Clarified circumstances under which certificates should be
attached. attached.
o Added Content-Disposition header field to examples. o Added Content-Disposition header field to examples.
B.2 Changes from draft-ietf-xmpp-e2e-05 B.3 Changes from draft-ietf-xmpp-e2e-05
o Addressed I-D nits and RFC Editor formatting. o Addressed I-D nits and RFC Editor formatting.
B.3 Changes from draft-ietf-xmpp-e2e-04 B.4 Changes from draft-ietf-xmpp-e2e-04
o Added text about instant inbox addresses. o Added text about instant inbox addresses.
B.4 Changes from draft-ietf-xmpp-e2e-03 B.5 Changes from draft-ietf-xmpp-e2e-03
o Specified that S/MIME multipart objects are enclosed in a CDATA o Specified that S/MIME multipart objects are enclosed in a CDATA
section. section.
o Changed "text/xml" to "text/plain" for message examples. o Changed "text/xml" to "text/plain" for message examples.
o Specified must-implement technologies, transfer encodings, o Specified must-implement technologies, transfer encodings,
certificate enrollment, certificate retrieval, and certificate certificate enrollment, certificate retrieval, and certificate
names (including subjectAltName for JIDs). names (including subjectAltName for JIDs).
o Specified requirements regarding attachment of signatures and o Specified requirements regarding attachment of signatures and
inclusion of certificates. inclusion of certificates.
o Fixed some small terminological errors. o Fixed some small terminological errors.
B.5 Changes from draft-ietf-xmpp-e2e-02 B.6 Changes from draft-ietf-xmpp-e2e-02
o Completely revised to use formats defined in the CPIM o Completely revised to use formats defined in the CPIM
specifications, S/MIME only, etc. specifications, S/MIME only, etc.
B.6 Changes from draft-ietf-xmpp-e2e-01 B.7 Changes from draft-ietf-xmpp-e2e-01
o Removed old Section 6 (Signalling Support via Presence) -- the o Removed old Section 6 (Signalling Support via Presence) -- the
ability to sign broadcasted presence made it redundant. ability to sign broadcasted presence made it redundant.
o Made small editorial changes to address RFC Editor requirements. o Made small editorial changes to address RFC Editor requirements.
B.7 Changes from draft-ietf-xmpp-e2e-00 B.8 Changes from draft-ietf-xmpp-e2e-00
o Added support for all stanza types. o Added support for all stanza types.
o Specified that the full stanza is encrypted. o Specified that the full stanza is encrypted.
o Added support for S/MIME in addition to OpenPGP. o Added support for S/MIME in addition to OpenPGP.
o Specified that encrypted presence must be directed to a specific o Specified that encrypted presence must be directed to a specific
recipient. recipient.
o Specified order of encrypting and signing. o Specified order of encrypting and signing.
o Added support for signing broadcasted presence. o Added support for signing broadcasted presence.
o Added IANA considerations. o Added IANA considerations.
o Changed namespace to 'urn:ietf:params:xml:ns:xmpp-e2e'. o Changed namespace to 'urn:ietf:params:xml:ns:xmpp-e2e'.
o Added XML schema. o Added XML schema.
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
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
skipping to change at page 19, line 29 skipping to change at page 20, 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
 End of changes. 57 change blocks. 
113 lines changed or deleted 126 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/