W3C home > Mailing lists > Public > public-xmlsec@w3.org > December 2010

Fwd: Update of application/xenc+xml media type registration

From: Thomas Roessler <tlr@w3.org>
Date: Wed, 15 Dec 2010 13:28:14 +0100
Cc: Thomas Roessler <tlr@w3.org>
Message-Id: <2B71074A-7DE3-47D5-84AD-E60AF5699EF9@w3.org>
To: public-xmlsec@w3.org
FYI.

Probably worth linking to ACTION-499, ACTION-511 and ISSUE-180.
--
Thomas Roessler, W3C  <tlr@w3.org>  (@roessler)







Begin forwarded message:

> From: Thomas Roessler <tlr@w3.org>
> Date: 15 December 2010 13:26:12 GMT+01:00
> To: iana@iana.org
> Cc: Thomas Roessler <tlr@w3.org>, ietf-types@iana.org, Joseph Reagle <reagle@mit.edu>, Frederick Hirsch <Frederick.Hirsch@nokia.com>
> Subject: Update of application/xenc+xml media type registration
> 
> 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.
> 
> 
Received on Wednesday, 15 December 2010 12:28:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 15 December 2010 12:28:20 GMT