[ietf-types] Update of application/xenc+xml media type registration

Thomas Roessler <tlr@w3.org> Wed, 15 December 2010 12:25 UTC

Return-Path: <tlr@w3.org>
X-Original-To: ietf-types@core3.amsl.com
Delivered-To: ietf-types@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AAB753A6D9A for <ietf-types@core3.amsl.com>; Wed, 15 Dec 2010 04:25:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level:
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_43=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7GDjTxoH8f+h for <ietf-types@core3.amsl.com>; Wed, 15 Dec 2010 04:24:58 -0800 (PST)
Received: from pechora4.lax.icann.org (pechora4.icann.org [IPv6:2620:0:2d0:1::39]) by core3.amsl.com (Postfix) with ESMTP id F050228C0CE for <ietf-types@ietf.org>; Wed, 15 Dec 2010 04:24:56 -0800 (PST)
Received: from jay.w3.org (ssh.w3.org [128.30.52.60]) by pechora4.lax.icann.org (8.13.8/8.13.8) with ESMTP id oBFCQH3I000387; Wed, 15 Dec 2010 04:26:38 -0800
Received: from jay.w3.org ([128.30.52.169] helo=[127.0.0.1]) by jay.w3.org with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.69) (envelope-from <tlr@w3.org>) id 1PSqQx-0002qJ-0P; Wed, 15 Dec 2010 07:26:15 -0500
From: Thomas Roessler <tlr@w3.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 15 Dec 2010 13:26:12 +0100
Message-Id: <15D64738-28B3-4C5B-8939-524F807F2DDD@w3.org>
To: iana@iana.org
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora4.lax.icann.org [208.77.188.39]); Wed, 15 Dec 2010 04:26:38 -0800 (PST)
X-Mailman-Approved-At: Wed, 15 Dec 2010 05:23:11 -0800
Cc: ietf-types@iana.org, Joseph Reagle <reagle@mit.edu>, Frederick Hirsch <Frederick.Hirsch@nokia.com>, Thomas Roessler <tlr@w3.org>
Subject: [ietf-types] Update of application/xenc+xml media type registration
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Dec 2010 12:25:12 -0000

Dear IANA,

the W3C is the change controller for the XML Encryption specification, which is the published specification for the application/xenc+xml media type.

The W3C XML Security Working Group has published a Last Call Working Draft for a version 1.1 of XML Encryption, including an updated media type registration template:

	http://www.w3.org/TR/2010/WD-xmlenc-core1-20101130/
	http://www.w3.org/TR/2010/WD-xmlenc-core1-20101130/#sec-MediaType-Registration

Please update the application/xenc+xml media type registration accordingly.

A text version of the updated media type registration template is included for your convenience below the .signature of this note.

Thanks,
--
Thomas Roessler, W3C  <tlr@w3.org>




8.2 application/xenc+xml Registration

   This is a media type registration as defined in Multipurpose Internet
   Mail Extensions (MIME) Part Four: Registration Procedures
   [[350]MIME-REG]

   Type name: application

   Subtype name: xenc+xml

   Required parameters: none

   Optional parameters: charset

     The allowable and recommended values for, and interpretation of the
     charset parameter are identical to those given for 'application/xml'
     in section 3.2 of RFC 3023 [[351]XML-MT].

   Encoding considerations:

     The encoding considerations are identical to those given for
     'application/xml' in section 3.2 of RFC 3023 [[352]XML-MT].

   Security considerations:

     See the [[353]XMLENC-CORE1] [354]Security Considerations section.

   Interoperability considerations: none

   Published specification: [[355]XMLENC-CORE1]

   Applications which use this media type:

     XML Encryption 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 XML Encryption documents, they will be XML documents in
     which the root element's QName's LocalPart is 'EncryptedData' or
     'EncryptedKey' with an associated namespace name of
     '[356]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 XML Encryption namespace. XML documents which
     contain these element types in places other than the root element
     can be described using facilities such as [[357]XMLSCHEMA-1],
     [[358]XMLSCHEMA-2].

     File extension(s): .xml

     Macintosh File Type Code(s): "TEXT"

   Person & email address to contact for further information:

     World Wide Web Consortium <web-human at w3.org>

   Intended usage: COMMON

   Author/Change controller:

   The XML Encryption specification is a work product of the World Wide
   Web Consortium (W3C) which has change control over the specification.