- From: Philipp Hoschka <ph@w3.org>
- Date: Thu, 22 Aug 2002 14:42:55 +0200
- To: ietf-types@iana.org
- CC: ietf-xml-mime@imc.org, www-smil@w3.org
- Message-ID: <3D64DC4F.D7A7B6B8@w3.org>
This email serves to instantiate the two week discussion period on "ietf-types@iana.org" of the ietf-draft describing the SMIL media-type registration. You can find the draft at http://www.ietf.org/internet-drafts/draft-hoschka-smil-media-type-10.txt The expected course of advancement for this specification is: 1. I have notified one of the Application area directors (Ned Freed) 2. Request publication as an Informational RFC as specified: ftp://ftp.isi.edu/in-notes/rfc-editor/instructions2authors.txt 3. Ensure IANA is aware of the publication and posts the registration as specified: ftp://ftp.isi.edu/in-notes/rfc2048.txt The changes in this specification since the last version discussed on "ietf-xml-mime@imc.org" include: 1. Registration of application/xml+smil in addition to application/smil 2. Addition of optional "profile" parameter 3. Addition of paragraph describing how to recognize SMIL files by looking into the file. Thank you. -- -Philipp Hoschka
J. Reagle
Internet-Draft W3C/LCS/MIT
Expires: October 2002 June 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. References
5. Author's Address
6. Full Copyright Statement
Reagle, J. Expires October 2002 [Page 1]
Internet-Draft XML Encryption Media-Type June 2002
1. Discussion 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 publicly 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
implementations) to note that the media type of the decrypted
(original) object might a type other than XML.
This media-type is only used for documents in which the XENC
EncyptedData and EncryptedKey element types appear as the root element
of the XML document. XML documents which contain XENC element types in
places other than the root element can be described using facilities
such as [XML-schema] or [StLaurent].
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
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 supersedes it.
Encoding considerations:
Same as charset parameter of application/xml as specified in RFC
3023 [XML-MT] or the most recent specification that supersedes it.
Security considerations:
Security considerations include many of those described in the
Reagle, J. Expires October 2002 [Page 2]
Internet-Draft XML Encryption Media-Type June 2002
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 be XML documents in which the
root element's QName's LocalPart is 'EncryptedData' with an
associated namespace name of 'http://www.w3.org/2001/04/xmlenc#'.
The application/xenc+xml type name MUST only be used for data
objects in which the root element is from the XENC namespace.
File extension(s): .xml
Macintosh File Type Code(s): "TEXT"
Person & email address to contact for further information:
Joseph Reagle <reagle@w3.org>
XENC Working Group <xml-encryption@w3.org>
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
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.
Reagle, J. Expires October 2002 [Page 3]
Internet-Draft XML Encryption Media-Type June 2002
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
StLaurent
Registration of xmlns Media Feature Tag. S. St.Laurent, and I.
Graham. Draft.
http://simonstl.com/ietf/draft-stlaurent-feature-xmlns-02.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-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/
5. Authors' Address
Joseph M. Reagle Jr., W3C
Massachusetts Institute of Technology
Laboratory for Computer Science
Reagle, J. Expires October 2002 [Page 4]
Internet-Draft XML Encryption Media-Type June 2002
NE43-358, 200 Technology Square
Cambridge, MA 02139
Phone: + 1.617.258.7621
Email: reagle@w3.org
6. 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.
Received on Thursday, 22 August 2002 08:46:55 UTC