J. Reagle Internet-Draft W3C/LCS/MIT Expires: May 22, 2002 Otober 2002 application/xenc+xml Media Type Registration draft-reagle-xenc-mediatype-00 Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http:// www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on October 22, 2002. Copyright Notice Copyright (C) The Internet Society (2002). All Rights Reserved. Abstract This document describes a media type (application/xenc+xml) for use with the XML Encryption specification. Table of Contents 1. Discussion of this Document 2. Introduction 3. application/xenc+xml Registration 4. Fragment Identifiers 5. Historical Considerations 6. IANA Considerations 7. Acknowledgements 8. References 9. Author's Address 10. Full Copyright Statement _________________________________________________________________ 1 Dicussion of this Document Please send comments to xml-encryption@w3.org. To subscribe, send a message with the body 'subscribe' to xml-encryption@w3.org. The mailing list is publically archived at http://lists.w3.org/Archives/Public/xml-encryption/ . 2 Introduction The XML Encryption Syntax and Processing document [XENC] specifies a process for encrypting data and representing the result in XML. The data may be arbitrary data (including an XML document), an XML element, or XML element content. The result of encrypting data is an XML Encryption element which contains or references the cipher data. The application/xenc+xml media type allows XENC applications to identify XENC documents for processing. Additionally it allows applications cognizant of this media-type (even if they are not XENC implmentations) to note that the media type of the decrypted (original) object might a type other than xml. 3. application/xenc+xml Registration This is a media type registration as defined in Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures [MIME-REG] MIME media type name: application MIME subtype name: xenc+xml @@ Should we include a redundant type parameter of the encrypted object? @@ Required parameters: none Optional parameters: charset Same as charset parameter of application/xml as specified in RFC 3023 [XML-MT] or the most recent specification that supercedes it. Encoding considerations: Same as charset parameter of application/xml as specified in RFC 3023 [XML-MT] or the most recent specification that supercedes it. Security considerations: Security considerations include many of those described in the Security Considerations of [XENC]. Interoperability considerations: none Published specification: [XENC]. Applications which use this media type: XENC is device-, platform-, and vendor-neutral and is supported by a range of Web applications. Additional Information: Magic number(s): none Although no byte sequences can be counted on to consistently identify XENC documents, they will have the sequence http://www.w3.org/2001/04/xmlenc# to identify the XENC namespace. This will usually be towards the top of the document, but may occur further down if parts of the XML document are being encrypted. File extension(s): .xml Macintosh File Type Code(s): "TEXT" Person & email address to contact for further information: Joseph Reagle XENC Working Group Intended usage: COMMON Author/Change controller: The XENC specification is a work product of the World Wide Web Consortium. The W3C and the W3C XENC Working Group have change control over the specification. 4 References EncReq XML Encryption Requirements. W3C Note. J. Reagle. W3C, March 2002. http://www.w3.org/TR/2002/NOTE-xml-encryption-req-20020304 Glossary RFC 2828. Internet Security Glossary. Informational. R Shirey. 2000 http://www.ietf.org/rfc/rfc2828.txt HTTP RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1. Internet Official Protocol Standards. J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, T. Berners-Lee. June 1999. http://www.ietf.org/rfc/rfc2616.txt KEYWORDS RFC 2119: Key words for use in RFCs to Indicate Requirement Levels. Best Current Practice. S. Bradner. March 1997. http://www.ietf.org/rfc/rfc2119.txt MIME RFC 2045: Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies. Standards Track. N. Freed & N. Borenstein. November 1996. http://www.ietf.org/rfc/rfc2045.txt MIME-REG RFC 2048: Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures. IETF BCP 13. Freed, N., Klensin, J. and J. Postel. November 1996. URI RFC 2396: Uniform Resource Identifiers (URI): Generic Syntax. Standards Track. T. Berners-Lee, R. Fielding, L. Masinter. August 1998. http://www.ietf.org/rfc/rfc2396.txt http://www.ietf.org/rfc/rfc1738.txt http://www.ietf.org/rfc/rfc2141.txt RFC 2611: URN Namespace Definition Mechanisms. Best Current Practices. Daigle, D. van Gulik, R. Iannella, P. Falstrom. June 1999. http://www.ietf.org/rfc/rfc2611.txt XENC XML Encryption Syntax and Processing. D. Eastlake, and J. Reagle. W3C Candidate Recommendation, 2002. http://www.w3.org/TR/2002/CR-xmlenc-core-20020304/ XML Extensible Markup Language (XML) 1.0 (Second Edition). T. Bray, J. Paoli, C. M. Sperberg-McQueen, E. Maler. W3C Recommendation, October 2000. XML-DSIG XML-Signature Syntax and Processing. D. Eastlake, J. Reagle, and D. Solo. W3C Recommendation, February 2002. http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/ XML-MT RFC 3023: XML Media Types. Informational. M. Murata, S. St.Laurent, D Kohn. January 2001. http://www.ietf.org/rfc/rfc2376.txt XML-NS Namespaces in XML. T. Bray, D. Hollander, A. Layman. W3C Recommendation, January 1999. http://www.w3.org/TR/1999/REC-xml-names-19990114 XML-schema XML Schema Part 1: Structures D. Beech, M. Maloney, N. Mendelsohn. W3C Recommendation, May 2001. http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/ XML Schema Part 2: Datatypes. P. Biron, A. Malhotra. W3C Recommendation, May 2001. http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/ Full Copyright Copyright (C) The Internet Society (2002). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.