idnits 2.17.1 draft-ietf-xmpp-e2e-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The exact meaning of the all-uppercase expression 'NOT REQUIRED' is not defined in RFC 2119. If it is intended as a requirements expression, it should be rewritten using one of the combinations defined in RFC 2119; otherwise it should not be all-uppercase. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (December 30, 2003) is 7420 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'XMPP-CPIM' is defined on line 691, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2632 (ref. 'CERT') (Obsoleted by RFC 3850) ** Downref: Normative reference to an Informational RFC: RFC 2792 (ref. 'CMC') ** Obsolete normative reference: RFC 2510 (ref. 'CMP') (Obsoleted by RFC 4210) ** Obsolete normative reference: RFC 3369 (ref. 'CMS') (Obsoleted by RFC 3852) == Outdated reference: A later version (-04) exists of draft-ietf-impp-im-03 == Outdated reference: A later version (-04) exists of draft-ietf-impp-pres-03 ** Downref: Normative reference to an Informational RFC: RFC 2778 (ref. 'IMP-MODEL') ** Downref: Normative reference to an Informational RFC: RFC 2779 (ref. 'IMP-REQS') ** Obsolete normative reference: RFC 2633 (ref. 'SMIME') (Obsoleted by RFC 3851) ** Obsolete normative reference: RFC 3280 (ref. 'X509') (Obsoleted by RFC 5280) == Outdated reference: A later version (-24) exists of draft-ietf-xmpp-core-21 == Outdated reference: A later version (-22) exists of draft-ietf-xmpp-im-20 == Outdated reference: A later version (-05) exists of draft-ietf-xmpp-cpim-03 Summary: 9 errors (**), 0 flaws (~~), 9 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 XMPP Working Group P. Saint-Andre 2 Internet-Draft Jabber Software Foundation 3 Expires: June 29, 2004 December 30, 2003 5 End-to-End Object Encryption in the Extensible Messaging and Presence 6 Protocol (XMPP) 7 draft-ietf-xmpp-e2e-07 9 Status of this Memo 11 This document is an Internet-Draft and is in full conformance with 12 all provisions of Section 10 of RFC2026. 14 Internet-Drafts are working documents of the Internet Engineering 15 Task Force (IETF), its areas, and its working groups. Note that other 16 groups may also distribute working documents as Internet-Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six months 19 and may be updated, replaced, or obsoleted by other documents at any 20 time. It is inappropriate to use Internet-Drafts as reference 21 material or to cite them other than as "work in progress." 23 The list of current Internet-Drafts can be accessed at http:// 24 www.ietf.org/ietf/1id-abstracts.txt. 26 The list of Internet-Draft Shadow Directories can be accessed at 27 http://www.ietf.org/shadow.html. 29 This Internet-Draft will expire on June 29, 2004. 31 Copyright Notice 33 Copyright (C) The Internet Society (2003). All Rights Reserved. 35 Abstract 37 This memo defines a method for end-to-end object signing and 38 encryption in the Extensible Messaging and Presence Protocol (XMPP). 40 Table of Contents 42 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 43 2. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 3 44 3. Securing Messages . . . . . . . . . . . . . . . . . . . . . . 5 45 4. Securing Presence . . . . . . . . . . . . . . . . . . . . . . 6 46 5. Securing Arbitrary XMPP Data . . . . . . . . . . . . . . . . . 8 47 6. Rules for S/MIME Generation and Handling . . . . . . . . . . . 9 48 7. Secure Communications Through a Gateway . . . . . . . . . . . 12 49 8. Security Considerations . . . . . . . . . . . . . . . . . . . 13 50 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 51 Normative References . . . . . . . . . . . . . . . . . . . . . 14 52 Informative References . . . . . . . . . . . . . . . . . . . . 16 53 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 16 54 A. Schema for urn:ietf:params:xml:ns:xmpp-e2e . . . . . . . . . . 16 55 B. Revision History . . . . . . . . . . . . . . . . . . . . . . . 17 56 Intellectual Property and Copyright Statements . . . . . . . . 19 58 1. Introduction 60 This memo define a method for end-to-end signing and encryption in 61 the Extensible Messaging and Presence Protocol (XMPP). (For 62 information about XMPP, see [XMPP-CORE] and [XMPP-IM].) The method 63 defined herein enables a sender to encrypt and/or sign an instant 64 message sent to a specific recipient, encrypt and/or sign presence 65 information that is directed to a specific user, and sign presence 66 information that is broadcasted to a specific user. This memo 67 thereby helps the XMPP specifications meet the requirements defined 68 in [IMP-REQS]. 70 1.1 Terminology 72 This document inherits terminology defined in [SMIME], [IMP-MODEL], 73 [CMS], and [XMPP-CORE]. 75 The capitalized key words "MUST", "MUST NOT", "REQUIRED", "SHALL", 76 "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and 77 "OPTIONAL" in this document are to be interpreted as described in 78 [TERMS]. 80 1.2 Discussion Venue 82 The authors welcome discussion and comments related to the topics 83 presented in this document. The preferred forum is the 84 mailing list, for which archives and subscription 85 information are available at . 88 1.3 Intellectual Property Notice 90 This document is in full compliance with all provisions of Section 10 91 of RFC 2026. Parts of this specification use the term "jabber" for 92 identifying namespaces and other protocol syntax. Jabber[tm] is a 93 registered trademark of Jabber, Inc. Jabber, Inc. grants permission 94 to the IETF for use of the Jabber trademark in association with this 95 specification and its successors, if any. 97 2. Requirements 99 For the purposes of this memo, we stipulate the following 100 requirements: 102 1. The method defined MUST address encryption and signing 103 requirements for minimal instant messaging and presence only, as 104 those are defined in [IMP-REQS]. The method is NOT REQUIRED to 105 support non-IM applications of XMPP, nor to support advanced 106 instant messaging and presence functionality that is outside the 107 scope of [IMP-REQS]. In particular, the method MUST address the 108 following requirements defined in [IMP-REQS]: 110 * The protocol MUST provide means to ensure confidence that a 111 received message (NOTIFICATION or INSTANT MESSAGE) has not 112 been corrupted or tampered with. (Section 2.5.1) 114 * The protocol MUST provide means to ensure confidence that a 115 received message (NOTIFICATION or INSTANT MESSAGE) has not 116 been recorded and played back by an adversary. (Section 117 2.5.2) 119 * The protocol MUST provide means to ensure that a sent message 120 (NOTIFICATION or INSTANT MESSAGE) is only readable by ENTITIES 121 that the sender allows. (Section 2.5.3) 123 * The protocol MUST allow any client to use the means to ensure 124 non-corruption, non-playback, and privacy, but the protocol 125 MUST NOT require that all clients use these means at all 126 times. (Section 2.5.4) 128 * When A establishes a SUBSCRIPTION to B's PRESENCE INFORMATION, 129 the protocol MUST provide A means of verifying the accurate 130 receipt of the content B chooses to disclose to A. (Section 131 5.1.4) 133 * The protocol MUST provide A means of verifying that the 134 presence information is accurate, as sent by B. (Section 135 5.3.1) 137 * The protocol MUST provide A means of ensuring that no other 138 PRINCIPAL C can see the content of M. (Section 5.4.6) 140 * The protocol MUST provide A means of ensuring that no other 141 PRINCIPAL C can tamper with M, and B means to verify that no 142 tampering has occurred. (Section 5.4.7) 144 2. The method defined MUST enable interoperability with non-XMPP 145 messaging systems that support the Common Presence and Instant 146 Messaging (CPIM) specifications defined by the Instant Messaging 147 and Presence (IMPP) Working Group. Therefore: 149 * Prior to encrypting or signing, the format of an instant 150 message MUST conform to the CPIM Message Format defined in 151 [MSGFMT]. 153 * Prior to encrypting or signing, the format of presence 154 information MUST conform to the CPP Presence Information Data 155 Format defined in [PIDF]. 157 3. The method MUST follow the required procedures (including the 158 specific algorithms) defined in [CPIM] and [CPP]. In particular, 159 these documents specify: 161 * Encryption MUST use [SMIME] encryption with [CMS] 162 EnvelopeData. 164 * Signing MUST use [SMIME] signatures with [CMS] SignedData. 166 4. In order to enable interoperable implementations, sending and 167 receiving applications MUST implement the algorithms defined 168 under Section 6.9. 170 3. Securing Messages 172 In order to encrypt a message, a sending entity MUST use the 173 following procedure: 175 1. Generate a "Message/CPIM" object as defined in [MSGFMT]. 177 2. Encrypt and/or sign both the headers and content of the "Message/ 178 CPIM" object as specified in Requirement 3 of Section 2 above. 180 3. Provide the resulting multipart [SMIME] object (see [MULTI]) 181 within a CDATA section of an child of a stanza, 182 where the element is qualified by the 183 'urn:ietf:params:xml:ns:xmpp-e2e' namespace. 185 Example 1: Sender generates "Message/CPIM" object: 187 Content-type: Message/CPIM 189 From: Juliet Capulet 190 To: Romeo Montague 191 DateTime: 2003-12-09T11:45:36.66Z 192 Subject: Imploring 194 Content-type: text/plain; charset=utf-8 195 Content-ID: <1234567890@example.com> 197 Wherefore art thou, Romeo? 199 Example 2: Sender generates signed message (the 'from' address on the 200 XMPP message stanza is stamped by sender's server): 202 203 204 213 To: Romeo Montague 214 DateTime: 2003-12-09T23:45:36.66Z 215 Subject: Imploring 217 Content-type: text/plain; charset=utf-8 218 Content-ID: <1234567890@example.com> 220 Wherefore art thou, Romeo? 221 --next 222 Content-Type: application/pkcs7-signature 223 Content-Disposition: attachment;handling=required;filename=smime.p7s 225 [signed body part] 227 --next-- 228 ]]> 229 230 232 4. Securing Presence 234 In order to encrypt presence information, a sending entity MUST use 235 the following procedure: 237 1. Generate an "application/pidf+xml" object as defined in [PIDF]. 239 2. Encrypt and/or sign the "application/pidf+xml" object as 240 specified in Requirement 3 of Section 2 above. 242 3. Provide the resulting [SMIME] object within a CDATA section of an 243 child of a stanza, where the element is 244 qualified by the 'urn:ietf:params:xml:ns:xmpp-e2e' namespace. 245 The stanza MUST include a 'to' attribute, i.e., it 246 must be an instance of directed presence as defined in [XMPP-IM]. 248 Example 3: Sender generates "application/pidf+xml" object: 250 251 254 256 open 257 away 258 259 retired to the chamber 260 2003-12-09T23:53:11.31 261 262 264 Example 4: Sender generates signed presence (the 'from' address on 265 the XMPP presence stanza is stamped by sender's server): 267 268 269 278 279 282 283 284 open 285 away 286 287 retired to the chamber 288 2003-12-09T23:53:11.31Z 289 290 291 --next 292 Content-Type: application/pkcs7-signature 293 Content-Disposition: attachment;handling=required;filename=smime.p7s 295 [signed body part] 296 --next-- 297 ]]> 298 299 301 5. Securing Arbitrary XMPP Data 303 The foregoing sections of this memo describe how to secure "least 304 common denominator" messaging and presence data of the kind that can 305 be directly translated into the MSGFMT or PIDF formats. However, 306 XMPP possesses a third base-level stanza type () in addition to 307 and , as well as the ability to include 308 extended XML data within arbitrary child elements of the three core 309 stanza types. Therefore it would be desirable to secure such data if 310 possible. 312 Because [MSGFMT] specifies the ability to encapsulate any MIME type, 313 the approach taken in this memo is to include arbitrary XMPP data in 314 a new MIME type, "application/xmpp+xml". The root element for this 315 MIME type is , and the root element MUST contain one and only 316 one child element, corresponding to one of the XMPP stanza types 317 (i.e., message, presence, or iq) if the default namespace is 318 'jabber:client' or 'jabber:server' as defined in [XMPP-CORE]. 320 The following examples illustrate the structure of the "application/ 321 xmpp+xml" MIME type. 323 Example 5: Message stanza with extended data contained in 324 "application/xmpp+xml" MIME type: 326 327 328 331 332 I told him what I thought, and told no more 333 Than what he found himself was apt and true. 334 335 336 337 339 Example 6: Presence stanza with extended data contained in 340 "application/xmpp+xml" MIME type: 342 343 344 345 dnd 346 Fomenting dissension 347 348 349 351 Example 7: IQ stanza with extended data contained in "application/ 352 xmpp+xml" MIME type: 354 355 356 360 361 Stabber 362 666 363 FiendOS 364 365 366 367 369 6. Rules for S/MIME Generation and Handling 371 6.1 Certificate Enrollment 373 [SMIME] does not specify how to obtain a certificate from a 374 certificate authority, but instead mandates that every sending agent 375 must already have a certificate. The PKIX Working Group has, at the 376 time of this writing, produced two separate standards for certificate 377 enrollment: [CMP] and [CMC]. Which method to use for certificate 378 enrollment is outside the scope of this memo. 380 6.2 Certificate Retrieval 382 A receiving agent MUST provide some certificate retrieval mechanism 383 in order to gain access to certificates for recipients of digital 384 envelopes. This memo does not cover how S/MIME agents handle 385 certificates, only what they do after a certificate has been 386 validated or rejected. S/MIME certification issues are covered in 387 [CERT]. 389 At a minimum, for initial S/MIME deployment, a user agent could 390 automatically generate a message to an intended recipient requesting 391 that recipient's certificate in a signed return message. Receiving 392 and sending agents SHOULD also provide a mechanism to allow a user to 393 "store and protect" certificates for correspondents in such a way so 394 as to guarantee their later retrieval. 396 6.3 Certificate Names 398 End-entity certificates used by XMPP entities in the context of this 399 memo SHOULD contain a valid instant messaging and presence address. 400 The address SHOULD be specified as both an 'im:' URI (for instant 401 messaging, as defined in [CPIM]) and a 'pres:' URI (for presence, as 402 defined in [CPP]); each of these URIs SHOULD be specified in a 403 separate GeneralName entry of type uniformResourceIdentifier inside 404 the subjectAltName (i.e., two separate entries). Information in the 405 subject distinguished name SHOULD be ignored. 407 Each URI MUST be of the form or , where 408 the "address" portion is an XMPP address (also referred to as a 409 Jabber Identifier or JID) as defined in [XMPP-CORE], prepended with 410 the 'im:' or 'pres:' URI scheme. The address SHOULD be of the form 411 (i.e., a "bare JID"), although any valid JID form MAY 412 be used. 414 The value of the JID contained in the XMPP 'from' attribute SHOULD 415 match the JID provided in the signer's certificate, with the 416 exception that the resource identifier portion of the JID contained 417 in the 'from' attribute SHOULD be ignored for matching purposes. 419 Receiving agents SHOULD check that sending JID matches a JID provided 420 in the signer's certificate, with the exception that the resource 421 identifier portion of the JID contained in the 'from' attribute MAY 422 be ignored for matching purposes. A receiving agent SHOULD provide 423 some explicit alternate processing of the message if this comparison 424 fails, which may be to display a message that shows the recipient the 425 addresses in the certificate or other certificate details. 427 The subject alternative name extension is used in S/MIME as the 428 preferred means to convey the instant messaging and presence address 429 that corresponds to the entity for this certificate. Any instant 430 messaging or presence address present in the certificate SHOULD be 431 encoded using the otherName choice of the subjectAltName type along 432 with a type-id of "xmpp" (as these terms are profiled in [X509]). 434 6.4 Transfer Encoding 436 Because it is expected that XMPP applications will not interface with 437 older 7-bit systems, the transfer encoding (as defined in Section 438 3.1.2 of [SMIME]) MUST be "binary". 440 6.5 Attachment of Signatures 442 Sending agents SHOULD attach a signature to each encrypted message or 443 presence stanza. If a signature is attached, a Content-Disposition 444 header field (as defined in [DISP]) SHOULD be included to specify how 445 the signature is to be handled by the receiving application. 447 6.6 Inclusion of Certificates 449 If the sender and recipient are involved in an active messaging 450 session over a period of time, the sending agent SHOULD include the 451 sender's certificate along with at least one encrypted message stanza 452 every five minutes. Outside the context of an active messaging 453 session, the sending agent SHOULD include the sender's certificate 454 along with each encrypted message stanza. A sending agent MAY 455 include the sender's certificate along with each encrypted presence 456 stanza. However, a sending agent SHOULD NOT include a certificate 457 more than once every five minutes. 459 6.7 Order of Signing and Encrypting 461 If a stanza is both signed and encrypted, it SHOULD be signed first, 462 then encrypted. 464 6.8 Checking of Timestamps 466 Timestamps are included in "Message/CPIM" and "application/pidf+xml" 467 objects to help prevent replay attacks. All timestamps MUST conform 468 to [DATETIME] and be presented as UTC with no offset, including 469 fractions of a second as appropriate. Absent a local adjustment to 470 the sending application's perceived time or the underlying clock 471 time, the sending application MUST ensure that the timestamps it 472 sends to the receiver increase monotonically (if necessary by 473 incrementing the seconds fraction in the timestamp if the clock 474 returns the same time for multiple requests). The following rules 475 apply to the receiving application: 477 o it MUST verify that the timestamp received is within five minutes 478 of the current time 480 o it SHOULD verify that the timestamp received is greater than any 481 timestamp received in the last 10 minutes which passed the 482 previous check 484 o if any of the foregoing checks fails, the timestamp SHOULD be 485 presented to the receiving entity (human or via an API) marked as 486 "old timestamp", "future timestamp", or "decreasing timestamp" 488 6.9 Mandatory to Implement Technologies 490 At a minimum, all implementations MUST support the following CMS 491 algorithms as defined in [CMS-ALG]: 493 for digest: SHA-1 495 for signing: RSA 497 for content encryption: AES 499 7. Secure Communications Through a Gateway 501 A common method for achieving interoperability between two disparate 502 services is through the use of a "gateway" that interprets the 503 protocols of each service and translates them into the protocols of 504 the other. The CPIM specifications (specifically [MSGFMT] and [PIDF] 505 define the common profiles to be used for interoperability between 506 instant messaging and presence services that comply with [IMP-REQS]. 507 In the case of communications between an XMPP service and a non-XMPP 508 service, we can visualize this relationship as follows: 510 +-------------+ +-------------+ +------------+ 511 | | | | | | 512 | XMPP | | XMPP-CPIM | | Non-XMPP | 513 | Service | <----> | Gateway | <----> | Service | 514 | | | | | | 515 +-------------+ +-------------+ +------------+ 517 The end-to-end encryption method defined herein enables the exchange 518 of encrypted and/or signed instant messages and presence through an 519 XMPP-CPIM gateway. In particular: 521 o When a gateway receives a secured XMPP message or presence stanza 522 from the XMPP service that is addressed to a user on the non-XMPP 523 service, it MUST remove the XMPP "wrapper" (everything down to and 524 including the and tags) in order to reveal the 525 multipart S/MIME object, then route the object to the non-XMPP 526 service (first wrapping it in the protocol used by the non-XMPP 527 service if necessary). 529 o When a gateway receives a secured non-XMPP instant message or 530 presence document from the non-XMPP service that is addressed to a 531 user on the XMPP service, it MUST remove the non-XMPP "wrapper" 532 (if any) in order to reveal the multipart S/MIME object, wrap the 533 object in an XMPP message or presence "wrapper" (including the 534 and tags), and then route the XMPP stanza to the XMPP 535 service. 537 The wrapped S/MIME object MUST be immutable and MUST NOT be modified 538 by an XMPP-CPIM gateway. 540 8. Security Considerations 542 This entire memo discusses security. Detailed security 543 considerations for instant messaging and presence protocols are given 544 in [IMP-REQS] (Sections 5.1 through 5.4), and for XMPP in particular 545 are given in [XMPP-CORE] (Sections 12.1 through 12.6). 547 The end-to-end security method defined here MAY result in exchanging 548 secured instant messages and presence information through a gateway 549 that implements the CPIM specifications. Such a gateway MUST be 550 compliant with the minimum security requirements of the instant 551 messaging and presence protocols with which it interfaces. 553 9. IANA Considerations 555 9.1 Content-type Registration for "application/xmpp+xml" 557 To: ietf-types@iana.org 559 Subject: Registration of MIME media type application/xmpp+xml 561 MIME media type name: application 563 MIME subtype name: xmpp+xml 565 Required parameters: (none) 567 Optional parameters: charset Indicates the character encoding of the 568 enclosed XML; the default encoding is UTF-8. 570 Encoding considerations: Contains XML, which can employ 8-bit 571 characters, depending on the character encoding used. 573 Security considerations: Contains a message, presence information, or 574 IQ (request-response) data in XMPP, which may be considered 575 private. Appropriate precautions should be adopted to limit 576 disclosure of this information. 578 Interoperability considerations: (none) 580 Specification: XXXX 582 Applications which use this media type: XMPP-compliant instant 583 messaging and presence systems. 585 Additional information: (none) 587 Person and email address to contact for further information: IETF, 588 XMPP Working Group, 590 Intended usage: COMMON 592 Author/Change controller: IETF, XMPP Working Group 594 9.2 XML Namespace Name for e2e Data in XMPP 596 A URN sub-namespace for signed and encrypted content in the 597 Extensible Messaging and Presence Protocol (XMPP) is defined as 598 follows. (This namespace name adheres to the format defined in 599 [XML-REG].) 601 URI: urn:ietf:params:xml:ns:xmpp-e2e 603 Specification: XXXX 605 Description: This is the XML namespace name for signed and encrypted 606 content in the Extensible Messaging and Presence Protocol as 607 defined by XXXX. 609 Registrant Contact: IETF, XMPP Working Group, 611 Normative References 613 [CERT] Ramsdell, B., "S/MIME Version 3 Certificate Handling", RFC 614 2632, June 1999. 616 [CMC] Blaze, M., Ioannidis, J. and A. Keromytis, "DSA and RSA 617 Key and Signature Encoding for the KeyNote Trust 618 Management System", RFC 2792, March 2000. 620 [CMP] Adams, C. and S. Farrell, "Internet X.509 Public Key 621 Infrastructure Certificate Management Protocols", RFC 622 2510, March 1999. 624 [CMS] Housley, R., "Cryptographic Message Syntax (CMS)", RFC 625 3369, August 2002. 627 [CMS-ALG] Housley, R., "Cryptographic Message Syntax (CMS) 628 Algorithms", RFC 3370, August 2002. 630 [CPIM] Crocker, D. and J. Peterson, "Common Profile for Instant 631 Messaging (CPIM)", draft-ietf-impp-im-03 (work in 632 progress), May 2003. 634 [CPP] Crocker, D. and J. Peterson, "Common Profile for Presence 635 (CPP)", draft-ietf-impp-pres-03 (work in progress), May 636 2003. 638 [DATETIME] 639 Klyne, G. and C. Newman, "Date and Time on the Internet: 640 Timestamps", RFC 3339, July 2002. 642 [DISP] Troost, R., Dorner, S. and K. Moore, "Communicating 643 Presentation Information in Internet Messages: The 644 Content-Disposition Header Field", RFC 2183, August 1997. 646 [IMP-MODEL] 647 Day, M., Rosenberg, J. and H. Sugano, "A Model for 648 Presence and Instant Messaging", RFC 2778, February 2000, 649 . 651 [IMP-REQS] 652 Day, M., Aggarwal, S. and J. Vincent, "Instant Messaging / 653 Presence Protocol Requirements", RFC 2779, February 2000. 655 [MSGFMT] Atkins, D. and G. Klyne, "Common Presence and Instant 656 Messaging: Message Format", draft-ietf-impp-cpim-msgfmt-08 657 (work in progress), January 2003. 659 [MULTI] Galvin, J., Murphy, S., Crocker, S. and N. Freed, 660 "Security Multiparts for MIME: Multipart/Signed and 661 Multipart/Encrypted", RFC 1847, October 1995. 663 [PIDF] Fujimoto, S., Sugano, H., Klyne, G., Bateman, A., Carr, W. 664 and J. Peterson, "Presence Information Data Format", 665 draft-ietf-impp-cpim-pidf-08 (work in progress), May 2003. 667 [SMIME] Ramsdell, B., "S/MIME Version 3 Message Specification", 668 RFC 2633, June 1999. 670 [TERMS] Bradner, S., "Key words for use in RFCs to Indicate 671 Requirement Levels", BCP 14, RFC 2119, March 1997. 673 [X509] Housley, R., Polk, W., Ford, W. and D. Solo, "Internet 674 X.509 Public Key Infrastructure Certificate and 675 Certificate Revocation List (CRL) Profile", RFC 3280, 676 April 2002. 678 [XMPP-CORE] 679 Saint-Andre, P., "XMPP Core", draft-ietf-xmpp-core-21 680 (work in progress), December 2003. 682 [XMPP-IM] Saint-Andre, P., "XMPP Instant Messaging", 683 draft-ietf-xmpp-im-20 (work in progress), December 2003. 685 Informative References 687 [XML-REG] Mealling, M., "The IANA XML Registry", 688 draft-mealling-iana-xmlns-registry-05 (work in progress), 689 June 2003. 691 [XMPP-CPIM] 692 Saint-Andre, P., "Mapping the Extensible Messaging and 693 Presence Protocol (XMPP) to Common Presence and Instant 694 Messaging (CPIM)", draft-ietf-xmpp-cpim-03 (work in 695 progress), November 2003. 697 Author's Address 699 Peter Saint-Andre 700 Jabber Software Foundation 702 EMail: stpeter@jabber.org 704 Appendix A. Schema for urn:ietf:params:xml:ns:xmpp-e2e 706 The following XML schema is descriptive, not normative. 708 710 716 718 720 Appendix B. Revision History 722 Note to RFC Editor: please remove this entire appendix, and the 723 corresponding entries in the table of contents, prior to publication. 725 B.1 Changes from draft-ietf-xmpp-e2e-06 727 o Specified use of SHA-1 for digest and AES for content encryption. 729 o Specified order of signing then encrypting. 731 o Specified format and checking of timestamps. 733 o Clarified use of subjectAltName field, where the GeneralName 734 content is a URI of the form im:user@host and pres:user@host. 736 o Clarified circumstances under which certificates should be 737 attached. 739 o Added Content-Disposition header field to examples. 741 B.2 Changes from draft-ietf-xmpp-e2e-05 743 o Addressed I-D nits and RFC Editor formatting. 745 B.3 Changes from draft-ietf-xmpp-e2e-04 747 o Added text about instant inbox addresses. 749 B.4 Changes from draft-ietf-xmpp-e2e-03 751 o Specified that S/MIME multipart objects are enclosed in a CDATA 752 section. 754 o Changed "text/xml" to "text/plain" for message examples. 756 o Specified must-implement technologies, transfer encodings, 757 certificate enrollment, certificate retrieval, and certificate 758 names (including subjectAltName for JIDs). 760 o Specified requirements regarding attachment of signatures and 761 inclusion of certificates. 763 o Fixed some small terminological errors. 765 B.5 Changes from draft-ietf-xmpp-e2e-02 767 o Completely revised to use formats defined in the CPIM 768 specifications, S/MIME only, etc. 770 B.6 Changes from draft-ietf-xmpp-e2e-01 772 o Removed old Section 6 (Signalling Support via Presence) -- the 773 ability to sign broadcasted presence made it redundant. 775 o Made small editorial changes to address RFC Editor requirements. 777 B.7 Changes from draft-ietf-xmpp-e2e-00 779 o Added support for all stanza types. 781 o Specified that the full stanza is encrypted. 783 o Added support for S/MIME in addition to OpenPGP. 785 o Specified that encrypted presence must be directed to a specific 786 recipient. 788 o Specified order of encrypting and signing. 790 o Added support for signing broadcasted presence. 792 o Added IANA considerations. 794 o Changed namespace to 'urn:ietf:params:xml:ns:xmpp-e2e'. 796 o Added XML schema. 798 Intellectual Property Statement 800 The IETF takes no position regarding the validity or scope of any 801 intellectual property or other rights that might be claimed to 802 pertain to the implementation or use of the technology described in 803 this document or the extent to which any license under such rights 804 might or might not be available; neither does it represent that it 805 has made any effort to identify any such rights. Information on the 806 IETF's procedures with respect to rights in standards-track and 807 standards-related documentation can be found in BCP-11. Copies of 808 claims of rights made available for publication and any assurances of 809 licenses to be made available, or the result of an attempt made to 810 obtain a general license or permission for the use of such 811 proprietary rights by implementors or users of this specification can 812 be obtained from the IETF Secretariat. 814 The IETF invites any interested party to bring to its attention any 815 copyrights, patents or patent applications, or other proprietary 816 rights which may cover technology that may be required to practice 817 this standard. Please address the information to the IETF Executive 818 Director. 820 Full Copyright Statement 822 Copyright (C) The Internet Society (2003). All Rights Reserved. 824 This document and translations of it may be copied and furnished to 825 others, and derivative works that comment on or otherwise explain it 826 or assist in its implementation may be prepared, copied, published 827 and distributed, in whole or in part, without restriction of any 828 kind, provided that the above copyright notice and this paragraph are 829 included on all such copies and derivative works. However, this 830 document itself may not be modified in any way, such as by removing 831 the copyright notice or references to the Internet Society or other 832 Internet organizations, except as needed for the purpose of 833 developing Internet standards in which case the procedures for 834 copyrights defined in the Internet Standards process must be 835 followed, or as required to translate it into languages other than 836 English. 838 The limited permissions granted above are perpetual and will not be 839 revoked by the Internet Society or its successors or assignees. 841 This document and the information contained herein is provided on an 842 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 843 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 844 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 845 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 846 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 848 Acknowledgment 850 Funding for the RFC Editor function is currently provided by the 851 Internet Society.