August 2010 - Ietf-types

Re: Standards tree image/ktx mime registration for review
by Mark Callow 07 Sep '10

07 Sep '10

To: Whom It May Concern: I sent the following messages on July 26th and July 22nd. I have had no response. I am going to assume this to mean the IETF has no objections to the proposed registration. If I do not hear anything to the contrary by Mon. August 23rd 2PM PDT, I am going to submit the registration to the IESG. Regards -Mark On 2010/07/26 20:58, Mark Callow wrote: > To Whom It May Concern: > > I sent the following message on July 22nd. The only response I have > received is an automated message telling me my message was awaiting > the moderator's review because I am not a list member. > > How long does a review typically take? > > Note the KTX home page listed in the registration template will change > during the next 24 hours to > > http://www.khronos.org/opengles/sdk/tools/KTX > > and the specification will be at > > http://www.khronos.org/opengles/sdk/tools/KTX/file-format-spec/ > > Regards > > -Mark > > On 2010/07/22 2:17, Mark Callow wrote: >> >> To Whom It May Concern: >> >> Attached is a registration template for a new image/ktx mime-type >> sent on behalf of the Khronos Group <http://www.khronos.org>. I >> understand the procedure is first for this list to review the >> template and, after it is final, to send it to iesg(a)ietf.org. >> >> Regards >> >> -Mark >> >> >> >> >

2 5

Registration of ttml+xml
by Philippe Le Hegaret 29 Aug '10

29 Aug '10

This new registration replaces the registration for ttaf+xml. [[ MIME media type name: application MIME subtype name: ttml+xml Required parameters: None. Optional parameters: charset Same as application/xml media type, as specified in [XML Media Types] or its successors. profile The document profile of a TTML 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 6.2.8 ttp:profile of the published specification. Encoding considerations: Same for application/xml. See [XML Media], Section 3.2. Restrictions on usage: None. Security considerations: As with other XML types and as noted in [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 TTML and of XML in general, it is possible that "application/ttml+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 TTML 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 TTML namespaces and in other namespaces. Because TTML is extensible, conformant "application/ttml+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 C Media Type Registration of the Timed Text Markup Language (TTML) 1.0 specification. Additional information: Magic number(s): File extension(s): ttml Macintosh file type code(s): "TTML" Person & email address to contact for further information: Timed Text Working Group (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. ]] -- Philippe Le Hégaret, W3C Interaction Domain Leader http://www.w3.org/People/LeHegaret

2 2

Registration of media type text/vcard
by Simon Perreault 28 Aug '10

28 Aug '10

Type name: text Subtype name: vcard Required parameters: none Optional parameters: version The "version" parameter is to be interpreted identically as the VERSION vCard property. If this parameter is present, all vCards in a text/vcard body part MUST have a VERSION property with value identical to that of this MIME parameter. Encoding considerations: The "charset" MIME parameter, if present, MUST be set to "UTF-8", as defined in [RFC3629]. Security considerations: See Section 9. Interoperability considerations: The text/vcard media type is intended to identify vCard data of any version. There are older specifications of vCard [RFC2426][oldreference_VCARD] still in common use. While these formats are similar, they are not strictly compatible. In general, it is necessary to inspect the value of the VERSION property (see Section 6.7.9) for identifying the standard to which a given vCard object conforms. In addition, the following media types are known to have been used to refer to vCard data. They should be considered deprecated in favor of text/vcard. * text/directory * text/directory; profile=vcard * text/x-vcard Published specification: draft-ietf-vcarddav-vcardrev-13 Applications that use this media type: They are numerous, diverse, and include mail user agents, instant messaging clients, address book applications, directory servers, customer relationship management software, etc. Additional information: Magic number(s): File extension(s): .vcf Macintosh file type code(s): Person & email address to contact for further information: Simon Perreault <simon.perreault(a)viagenie.ca> Intended usage: COMMON Restrictions on usage: none Author: Simon Perreault and Pete Resnick Change controller: IETF -- NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca STUN/TURN server --> http://numb.viagenie.ca vCard 4.0 --> http://www.vcarddav.org

5 4

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

27 Aug '10

On Thu, 2010-08-26 at 17:44 -0700, David Singer wrote: > I would leave the Mac file type code blank, myself. Or make it a text document (which it is). We no longer register these, afaik, so... Hi David, as far as I know, RFC 4288 indicates: [[ 4.11. Additional Information Various sorts of optional information SHOULD be included in the specification of a media type if it is available: [...] o File name extension(s) commonly used on one or more platforms to indicate that some file contains a given media type. o Mac OS File Type code(s) (4 octets) used to label files containing a given media type. ]] http://www.ietf.org/rfc/rfc4288.txt So, I don't mind one way or another, but it seems to me RFC 4288 needs to be updated if we're going to drop the usage. Philippe

3 2

Re: Registration of media type text/vcard
by Simon Perreault 26 Aug '10

26 Aug '10

On 2010-08-25 11:48, Paul Libbrecht wrote: > What is the advantage of having a charset parameter? You mean for vCard 4 or for MIME? For vCard 4, we felt that MIME came with a charset parameter and we had no power to way "this parameter MUST NOT not be applied to vCard 4". That's why we say instead that if it is used, then it MUST say UTF-8. > From your registration the parameter brings no information (am I > right?). So why include it and not simply rely on the Byte-Order-Mark? vCard 4 does not use a BOM. vCard 4 is always UTF-8, period. We do not wish to "include" the charset parameter. If it is possible to "exclude" it, that would make us happy. Simon -- NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca STUN/TURN server --> http://numb.viagenie.ca vCard 4.0 --> http://www.vcarddav.org

4 7

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

26 Aug '10

On Thu, 2010-08-26 at 22:11 +0200, Paul Libbrecht wrote: > Could I suggest you follow another enhancement Chris Lilley has > followed as visible in: > > http://dev.w3.org/SVG/profiles/1.1F2/publish/mimereg.html > > Namely the addition of clipboard names (Mac´s UTI and Windows flavor > names). How about: Macintosh Universal Type Identifier code: org.w3c.ttml conforms to public.xml Windows Clipboard Name: "Timed Text Document" Philippe

2 1

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

[admin] message backlog
by Mark Baker 04 Aug '10

04 Aug '10

Hello everyone, I apologize, but it seems that sometime in April I stopped receiving notifications from mailman about messages requiring approval. Unfortunately I didn't notice this until today, when I received a bounce notification. Luckily there were only 4 non-spam messages in the queue, which I will dispatch momentarily. I will immediately investigate why I stopped receiving these notifications. Thanks for your understanding, and again, my apologies. Mark.

1 0