idnits 2.17.1 draft-ietf-xmpp-e2e-08.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 == The page length should not exceed 58 lines per page, but there was 19 longer pages, the longest (page 17) being 70 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 21 pages 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 (May 27, 2004) is 7274 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 689, 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') -- Possible downref: Non-RFC (?) normative reference: ref. 'PIDF' ** Obsolete normative reference: RFC 2633 (ref. 'SMIME') (Obsoleted by RFC 3851) ** Obsolete normative reference: RFC 3280 (ref. 'X509') (Obsoleted by RFC 5280) -- Possible downref: Non-RFC (?) normative reference: ref. 'XML' ** Obsolete normative reference: RFC 3023 (ref. 'XML-MEDIA') (Obsoleted by RFC 7303) Summary: 10 errors (**), 0 flaws (~~), 8 warnings (==), 5 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: November 25, 2004 May 27, 2004 5 End-to-End Object Encryption in the Extensible Messaging and Presence 6 Protocol (XMPP) 7 draft-ietf-xmpp-e2e-08 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 November 25, 2004. 31 Copyright Notice 33 Copyright (C) The Internet Society (2004). 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 . . . . . . . . . . . . . . . . . . . . . . 4 45 4. Securing Presence . . . . . . . . . . . . . . . . . . . . . . 6 46 5. Securing Arbitrary XMPP Data . . . . . . . . . . . . . . . . . 8 47 6. Rules for S/MIME Generation and Handling . . . . . . . . . . . 10 48 7. Secure Communications Through a Gateway . . . . . . . . . . . 13 49 8. urn:ietf:params:xml:xmpp-e2e Namespace . . . . . . . . . . . . 13 50 9. application/xmpp+xml Media Type . . . . . . . . . . . . . . . 14 51 10. Security Considerations . . . . . . . . . . . . . . . . . . . 14 52 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 53 Normative References . . . . . . . . . . . . . . . . . . . . . 15 54 Informative References . . . . . . . . . . . . . . . . . . . . 17 55 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 17 56 A. Schema for urn:ietf:params:xml:ns:xmpp-e2e . . . . . . . . . . 18 57 B. Revision History . . . . . . . . . . . . . . . . . . . . . . . 18 58 Intellectual Property and Copyright Statements . . . . . . . . 20 60 1. Introduction 62 This memo define a method for end-to-end signing and encryption in 63 the Extensible Messaging and Presence Protocol (XMPP). (For 64 information about XMPP, see [XMPP-CORE] and [XMPP-IM].) The method 65 specified herein enables a sender to encrypt and/or sign an instant 66 message sent to a specific recipient, encrypt and/or sign presence 67 information that is directed to a specific user, and sign presence 68 information that is broadcasted to a specific user. This memo 69 thereby helps the XMPP specifications meet the requirements specified 70 in [IMP-REQS]. 72 1.1 Terminology 74 This document inherits terminology defined in [SMIME], [IMP-MODEL], 75 [CMS], and [XMPP-CORE]. 77 The capitalized key words "MUST", "MUST NOT", "REQUIRED", "SHALL", 78 "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and 79 "OPTIONAL" in this document are to be interpreted as described in 80 [TERMS]. 82 1.2 Discussion Venue 84 The authors welcome discussion and comments related to the topics 85 presented in this document. The preferred forum is the 86 mailing list, for which archives and subscription 87 information are available at <>. 90 2. Requirements 92 For the purposes of this memo, we stipulate the following 93 requirements: 95 1. The method defined MUST address encryption and signing 96 requirements for minimal instant messaging and presence only, as 97 those are defined in [IMP-REQS]. The method is NOT REQUIRED to 98 support non-IM applications of XMPP, nor to support advanced 99 instant messaging and presence functionality that is outside the 100 scope of [IMP-REQS]. In particular, the method MUST address the 101 following requirements defined in [IMP-REQS]: 102 * The protocol MUST provide means to ensure confidence that a 103 received message (NOTIFICATION or INSTANT MESSAGE) has not 104 been corrupted or tampered with. (Section 2.5.1) 105 * The protocol MUST provide means to ensure confidence that a 106 received message (NOTIFICATION or INSTANT MESSAGE) has not 107 been recorded and played back by an adversary. (Section 108 2.5.2) 109 * The protocol MUST provide means to ensure that a sent message 110 (NOTIFICATION or INSTANT MESSAGE) is only readable by ENTITIES 111 that the sender allows. (Section 2.5.3) 112 * The protocol MUST allow any client to use the means to ensure 113 non-corruption, non-playback, and privacy, but the protocol 114 MUST NOT require that all clients use these means at all 115 times. (Section 2.5.4) 116 * When A establishes a SUBSCRIPTION to B's PRESENCE INFORMATION, 117 the protocol MUST provide A means of verifying the accurate 118 receipt of the content B chooses to disclose to A. (Section 119 5.1.4) 120 * The protocol MUST provide A means of verifying that the 121 presence information is accurate, as sent by B. (Section 122 5.3.1) 123 * The protocol MUST provide A means of ensuring that no other 124 PRINCIPAL C can see the content of M. (Section 5.4.6) 125 * The protocol MUST provide A means of ensuring that no other 126 PRINCIPAL C can tamper with M, and B means to verify that no 127 tampering has occurred. (Section 5.4.7) 128 2. The method defined MUST enable interoperability with non-XMPP 129 messaging systems that support the Common Presence and Instant 130 Messaging (CPIM) specifications defined by the Instant Messaging 131 and Presence (IMPP) Working Group. Therefore: 132 * Prior to encrypting or signing, the format of an instant 133 message MUST conform to the CPIM Message Format defined in 134 [MSGFMT]. 135 * Prior to encrypting or signing, the format of presence 136 information MUST conform to the CPP Presence Information Data 137 Format defined in [PIDF]. 138 3. The method MUST follow the required procedures (including the 139 specific algorithms) defined in [CPIM] and [CPP]. In particular, 140 these documents specify: 141 * Encryption MUST use [SMIME] encryption with [CMS] 142 EnvelopeData. 143 * Signing MUST use [SMIME] signatures with [CMS] SignedData. 144 4. In order to enable interoperable implementations, sending and 145 receiving applications MUST implement the algorithms defined 146 under Section 6.9. 148 3. Securing Messages 150 In order to encrypt a message, a sending entity MUST use the 151 following procedure: 153 1. Generate a "Message/CPIM" object as defined in [MSGFMT]. 154 2. Encrypt and/or sign both the headers and content of the "Message/ 155 CPIM" object as specified in Requirement 3 of Section 2 above. 157 3. Provide the resulting multipart [SMIME] object (see [MULTI]) 158 within a CDATA section of an child of a stanza, 159 where the element is qualified by the 160 'urn:ietf:params:xml:ns:xmpp-e2e' namespace as specified more 161 fully in Section 8 below. 163 Example 1: Sender generates "Message/CPIM" object: 165 Content-type: Message/CPIM 167 From: Juliet Capulet 168 To: Romeo Montague 169 DateTime: 2003-12-09T11:45:36.66Z 170 Subject: Imploring 172 Content-type: text/plain; charset=utf-8 173 Content-ID: <1234567890@example.com> 175 Wherefore art thou, Romeo? 176 Example 2: Sender generates signed message (the 'from' address on the 177 XMPP message stanza is stamped by sender's server): 179 180 181 190 To: Romeo Montague 191 DateTime: 2003-12-09T23: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? 198 --next 199 Content-Type: application/pkcs7-signature 200 Content-Disposition: attachment;handling=required;filename=smime.p7s 202 [signed body part] 204 --next-- 205 ]]> 206 207 209 4. Securing Presence 211 In order to encrypt presence information, a sending entity MUST use 212 the following procedure: 214 1. Generate an "application/pidf+xml" object as defined in [PIDF]. 215 2. Encrypt and/or sign the "application/pidf+xml" object as 216 specified in Requirement 3 of Section 2 above. 217 3. Provide the resulting [SMIME] object within a CDATA section of an 218 child of a stanza, where the element is 219 qualified by the 'urn:ietf:params:xml:ns:xmpp-e2e' namespace. 220 The stanza MUST include a 'to' attribute, i.e., it 221 must be an instance of directed presence as defined in [XMPP-IM]. 223 Example 3: Sender generates "application/pidf+xml" object: 225 226 229 231 open 232 away 233 234 retired to the chamber 235 2003-12-09T23:53:11.31 236 237 238 Example 4: Sender generates signed presence (the 'from' address on 239 the XMPP presence stanza is stamped by sender's server): 241 242 243 252 253 256 257 258 open 259 away 260 261 retired to the chamber 262 2003-12-09T23:53:11.31Z 263 264 265 --next 266 Content-Type: application/pkcs7-signature 267 Content-Disposition: attachment;handling=required;filename=smime.p7s 269 [signed body part] 271 --next-- 272 ]]> 273 274 276 5. Securing Arbitrary XMPP Data 278 The foregoing sections of this memo describe how to secure "least 279 common denominator" messaging and presence data of the kind that can 280 be directly translated into the MSGFMT or PIDF formats. However, 281 XMPP possesses a third base-level stanza type () in addition to 282 and , as well as the ability to include 283 extended XML data within arbitrary child elements of the three core 284 stanza types. Therefore it would be desirable to secure such data if 285 possible. 287 Because [MSGFMT] specifies the ability to encapsulate any MIME type, 288 the approach taken in this memo is to include arbitrary XMPP data in 289 an XML media type named "application/xmpp+xml" as specified more 290 fully in Section 9 below. 292 The following examples illustrate the structure of the "application/ 293 xmpp+xml" MIME type. 295 Example 5: Message stanza with extended data contained in 296 "application/xmpp+xml" MIME type: 298 299 300 303 304 I told him what I thought, and told no more 305 Than what he found himself was apt and true. 306 307 308 309 311 Example 6: Presence stanza with extended data contained in 312 "application/xmpp+xml" MIME type: 314 315 316 317 dnd 318 Fomenting dissension 319 320 321 322 Example 7: IQ stanza with extended data contained in "application/ 323 xmpp+xml" MIME type: 325 326 327 331 332 Stabber 333 666 334 FiendOS 335 336 337 338 340 6. Rules for S/MIME Generation and Handling 342 6.1 Certificate Enrollment 344 [SMIME] does not specify how to obtain a certificate from a 345 certificate authority, but instead mandates that every sending agent 346 must already have a certificate. The PKIX Working Group has, at the 347 time of this writing, produced two separate standards for certificate 348 enrollment: [CMP] and [CMC]. Which method to use for certificate 349 enrollment is outside the scope of this memo. 351 6.2 Certificate Retrieval 353 A receiving agent MUST provide some certificate retrieval mechanism 354 in order to gain access to certificates for recipients of digital 355 envelopes. This memo does not cover how S/MIME agents handle 356 certificates, only what they do after a certificate has been 357 validated or rejected. S/MIME certification issues are covered in 358 [CERT]. 360 At a minimum, for initial S/MIME deployment, a user agent could 361 automatically generate a message to an intended recipient requesting 362 that recipient's certificate in a signed return message. Receiving 363 and sending agents SHOULD also provide a mechanism to allow a user to 364 "store and protect" certificates for correspondents in such a way so 365 as to guarantee their later retrieval. 367 6.3 Certificate Names 369 End-entity certificates used by XMPP entities in the context of this 370 memo SHOULD contain a valid instant messaging and presence address. 371 The address SHOULD be specified as both an 'im:' URI (for instant 372 messaging, as defined in [CPIM]) and a 'pres:' URI (for presence, as 373 defined in [CPP]); each of these URIs SHOULD be specified in a 374 separate GeneralName entry of type uniformResourceIdentifier inside 375 the subjectAltName (i.e., two separate entries). Information in the 376 subject distinguished name SHOULD be ignored. 378 Each URI MUST be of the form or , where 379 the "address" portion is an XMPP address (also referred to as a 380 Jabber Identifier or JID) as defined in [XMPP-CORE], prepended with 381 the 'im:' or 'pres:' URI scheme. The address SHOULD be of the form 382 (i.e., a "bare JID"), although any valid JID form MAY 383 be used. 385 The value of the JID contained in the XMPP 'from' attribute SHOULD 386 match the JID provided in the signer's certificate, with the 387 exception that the resource identifier portion of the JID contained 388 in the 'from' attribute SHOULD be ignored for matching purposes. 390 Receiving agents SHOULD check that sending JID matches a JID provided 391 in the signer's certificate, with the exception that the resource 392 identifier portion of the JID contained in the 'from' attribute MAY 393 be ignored for matching purposes. A receiving agent SHOULD provide 394 some explicit alternate processing of the message if this comparison 395 fails, which may be to display a message that shows the recipient the 396 addresses in the certificate or other certificate details. 398 The subject alternative name extension is used in S/MIME as the 399 preferred means to convey the instant messaging and presence address 400 that corresponds to the entity for this certificate. Any instant 401 messaging or presence address present in the certificate SHOULD be 402 encoded using the otherName choice of the subjectAltName type along 403 with a type-id of "xmpp" (as these terms are profiled in [X509]). 405 6.4 Transfer Encoding 407 Because it is expected that XMPP applications will not interface with 408 older 7-bit systems, the transfer encoding (as defined in Section 409 3.1.2 of [SMIME]) MUST be "binary". 411 6.5 Attachment of Signatures 413 Sending agents SHOULD attach a signature to each encrypted message or 414 presence stanza. If a signature is attached, a Content-Disposition 415 header field (as defined in [DISP]) SHOULD be included to specify how 416 the signature is to be handled by the receiving application. 418 6.6 Inclusion of Certificates 420 If the sender and recipient are involved in an active messaging 421 session over a period of time, the sending agent SHOULD include the 422 sender's certificate along with at least one encrypted message stanza 423 every five minutes. Outside the context of an active messaging 424 session, the sending agent SHOULD include the sender's certificate 425 along with each encrypted message stanza. A sending agent MAY 426 include the sender's certificate along with each encrypted presence 427 stanza. However, a sending agent SHOULD NOT include a certificate 428 more than once every five minutes. 430 6.7 Order of Signing and Encrypting 432 If a stanza is both signed and encrypted, it SHOULD be signed first, 433 then encrypted. 435 6.8 Checking of Timestamps 437 Timestamps are included in "Message/CPIM" and "application/pidf+xml" 438 objects to help prevent replay attacks. All timestamps MUST conform 439 to [DATETIME] and be presented as UTC with no offset, including 440 fractions of a second as appropriate. Absent a local adjustment to 441 the sending application's perceived time or the underlying clock 442 time, the sending application MUST ensure that the timestamps it 443 sends to the receiver increase monotonically (if necessary by 444 incrementing the seconds fraction in the timestamp if the clock 445 returns the same time for multiple requests). The following rules 446 apply to the receiving application: 448 o it MUST verify that the timestamp received is within five minutes 449 of the current time 450 o it SHOULD verify that the timestamp received is greater than any 451 timestamp received in the last 10 minutes which passed the 452 previous check 453 o if any of the foregoing checks fails, the timestamp SHOULD be 454 presented to the receiving entity (human or via an API) marked as 455 "old timestamp", "future timestamp", or "decreasing timestamp" 457 6.9 Mandatory to Implement Technologies 459 At a minimum, all implementations MUST support the following CMS 460 algorithms as defined in [CMS-ALG]: 462 for digest: SHA-1 463 for signing: RSA 464 for content encryption: AES 466 7. Secure Communications Through a Gateway 468 A common method for achieving interoperability between two disparate 469 services is through the use of a "gateway" that interprets the 470 protocols of each service and translates them into the protocols of 471 the other. The CPIM specifications (specifically [MSGFMT] and [PIDF] 472 define the common profiles to be used for interoperability between 473 instant messaging and presence services that comply with [IMP-REQS]. 474 In the case of communications between an XMPP service and a non-XMPP 475 service, we can visualize this relationship as follows: 477 +-------------+ +-------------+ +------------+ 478 | | | | | | 479 | XMPP | | XMPP-CPIM | | Non-XMPP | 480 | Service | <----> | Gateway | <----> | Service | 481 | | | | | | 482 +-------------+ +-------------+ +------------+ 484 The end-to-end encryption method defined herein enables the exchange 485 of encrypted and/or signed instant messages and presence through an 486 XMPP-CPIM gateway. In particular: 488 o When a gateway receives a secured XMPP message or presence stanza 489 from the XMPP service that is addressed to a user on the non-XMPP 490 service, it MUST remove the XMPP "wrapper" (everything down to and 491 including the and tags) in order to reveal the 492 multipart S/MIME object, then route the object to the non-XMPP 493 service (first wrapping it in the protocol used by the non-XMPP 494 service if necessary). 495 o When a gateway receives a secured non-XMPP instant message or 496 presence document from the non-XMPP service that is addressed to a 497 user on the XMPP service, it MUST remove the non-XMPP "wrapper" 498 (if any) in order to reveal the multipart S/MIME object, wrap the 499 object in an XMPP message or presence "wrapper" (including the 500 and tags), and then route the XMPP stanza to the XMPP 501 service. 503 The wrapped S/MIME object MUST be immutable and MUST NOT be modified 504 by an XMPP-CPIM gateway. 506 8. urn:ietf:params:xml:xmpp-e2e Namespace 508 The element is a 509 wrapper for an XML CDATA section (as specified in Section 2.7 of 511 [XML]) that contains a "Message/CPIM", "application/pidf+xml", or 512 "application/xmpp+xml" object. Thus the 513 'urn:ietf:params:xml:xmpp-e2e' namespace has no inherent semantics, 514 and the semantics of the encapsulated object are defined by one of 515 the following specifications: 517 o [MSGFMT] for "Message/CPIM" 518 o [PIDF] for "application/pidf+xml" 519 o [XMPP-CORE] for "application/xmpp+xml" 521 Although the "application/xmpp+xml" media type is specified in this 522 document, the element is simply a wrapper for a , 523 , or stanza, where the semantics of those stanza 524 types are specified in [XMPP-CORE]. 526 Given that the 'urn:ietf:params:xml:ns:xmpp-e2e' namespace has no 527 inherent semantics and specifies a using protocol only, versioning is 528 the responsibility of the protocols that define the encapsulated 529 objects ([MSGFMT], [PIDF], and [XMPP-CORE]). 531 9. application/xmpp+xml Media Type 533 The "application/xmpp+xml" media type adheres to the guidelines 534 specified in [XML-MEDIA]. The root element for this MIME type is 535 , and the root element MUST contain one and only one child 536 element, corresponding to one of the XMPP stanza types (i.e., 537 message, presence, or iq) if the default namespace is 'jabber:client' 538 or 'jabber:server' as defined in [XMPP-CORE]. The character encoding 539 for this XML media type MUST be UTF-8, in accordance with Section 540 11.5 of [XMPP-CORE]. 542 10. Security Considerations 544 This entire memo discusses security. Detailed security 545 considerations for instant messaging and presence protocols are given 546 in [IMP-REQS] (Sections 5.1 through 5.4), and for XMPP in particular 547 are given in [XMPP-CORE] (Sections 12.1 through 12.6). In addition, 548 all of the security considerations specified in [XML-MEDIA] apply to 549 the "application/xmpp+xml" media type. 551 The end-to-end security method defined here MAY result in exchanging 552 secured instant messages and presence information through a gateway 553 that implements the CPIM specifications. Such a gateway MUST be 554 compliant with the minimum security requirements of the instant 555 messaging and presence protocols with which it interfaces. 557 11. IANA Considerations 559 11.1 XML Namespace Name for e2e Data in XMPP 561 A URN sub-namespace for signed and encrypted content in the 562 Extensible Messaging and Presence Protocol (XMPP) is defined as 563 follows. (This namespace name adheres to the format defined in 564 [XML-REG].) 566 URI: urn:ietf:params:xml:ns:xmpp-e2e 567 Specification: XXXX 568 Description: This is the XML namespace name for signed and encrypted 569 content in the Extensible Messaging and Presence Protocol as 570 defined by XXXX. 571 Registrant Contact: IESG, 573 11.2 Content-type Registration for "application/xmpp+xml" 575 To: ietf-types@iana.org 577 Subject: Registration of MIME media type application/xmpp+xml 579 MIME media type name: application 580 MIME subtype name: xmpp+xml 581 Required parameters: (none) 582 Optional parameters: (charset) Same as charset parameter of 583 application/xml as specified in RFC 3023; per Section 11.5 of 584 [draft-ietf-xmpp-core-24], the charset must be UTF-8. 585 Encoding considerations: Same as encoding considerations of 586 application/xml as specified in RFC 3023; per Section 11.5 of 587 [draft-ietf-xmpp-core-24], the encoding must be UTF-8. 588 Security considerations: All of the security considerations specified 589 in RFC 3023 and [draft-ietf-xmpp-core-24] apply to this XML media 590 type. Refer to Section 10 of XXXX. 591 Interoperability considerations: (none) 592 Specification: XXXX 593 Applications which use this media type: XMPP-compliant instant 594 messaging and presence systems. 595 Additional information: (none) 596 Person and email address to contact for further information: IESG, 597 598 Intended usage: COMMON 599 Author/Change controller: IETF, XMPP Working Group 601 Normative References 603 [CERT] Ramsdell, B., "S/MIME Version 3 Certificate Handling", RFC 604 2632, June 1999. 606 [CMC] Blaze, M., Ioannidis, J. and A. Keromytis, "DSA and RSA 607 Key and Signature Encoding for the KeyNote Trust 608 Management System", RFC 2792, March 2000. 610 [CMP] Adams, C. and S. Farrell, "Internet X.509 Public Key 611 Infrastructure Certificate Management Protocols", RFC 612 2510, March 1999. 614 [CMS] Housley, R., "Cryptographic Message Syntax (CMS)", RFC 615 3369, August 2002. 617 [CMS-ALG] Housley, R., "Cryptographic Message Syntax (CMS) 618 Algorithms", RFC 3370, August 2002. 620 [CPIM] Crocker, D. and J. Peterson, "Common Profile for Instant 621 Messaging (CPIM)", draft-ietf-impp-im-03 (work in 622 progress), May 2003. 624 [CPP] Crocker, D. and J. Peterson, "Common Profile for Presence 625 (CPP)", draft-ietf-impp-pres-03 (work in progress), May 626 2003. 628 [DATETIME] 629 Klyne, G. and C. Newman, "Date and Time on the Internet: 630 Timestamps", RFC 3339, July 2002. 632 [DISP] Troost, R., Dorner, S. and K. Moore, "Communicating 633 Presentation Information in Internet Messages: The 634 Content-Disposition Header Field", RFC 2183, August 1997. 636 [IMP-MODEL] 637 Day, M., Rosenberg, J. and H. Sugano, "A Model for 638 Presence and Instant Messaging", RFC 2778, February 2000, 639 . 641 [IMP-REQS] 642 Day, M., Aggarwal, S. and J. Vincent, "Instant Messaging / 643 Presence Protocol Requirements", RFC 2779, February 2000. 645 [MSGFMT] Atkins, D. and G. Klyne, "Common Presence and Instant 646 Messaging: Message Format", draft-ietf-impp-cpim-msgfmt-08 647 (work in progress), January 2003. 649 [MULTI] Galvin, J., Murphy, S., Crocker, S. and N. Freed, 650 "Security Multiparts for MIME: Multipart/Signed and 651 Multipart/Encrypted", RFC 1847, October 1995. 653 [PIDF] Fujimoto, S., Sugano, H., Klyne, G., Bateman, A., Carr, W. 655 and J. Peterson, "Presence Information Data Format", 656 draft-ietf-impp-cpim-pidf-08 (work in progress), May 2003. 658 [SMIME] Ramsdell, B., "S/MIME Version 3 Message Specification", 659 RFC 2633, June 1999. 661 [TERMS] Bradner, S., "Key words for use in RFCs to Indicate 662 Requirement Levels", BCP 14, RFC 2119, March 1997. 664 [X509] Housley, R., Polk, W., Ford, W. and D. Solo, "Internet 665 X.509 Public Key Infrastructure Certificate and 666 Certificate Revocation List (CRL) Profile", RFC 3280, 667 April 2002. 669 [XML] Bray, T., Paoli, J., Sperberg-McQueen, C. and E. Maler, 670 "Extensible Markup Language (XML) 1.0 (2nd ed)", W3C 671 REC-xml, October 2000, . 673 [XML-MEDIA] 674 Murata, M., St. Laurent, S. and D. Kohn, "XML Media 675 Types", RFC 3023, January 2001. 677 [XMPP-CORE] 678 Saint-Andre, P., "XMPP Core", draft-ietf-xmpp-core-24 679 (work in progress), May 2004. 681 [XMPP-IM] Saint-Andre, P., "XMPP Instant Messaging", 682 draft-ietf-xmpp-im-22 (work in progress), May 2004. 684 Informative References 686 [XML-REG] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 687 January 2004. 689 [XMPP-CPIM] 690 Saint-Andre, P., "Mapping the Extensible Messaging and 691 Presence Protocol (XMPP) to Common Presence and Instant 692 Messaging (CPIM)", draft-ietf-xmpp-cpim-05 (work in 693 progress), May 2004. 695 Author's Address 697 Peter Saint-Andre 698 Jabber Software Foundation 700 EMail: stpeter@jabber.org 702 Appendix A. Schema for urn:ietf:params:xml:ns:xmpp-e2e 704 The following XML schema is descriptive, not normative. 706 708 714 716 718 Appendix B. Revision History 720 Note to RFC Editor: please remove this entire appendix, and the 721 corresponding entries in the table of contents, prior to publication. 723 B.1 Changes from draft-ietf-xmpp-e2e-07 725 o Clarified relationship of the 'urn:ietf:params:xml:ns:xmpp-e2e' 726 namespace to its encapsulated objects, including versioning, and 727 placed this content in its own section. 728 o Clarified nature of "application/xmpp+xml" media type and placed 729 this content in its own section. 730 o Added reference to RFC 3023 and modified XML media type 731 registration to adhere to the guidelines specified therein. 732 o Changed XML params registrant to IESG, per RFC 3688. 733 o Updated other references. 735 B.2 Changes from draft-ietf-xmpp-e2e-06 737 o Specified use of SHA-1 for digest and AES for content encryption. 738 o Specified order of signing then encrypting. 739 o Specified format and checking of timestamps. 740 o Clarified use of subjectAltName field, where the GeneralName 741 content is a URI of the form im:user@host and pres:user@host. 742 o Clarified circumstances under which certificates should be 743 attached. 744 o Added Content-Disposition header field to examples. 746 B.3 Changes from draft-ietf-xmpp-e2e-05 747 o Addressed I-D nits and RFC Editor formatting. 749 B.4 Changes from draft-ietf-xmpp-e2e-04 751 o Added text about instant inbox addresses. 753 B.5 Changes from draft-ietf-xmpp-e2e-03 755 o Specified that S/MIME multipart objects are enclosed in a CDATA 756 section. 757 o Changed "text/xml" to "text/plain" for message examples. 758 o Specified must-implement technologies, transfer encodings, 759 certificate enrollment, certificate retrieval, and certificate 760 names (including subjectAltName for JIDs). 761 o Specified requirements regarding attachment of signatures and 762 inclusion of certificates. 763 o Fixed some small terminological errors. 765 B.6 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.7 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. 774 o Made small editorial changes to address RFC Editor requirements. 776 B.8 Changes from draft-ietf-xmpp-e2e-00 778 o Added support for all stanza types. 779 o Specified that the full stanza is encrypted. 780 o Added support for S/MIME in addition to OpenPGP. 781 o Specified that encrypted presence must be directed to a specific 782 recipient. 783 o Specified order of encrypting and signing. 784 o Added support for signing broadcasted presence. 785 o Added IANA considerations. 786 o Changed namespace to 'urn:ietf:params:xml:ns:xmpp-e2e'. 787 o Added XML schema. 789 Intellectual Property Statement 791 The IETF takes no position regarding the validity or scope of any 792 intellectual property or other rights that might be claimed to 793 pertain to the implementation or use of the technology described in 794 this document or the extent to which any license under such rights 795 might or might not be available; neither does it represent that it 796 has made any effort to identify any such rights. Information on the 797 IETF's procedures with respect to rights in standards-track and 798 standards-related documentation can be found in BCP-11. Copies of 799 claims of rights made available for publication and any assurances of 800 licenses to be made available, or the result of an attempt made to 801 obtain a general license or permission for the use of such 802 proprietary rights by implementors or users of this specification can 803 be obtained from the IETF Secretariat. 805 The IETF invites any interested party to bring to its attention any 806 copyrights, patents or patent applications, or other proprietary 807 rights which may cover technology that may be required to practice 808 this standard. Please address the information to the IETF Executive 809 Director. 811 Full Copyright Statement 813 Copyright (C) The Internet Society (2004). All Rights Reserved. 815 This document and translations of it may be copied and furnished to 816 others, and derivative works that comment on or otherwise explain it 817 or assist in its implementation may be prepared, copied, published 818 and distributed, in whole or in part, without restriction of any 819 kind, provided that the above copyright notice and this paragraph are 820 included on all such copies and derivative works. However, this 821 document itself may not be modified in any way, such as by removing 822 the copyright notice or references to the Internet Society or other 823 Internet organizations, except as needed for the purpose of 824 developing Internet standards in which case the procedures for 825 copyrights defined in the Internet Standards process must be 826 followed, or as required to translate it into languages other than 827 English. 829 The limited permissions granted above are perpetual and will not be 830 revoked by the Internet Society or its successors or assignees. 832 This document and the information contained herein is provided on an 833 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 834 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 835 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 836 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 837 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 839 Acknowledgment 841 Funding for the RFC Editor function is currently provided by the 842 Internet Society.