October 2009 - Ietf-types

Registration of media type application/ttaf+xml
by Philippe Le Hegaret 26 Aug '10

26 Aug '10

The following media type registration will be submitted to the IESG for review, approval, and registration with IANA (as per [1]). At this point, we would appreciate comments on this registration information. If you see any problems, please let us know. Regards, Philippe [1] http://www.w3.org/2002/06/registering-mediatype [[ This appendix registers a new MIME media type, "application/ttaf+xml" in conformance with [1144]BCP 13 and [1145]W3CRegMedia. The information in this appendix is being submitted to the Internet Engineering Steering Group (IESG) for review, approval, and registration with the Internet Assigned Numbers Authority (IANA). [1144] http://www.ietf.org/rfc/rfc4288.txt [1145] http://www.w3.org/2002/06/registering-mediatype.html MIME media type name: application MIME subtype name: ttaf+xml Required parameters: None. Optional parameters: The encoding of a TT AF document must be determined by the XML encoding declaration. This has identical semantics to the application/xml media type in the case where the charset parameter is omitted, as specified in [1146][XML Media], Sections 8.9, 8.10 and 8.11. The document profile of a TT AF document may be specified using an optional profile parameter, which, if specified, the value of which must adhere to the syntax and semantics of ttp:profile parameter defined by Section [1147]6.2.8 ttp:profile of the published specification. Encoding considerations: Same for application/xml. See [1148][XML Media], Section 3.2. Restrictions on usage: None. Security considerations: As with other XML types and as noted in [1149][XML Media] Section 10, repeated expansion of maliciously constructed XML entities can be used to consume large amounts of memory, which may cause XML processors in constrained environments to fail. In addition, because of the extensibility features for TT AF and of XML in general, it is possible that "application/ttaf+xml" may describe content that has security implications beyond those described here. However, if the processor follows only the normative semantics of the published specification, this content will be outside TT AF namespaces and may be ignored. Only in the case where the processor recognizes and processes the additional content, or where further processing of that content is dispatched to other processors, would security issues potentially arise. And in that case, they would fall outside the domain of this registration document. Interoperability considerations: The published specification describes processing semantics that dictate behavior that must be followed when dealing with, among other things, unrecognized elements and attributes, both in TT AF namespaces and in other namespaces. Because TT AF is extensible, conformant "application/ttaf+xml" processors must expect that content received is well-formed XML, but it cannot be guaranteed that the content is valid to a particular DTD or Schema or that the processor will recognize all of the elements and attributes in the document. Published specification: This media type registration is extracted from Appendix [1150]D Media Type Registration of the [1151]Timed Text (TT) Authoring Format 1.0 - Distribution Format Exchange Profile (DFXP) specification. [1151] http://www.w3.org/TR/ttaf1-dfxp/ Additional information: None. Person & email address to contact for further information: Glenn Adams (public-tt(a)w3.org) Intended usage: COMMON Author/Change controller: The published specification is a work product of the World Wide Web Consortium's Timed Text (TT) Working Group. The W3C has change control over this specification. ]] http://www.w3.org/TR/ttaf1-dfxp/#media-type-registration

7 9

[widgets] Media Type Registration for application/widget
by Marcos Caceres 28 Oct '09

28 Oct '09

Dear IETF, As part of the Widgets 1.0: Packaging and Configuration Specification progressing to Last Call, the W3C Web Applications Working Group would like to begin registration procedures for the "application/widget" MIME type. We have written a draft of the registration text for you to review and comment (full text below). The section in our specification that defines the registration can be found here: http://dev.w3.org/2006/waf/widgets/#media-type-registration-for-applicationw Our Last Call Review Period ends 19 of November, 2009. Kind regards, Marcos ------------ Media Type Registration for application/widget This appendix registers a new MIME media type, "application/widget" in conformance with BCP 13 and W3CRegMedia. This registration is for community review and will be submitted to the IANA. Type name: application subtype name: widget Required parameters: None. Optional parameters: None. Encoding considerations: Widget packages are binary data and thus are encoded for MIME transmission. As a widget package is binary, it requires encoding on transports not capable of handling binary. The same guidelines that apply to application/octet-stream apply to widget packages (see [MIME]). Security considerations: In addition to the security considerations specified for Zip files in the [Zip-MIME] registration, there are a number of security considerations that need to be taken into account when dealing with widget packages and configuration documents. As the configuration document format is [XML] and will commonly be ecoded using [Unicode], the security considerations described in [XML-MIME] and [UTR36] apply. In additon, implementers need to impose their own implementation-specific limits on the values of otherwise unconstrained attribute types, e.g. to prevent denial of service attacks, to guard against running out of memory, or to work around platform-specific limitations. The configuration document allows authors, through the feature element, to request permission to enable third-party runtime components and APIs. As these features are outside the scope of this specification, significant caution needs to be taken when granting a widget the capability to use a feature. Features themselves define their own security considerations. Widget packages will generally contain ECMAscript, HTML, CSS files, and other media, which are executed in a sand boxed environment. As such, implementers need to be aware of the security implications for the types they support. Specifically, implementers need to consider the security implications outlined in the [CSS-MIME] specification, the [ECMAScript-MIME] specification, and the [HTML-MIME] specification. As widget packages can contain content that is able to simultaneously interact with the local device and a remote host, implementers need to consider the privacy implications resulting from exposing private information to a remote host. Mitigation and in-depth defensive measures are an implementation responsibility and not prescribed by this specification. However, in designing these measures, implementors are advised to enable user awareness of information sharing, and to provide easy access to interfaces that enable revocation of permissions. As this specification relies on the standardized heuristics for determining the content type of files defined in the [SNIFF] specification, implementers need to consider the security considerations discussed in the [SNIFF] specification. As this specification allows for the declaration of IRIs within certain elements of a configuration documents, implementers need to consider the security considerations discussed in the [IRI] specification. Interoperability considerations: Some issues can arise with regards to character encodings of file names, the length of zip relative paths, and the use of certain strings as file names. This specification does not put a restriction on the byte length of a Zip relative path, so a user agent needs to be able to deal with Zip relative paths that have lengths longer than 250 bytes. As some operating systems have restrictions on how long a path length can be, authors need to keep the lengths of relative paths at less than 250 bytes. Unicode code points may require more than one byte to encode a character, which can result in a path whose length is less than 250 characters but whose size is greater than 250 bytes. Authors need to be aware that, at the time of publication, there are interoperability issues with regards to using characters outside the safe-chars range for file or folder names in a Zip archive when using Zipping tools bundled with operating systems. The interoperability issues have arisen from non-conforming implementations of the [ZIP] specification across operating systems: very few, if any, correctly support encoding file names in Unicode. In the case where the Zip relative path is encoded using [UTF-8], the language encoding flag (EFS) needs to be set. If an author chooses to use the utf8-chars, they need to thoroughly test their widgets on various platforms prior to distribution; otherwise it is suggested that authors restrict file and folder names to the safe-chars (characters in the US-ASCII range). In addition, having excessively long path names (e.g. over 120 characters) can also result in interoperability issues on some operating systems. Authors need to avoid using forbidden characters when naming the files used by a widget. These characters are reserved to maintain interoperability across various file systems and with [URI]s. Authors need to avoid using the following words as either a folder or a file-name in a Zip relative path as they are reserved by some operating systems (case-insensitive): CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, LPT9, CLOCKS$. For example, the following names are ok: "CON-tact.txt", "printer.lpt1", "DCOM1.pdf". However, "com3.txt" "Lpt1", "CoM9.gif" would not be. In addition, authors need to avoid having a "." U+002E FULL STOP as the last character of a file or folder name as some operating systems will remove the character when the file is extracted from the Zip archive onto the device. Furthermore, avoid having the space character (SP) at the start or end of a file name; and take caution when using the "+" U+002B PLUS SIGN, as it might cause issues on some operating systems. Published specification: http://www.w3.org/TR/widgets/ Applications that use this media type: User agents that claim conformance to this specification. Magic number(s): 50 4B 03 04 File extension(s): wgt Macintosh file type code(s): None. Person & email address to contact for further information: Steven Pemberton, member-webapps(a)w3.org Intended usage: Common. Restrictions on usage: None. Author: The W3C's Web Applications Working Group

1 0

[widgets] Media Type Registration for application/widget
by Marcos Caceres 28 Oct '09

28 Oct '09

Dear IETF, As part of the Widgets 1.0: Packaging and Configuration Specification progressing to Last Call, the W3C Web Applications Working Group would like to begin registration procedures for the "application/widget" MIME type. We have written a draft of the registration text for you to review and comment (full text below). The section in our specification that defines the registration can be found here: http://dev.w3.org/2006/waf/widgets/#media-type-registration-for-applicationw Our Last Call Review Period ends 19 of November, 2009. Kind regards, Marcos ------------ Media Type Registration for application/widget This appendix registers a new MIME media type, "application/widget" in conformance with BCP 13 and W3CRegMedia. This registration is for community review and will be submitted to the IANA. Type name: application subtype name: widget Required parameters: None. Optional parameters: None. Encoding considerations: Widget packages are binary data and thus are encoded for MIME transmission. As a widget package is binary, it requires encoding on transports not capable of handling binary. The same guidelines that apply to application/octet-stream apply to widget packages (see [MIME]). Security considerations: In addition to the security considerations specified for Zip files in the [Zip-MIME] registration, there are a number of security considerations that need to be taken into account when dealing with widget packages and configuration documents. As the configuration document format is [XML] and will commonly be ecoded using [Unicode], the security considerations described in [XML-MIME] and [UTR36] apply. In additon, implementers need to impose their own implementation-specific limits on the values of otherwise unconstrained attribute types, e.g. to prevent denial of service attacks, to guard against running out of memory, or to work around platform-specific limitations. The configuration document allows authors, through the feature element, to request permission to enable third-party runtime components and APIs. As these features are outside the scope of this specification, significant caution needs to be taken when granting a widget the capability to use a feature. Features themselves define their own security considerations. Widget packages will generally contain ECMAscript, HTML, CSS files, and other media, which are executed in a sand boxed environment. As such, implementers need to be aware of the security implications for the types they support. Specifically, implementers need to consider the security implications outlined in the [CSS-MIME] specification, the [ECMAScript-MIME] specification, and the [HTML-MIME] specification. As widget packages can contain content that is able to simultaneously interact with the local device and a remote host, implementers need to consider the privacy implications resulting from exposing private information to a remote host. Mitigation and in-depth defensive measures are an implementation responsibility and not prescribed by this specification. However, in designing these measures, implementors are advised to enable user awareness of information sharing, and to provide easy access to interfaces that enable revocation of permissions. As this specification relies on the standardized heuristics for determining the content type of files defined in the [SNIFF] specification, implementers need to consider the security considerations discussed in the [SNIFF] specification. As this specification allows for the declaration of IRIs within certain elements of a configuration documents, implementers need to consider the security considerations discussed in the [IRI] specification. Interoperability considerations: Some issues can arise with regards to character encodings of file names, the length of zip relative paths, and the use of certain strings as file names. This specification does not put a restriction on the byte length of a Zip relative path, so a user agent needs to be able to deal with Zip relative paths that have lengths longer than 250 bytes. As some operating systems have restrictions on how long a path length can be, authors need to keep the lengths of relative paths at less than 250 bytes. Unicode code points may require more than one byte to encode a character, which can result in a path whose length is less than 250 characters but whose size is greater than 250 bytes. Authors need to be aware that, at the time of publication, there are interoperability issues with regards to using characters outside the safe-chars range for file or folder names in a Zip archive when using Zipping tools bundled with operating systems. The interoperability issues have arisen from non-conforming implementations of the [ZIP] specification across operating systems: very few, if any, correctly support encoding file names in Unicode. In the case where the Zip relative path is encoded using [UTF-8], the language encoding flag (EFS) needs to be set. If an author chooses to use the utf8-chars, they need to thoroughly test their widgets on various platforms prior to distribution; otherwise it is suggested that authors restrict file and folder names to the safe-chars (characters in the US-ASCII range). In addition, having excessively long path names (e.g. over 120 characters) can also result in interoperability issues on some operating systems. Authors need to avoid using forbidden characters when naming the files used by a widget. These characters are reserved to maintain interoperability across various file systems and with [URI]s. Authors need to avoid using the following words as either a folder or a file-name in a Zip relative path as they are reserved by some operating systems (case-insensitive): CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, LPT9, CLOCKS$. For example, the following names are ok: "CON-tact.txt", "printer.lpt1", "DCOM1.pdf". However, "com3.txt" "Lpt1", "CoM9.gif" would not be. In addition, authors need to avoid having a "." U+002E FULL STOP as the last character of a file or folder name as some operating systems will remove the character when the file is extracted from the Zip archive onto the device. Furthermore, avoid having the space character (SP) at the start or end of a file name; and take caution when using the "+" U+002B PLUS SIGN, as it might cause issues on some operating systems. Published specification: http://www.w3.org/TR/widgets/ Applications that use this media type: User agents that claim conformance to this specification. Magic number(s): 50 4B 03 04 File extension(s): wgt Macintosh file type code(s): None. Person & email address to contact for further information: Steven Pemberton, member-webapps(a)w3.org Intended usage: Common. Restrictions on usage: None. Author: The W3C's Web Applications Working Group

1 0

Registration of MIME media type application/framework-attributes+xml
by Eric Burger 28 Oct '09

28 Oct '09

[Thanks to Martin... specification is at http://tools.ietf.org/id/draft-ietf-mediactrl-sip-control-framework-11 ] MIME media type name: application MIME subtype name: framework-attributes+xml Required parameters: (none) Optional parameters: Same as charset parameter application/xml as specified in RFC 3023. Encoding considerations: Same as encoding considerations of application/xml as specified in RFC 3023. Security considerations: No known security considerations outside of those provided by core Media Control Channel Framework. Interoperability considerations: This content type provides common constructs for related Media Control Channel packages. Published specification: RFC XXXX [NOTE TO IANA/RFC-EDITOR: Please replace XXXX with the RFC number for this specification.] Applications which use this media type: Implementations of appropriate Media Control Channel packages. Additional Information: Magic Number(s): (none) File extension(s): (none) Macintosh File Type Code(s): (none) Person & email address to contact for further information: Chris Boulton <chris(a)ns-technologies.com> Intended usage: LIMITED USE Author/Change controller: The IETF Other information: None.

1 0

Registration of MIME Media Type application/cfw
by Eric Burger 28 Oct '09

28 Oct '09

[Thanks to Martin... specification is at http://tools.ietf.org/id/draft-ietf-mediactrl-sip-control-framework-11 ] MIME media type name: application MIME subtype name: cfw Required parameters: None Optional parameters: None Encoding considerations: See section 4 of RFC XXXX Security considerations: See Section 12 of RFC XXXX. Interoperability considerations: Endpoint compliant to this specification must use this MIME type. Receivers who cannot support this specification will reject using appropriate protocol mechanism. Published specification: RFC XXXX Applications that use this media type: Media Control Channel compliant applications. Additional information: None Person and email address to contact for further information: Chris Boulton: chris(a)ns-technologies.com Intended usage: COMMON Restrictions on usage: Should be used only in conjunction with this specification, RFC XXXX. Author: Chris Boulton Change controller: IETF MediaCtrl working group, delegated from the IESG.

1 0

Change to Registration of media type vnd.solent.sdkm+xml
by J. Clifford Gauntlett 27 Oct '09

27 Oct '09

Name : Cliff Gauntlett Email : cliff&solenttec.net MIME media type name : Application MIME subtype name : Vendor Tree - vnd.solent.sdkm+xml Required parameters : None. Optional parameters : None. Encoding considerations : 8bit This media type may require encoding on transports not capable of handling 8 bit text. Charset UTF-8 is the only supported character set for this MIME type. Security considerations : The document contains an XML description of a variable size sudoku puzzle. The format for the document is a standard xml document which is described in the namespace "http://www.sudokumagic.co.uk/sudokumagicds.xsd". Security precautions regarding xml documents should be used although the document contains no executable code. Interoperability considerations : This file format is intended to be used by an application call SudokuMagic which is available on a variety of platforms. This program currently uses Unicode character representation. Other programs from different vendors may also use this format and interoperability issues should be discussed in the appropriate documentation for those programs. Published specification : Schema definitions are available at "http://www.sudokumagic.co.uk/sudokumagicds.xsd". The current version of the definition is 2.009.10.13001 and maybe updated from time to time. Applications which use this media : SudokuMagicWFE, SudokuMagicPPC, SudokuMagicMAC, SudokuMagicMOB, SudokuMagicSRV, SudokuMagicWS. These are the currently known applications which use the format. Additional information : 1. Magic number(s) : None. 2. File extension(s) : sdkm sdkd sdkg 3. Macintosh file type code : SDKM 4. Object Identifiers: None. None. Person to contact for further information : 1. Name : Cliff Gauntlett 2. Email : cliff&solenttec.net Intended usage : Common Author: Cliff Gauntlett Change controller : Cliff Gauntlett Web URL has been updated as well as current version numbers.

1 0

IETF Types Review: application/cfw
by Eric Burger 27 Oct '09

27 Oct '09

Please review the MIME Type application/cfw, as defined in http://tools.ietf.org/id/draft-ietf-mediactrl-sip-control-framework-11 Cross-posting to mediactrl(a)ietf.org would be greatly appreciated.

2 1

please comment on media-type registrations for MathML
by Paul Libbrecht 07 Oct '09

07 Oct '09

Dear Media-types experts, the last-call period for MathML3 has now launched and is set to end Nov 11th. See the announce at: http://www.w3.org/mid/9F0A2A05-3BCD-4E00-8B63-0DE2419CB98E@ams.org In this specification draft, one can find three registrations for media-types related to MathML in the appendix B: http://www.w3.org/TR/2009/WD-MathML3-20090924/appendixb.html They are copied below. I would love comments on them until Nov 11th. Paul B.1 Media type for Generic MathML This registration is for community review and will be submitted to the IESG for review, approval, and registration with IANA. Type name: application Subtype name: mathml+xml Required parameters: none Optional parameters: charset as per [RFC3023] Encoding considerations: same as XML as specified in [RFC3023]. Security considerations: none Interoperability considerations: entities with this media type also have the media type application/xml and may also have the media types application/presentation-mathml+xml or application/content-mathml+xml. Published specification: MathML-3, draft at: http://www.w3.org/TR/MathML3/ Applications that use this media type: (todo) Additional information Magic number(s): see [RFC3023] File extension(s): .mml Windows Clipboard Name: MathML Macintosh file type code(s) MML Macintosh Universal Type Identifier code: public.mathml conforming to public.xml Person & email address to contact for further information: World Wide Web Consortium web-human(a)w3.org Intended usage: COMMON Restrictions on usage: None Author and Change controller: The MathML specification is the product of the World Wide Web Consortium's Math Working Group. The W3C has change control over this specification. B.2 Media type for Presentation MathML This registration is for community review and will be submitted to the IESG for review, approval, and registration with IANA. Type name: application Subtype name: mathml-presentation+xml Required parameters: none Optional parameters: charset as per [RFC3023] Encoding considerations: same as XML as specified in [RFC3023]. Security considerations: none Interoperability considerations: This media type is a more specific type than application/mathml+xml. Hence any entity of this type is also of the type application/mathml+xml as well as application/xml. An agent offering this specific media type MUST also offer the application/mathml+xml media type. An agent delivering an entity of this media type SHOULD only do so if it knows the receiving party supports it, for example thanks to the Accept http header, and should otherwise deliver the more generic type. Published specification: MathML-3, draft at: http://www.w3.org/TR/MathML3/ Applications that use this media type: (todo) Additional information: Magic number(s): see [RFC3023] File extension(s): none Windows Clipboard Name: MathML Presentation Macintosh file type code(s) MMLp Macintosh Universal Type Identifier code: public.mathml.presentation conforming to public.mathml (described above) conforming to public.xml Person & email address to contact for further information: World Wide Web Consortium web-human(a)w3.org Intended usage: COMMON Restrictions on usage: None Author and Change controller The MathML specification is the product of the World Wide Web Consortium's Math Working Group. The W3C has change control over this specification. B.3 Media type for Content MathML This registration is for community review and will be submitted to the IESG for review, approval, and registration with IANA. Type name: application Subtype name: mathml-content+xml Required parameters: none Optional parameters: charset as per [RFC3023] Encoding considerations: same as XML as specified in [RFC3023]. Security considerations: none Interoperability considerations: This media type is a more specific type than application/mathml+xml. Hence any entity of this type is also of the type application/mathml+xml as well as application/xml. An agent offering this specific media type MUST also offer the application/mathml+xml media type. An agent delivering an entity of this media type SHOULD only do so if it knows the receiving party supports it, for example thanks to the Accept http header, and should otherwise deliver the more generic type. Published specification: MathML-3, draft at: http://www.w3.org/TR/MathML3/ Applications that use this media type: (todo) Additional information: Magic number(s): see [RFC3023] File extension(s): none Windows Clipboard Name: MathML Content Macintosh file type code(s): MMLc Macintosh Universal Type Identifier code: public.mathml.content conforming to public.mathml (described above) conforming to public.xml Person & email address to contact for further information: World Wide Web Consortium web-human(a)w3.org Intended usage: COMMON Restrictions on usage: None Author and Change controller: The MathML specification is the product of the World Wide Web Consortium's Math Working Group. The W3C has change control over this specification.

2 3

Registration of media type video/H264-RCDO
by Tom Kristensen 06 Oct '09

06 Oct '09

Last week we submitted a new version of draft-ietf-avt-rtp-h264-rcdo: http://tools.ietf.org/html/draft-ietf-avt-rtp-h264-rcdo-03 In this version of the draft the complete media type registration was included. The media subtype for RCDO for H.264 is allocated from the IETF tree. The media type registration is attached to this message, for convenience. Cheers, -- Tom

2 1

Re: Review of application/pkix-attr-cert Media Type
by Russ Housley 05 Oct '09

05 Oct '09

I just posted an update. Russ At 01:21 PM 10/5/2009, Bjoern Hoehrmann wrote: >* Russ Housley wrote: > >http://www.ietf.org/id/draft-ietf-pkix-attr-cert-mime-type-01.txt > > > >This document includes the application/pkix-attr-cert media type > >registration. The document is also going through WG Last Call in the > >PKIX WG. Please review. > >In the template, the "Person & email address" part does not properly >separate name and address (like is done under "Author" for example). > >File name extensions are usually given in lower case; if people are >actually to use the "AC" spelling and not "ac", that should be said >more clearly, otherwise it should say "ac" instead. > >The encoding considerations should simply say 7bit, 8bit, or one of >the other values specified in RFC 4288 section 4.8. I believe I said >as much earlier. > >Is there no pattern that could be cited in the magic number section? >-- >Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de >Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de >25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/

1 0