January 2010 - 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

Potential media type registration: application/metalink4+xml for Metalink Download Description Format
by Anthony Bryan 22 Apr '10

22 Apr '10

>From http://tools.ietf.org/html/draft-bryan-metalink application/metalink4+xml MIME type A Metalink Document, when serialized as XML 1.0, can be identified with the following media type: MIME media type name: application MIME subtype name: metalink4+xml Mandatory parameters: None. Optional parameters: "charset": This parameter has semantics identical to the charset parameter of the "application/xml" media type as specified in [RFC3023]. Encoding considerations: Identical to those of "application/xml" as described in [RFC3023], Section 3.2. Security considerations: As defined in this specification. In addition, as this media type uses the "+xml" convention, it shares the same security considerations as described in [RFC3023], Section 10. Interoperability considerations: There are no known interoperability issues. Published specification: This specification. Applications that use this media type: No known applications currently use this media type. Additional information: Magic number(s): As specified for "application/xml" in [RFC3023], Section 3.2. File extension: .meta4 Fragment identifiers: As specified for "application/xml" in [RFC3023], Section 5. Base URI: As specified in [RFC3023], Section 6. Macintosh File Type code: TEXT Person and email address to contact for further information: Anthony Bryan <anthonybryan(a)gmail.com> Intended usage: COMMON Author/Change controller: IESG thank you, -- (( Anthony Bryan ... Metalink [ http://www.metalinker.org ] )) Easier, More Reliable, Self Healing Downloads

2 2

Registration of media type application/its+xml
by Felix Sasaki 21 Apr '10

21 Apr '10

MIME media type name: application MIME subtype name: its+xml Required parameters: none Optional parameters: charset This parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in IETF RFC 3023. Encoding considerations: Identical to those of "application/xml" as described in IETF RFC 3023, section 3.2, as applied to an ITS document. Security considerations: An ITS 1.0 document may cause arbitrary URIs or IRIs to be dereferenced, via the @xlink:href attribute at the its:rules element. Therefore, the security issues of [RFC3987] Section 8 should be considered. In addition, the contents of resources identified by file: URIs can in some cases be accessed, processed and returned as results. An implementation of ITS global rules requires the support of XPath 1.0 or its successor. Hence, processing of global rules might encompass dereferencing of URIs or IRIs during computation of XPath expressions. Arbitrary recursion is possible, as is arbitrarily large memory usage, and implementations may place limits on CPU and memory usage, as well as restricting access to system-defined functions. ITS 1.0 permits extensions. Hence it is possible that application/its+xml may describe content that has security implications beyond those described here. Interoperability considerations: There are no known interoperability issues. Published specifications: http://www.w3.org/TR/2007/REC-its-20070403/ Applications which use this media type: This new media type is being registered to allow for deployment of ITS 1.0 on the World Wide Web. Additional information: File extension: its Fragment identifiers: A syntax identical to that of "application/xml" as described in IETF RFC 3023. Base URI: As specified in IETF RFC 3023, section 6. Macintosh File Type code: TEXT Person and email address to contact for further information: World Wide Web Consortium <web-human(a)w3.org> Intended usage: COMMON Author/Change controller: The Internationalization Tag Set (ITS) 1.0 specification set is a work product of the World Wide Web Consortium's Internationalization Tag Set Working Group. The W3C has change control over this specification.

2 1

Registration of media type application/iptv_rtsp
by Miguel Angel Reina Ortega 21 Jan '10

21 Jan '10

Type name: application Subtype name: Standards tree - iptv_rtsp Required parameters: No parameters Optional parameters: No parameters Encoding considerations: 8 bit text (this media type may require encoding on transports not capable of handling 8 bit text) The iptv_rtsp media type is intended to be a media descriptor for an RTSP content control channel. The encoding of the RTSP protocol is specified in RFC 2326 - Real Time Streaming Protocol (RTSP). Security considerations: The same security considerations apply as for the RTSP protocol, which is specified in RFC 2326 - Real Time Streaming Protocol (RTSP). Interoperability considerations: Interoperability of the RTSP protocol is specified in RFC 2326 - Real Time Streaming Protocol (RTSP). Published specification: ETSI TS 183 063 v2.4.2 (2009-06). Available at http://pda.etsi.org/pda/queryform.asp Applications that use this media type: The iptv_rtsp media type is intended to be a media descriptor for an RTSP content control channel. An RTSP content control channel is established using SIP and the SDP offer/answer model as described in ETSI TS 183 063 Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); IMS-based IPTV Stage 3 Specification", ETSI TS 183 063 v2.4.2 (2009-06). Additional information: Magic number(s): There is no single string that is always present. File extension(s): No specific file extension is recommended for this type. Macintosh file type code(s): No specific Macintosh file type codes are recommended for this type. Person & email address to contact for further information: MiguelAngel.ReinaOrtega(a)etsi.org<mailto:MiguelAngel.ReinaOrtega@etsi.org> on behalf of ETSI Intended usage: COMMON Restrictions on usage: No restrictions apply. Authors: the rapporteur (zhouzhipeng <zhouzp(a)HUAWEI.COM<mailto:zhouzp@HUAWEI.COM>>) The WG chairman (Raymond.forbes(a)ericsson.com<mailto:Raymond.forbes@ericsson.com>) Change controller: the ETSI TO (sonia.compans(a)etsi.org<mailto:sonia.compans@etsi.org>) ------------------------------------------- Miguel A. Reina Ortega Technical Expert Centre for Testing and Interoperability (CTI) tel: +33 (0)4 92 94 43 49 mob: +33 (0)6 76 73 60 99 web: http://www.etsi.org<http://www.etsi.org/>

2 1

Media type review for audio/fwdred
by Tom Taylor 05 Jan '10

05 Jan '10

The AVT Working Group requests media type review for registration of media type audio/fwdred. The documentation is in draft-ietf-avt-forward-shifted-red-03.txt, which is in WG Last Call. We would be grateful if any comments could be received by January 18. Tom Taylor AVT Co-Chair

1 0