- Ietf-types - alvestrand.no

Server downtime
by Harald Tveit Alvestrand 13 Jun '08

13 Jun '08

Hello, due to a hard disk crash, the server hosting these 3 IETF lists (among other things) has been unavailable for more than 24 hours, starting June 12 around 0300 GMT. It has now been restored from backup, and the hardware replaced, but unfortunately I cannot guarantee that no mail was lost in the crash. Please check that mail you have sent has arrived safely in the archives of the list, and feel free to ask for a resend if you see replies to recent mails you don't think you've seen. The system now appears to be normal on the mail side, but the web side is still not recovered. Harald Alvestrand

1 0

[Fwd: Last Call: draft-goncalves-rfc3534bis (Ogg Media Types) to Proposed Standard]
by Magnus Westerlund 10 Jun '08

10 Jun '08

Hi, This IETF last call is for a document that is a updated media type registration. Please review within the IETF last call period. Thanks Magnus Westerlund IETF Transport Area Director & TSVWG Chair ---------------------------------------------------------------------- Multimedia Technologies, Ericsson Research EAB/TVM ---------------------------------------------------------------------- Ericsson AB | Phone +46 8 4048287 Färögatan 6 | Fax +46 8 7575550 S-164 80 Stockholm, Sweden | mailto: magnus.westerlund(a)ericsson.com ----------------------------------------------------------------------

2 1

Re: Re: Registration of media type FO and ZFO
by Jakub Hytka 10 Jun '08

10 Jun '08

Thanks for the suggestions Frank. I added some information under published specification to describe both media types. We still want to keep the vnd.software602.filler.xml+form and vnd.software602.filler.xml+zip+form subtypes, because they are highly descriptive in our opinion. Is this a important issue to be considered? Here follows the updated registration proposal: ------------------------------------------------------ ---FO--- Type name: application Subtype name: Vendor Tree - vnd.software602.filler.xml+form Required parameters: None Optional parameters: None Encoding considerations: UTF-8 Security considerations: FO is a XML-based plain text format, secured by signing the file itself through the means of the XML Signature standard. Interoperability considerations: There are no special interoperability issues. Published specification: Software602 distinguishes the FO file as a XML data file containing an electronic form intended for usage in the 602XML applications. The form is a composure of the layout structure using XSL-FO, data instance and data model using generic XML elements defined in the 602XML framework. The whole electornic form structure is always embedded into a digital signature represented by XML elements of the XML Signature standard Applications that use this media type: The FO file is used by the Software602 602XML applications - 602XML Filler, 602XML Designer, 602XML Designer Express and 602XML FormServer Additional information: Magic number(s): NONE File extension(s): FO Macintosh file type code(s): - Person & email address to contact for further information: Jakub Hytka, hytka(a)602.cz, Martin Vondrous, vondrous(a)602.cz <mailto:vondrous@602.cz> Intended usage: Common Restrictions on usage: None Author: Jakub Hytka Change controller: Jakub Hytka, Martin Vondrous ---ZFO--- Type name: application Subtype name: Vendor Tree - vnd.software602.filler.xml+zip+form Required parameters: None Optional parameters: None Encoding considerations: UTF-8 Security considerations: ZFO is a XML-based plain text format packed using the ZIP archive algorithms. The XML content is secured by signing the file itself through the means of the XML Signature standard. The ZIP file itself can be protected in the usual way by setting up a password. Interoperability considerations: There are no special interoperability issues. Published specification: Software602 distinguishes the ZFO file as a ZIP archive file containing the FO electronic form. The FO electronic form is a XML data file containing an electronic form intended for usage in the 602XML applications. The form is a composure of the layout structure using XSL-FO, data instance and data model using generic XML elements defined in the 602XML framework. The whole electornic form structure is always embedded into a digital signature represented by XML elements of the XML Signature standard Applications that use this media type: The ZFO file is used by the Software602 602XML applications - 602XML Filler, 602XML Designer, 602XML Designer Express and 602XML FormServer Additional information: Magic number(s): NONE File extension(s): FO Macintosh file type code(s): - Person & email address to contact for further information: Jakub Hytka, hytka(a)602.cz, Martin Vondrous, vondrous(a)602.cz <mailto:vondrous@602.cz> Intended usage: Common Restrictions on usage: None Author: Jakub Hytka Change controller: Jakub Hytka, Martin Vondrous ---------------------------------------------------------------- Jakub

3 4

Re: Registration of media type FO and ZFO
by Martin Duerst 10 Jun '08

10 Jun '08

At 03:01 08/06/10, Bjoern Hoehrmann wrote: >* Jakub Hytka wrote: >>Thanks for the suggestions Frank. I added some information under >>published specification to describe both media types. >>We still want to keep the vnd.software602.filler.xml+form and >>vnd.software602.filler.xml+zip+form subtypes, because they are highly >>descriptive in our opinion. Is this a important issue to be considered? >> >>Here follows the updated registration proposal: >> >>------------------------------------------------------ >>---FO--- >> >> Type name: application >> >> Subtype name: Vendor Tree - vnd.software602.filler.xml+form >> >> Required parameters: None >> >> Optional parameters: None >> >> Encoding considerations: UTF-8 >> >> Security considerations: FO is a XML-based plain text format, secured >>by signing the file itself through the means of the XML Signature standard. > >See RFC 4288 on the possible values for the Encoding considerations. I >am not sure what kind of format you have. Could application/xml also be >used instead of vnd.software602.filler.xml+form, i.e., are these simply >XML documents with a special type, or is there some special encoding >that makes them non-XML without additional decoding? If they are XML, >then I would advise to reference RFC 3023 for encoding considerations, >and add the optional 'charset' parameter, and consider calling the type >e.g. vnd.software602.filler.form+xml. Very much so indeed. The current subtype name is highly unclear, and if it's indeed XML, then +xml should be last. "because they are highly descriptive" is really a non-starter. The +xml suffix is highly descriptive, the +form 'suffix' is completely undefined. Regards, Martin >By the way, your first message in this thread sounded like this is not >the first time you send the proposal, if that is so, please note that I >could not find a previous message from you in the archive. > >> Additional information: >> >> Magic number(s): NONE >> File extension(s): FO >> Macintosh file type code(s): - > >I would advise against using this extension, I believe it is in common >use for XSL FO already. > >> Type name: application >> Subtype name: Vendor Tree - vnd.software602.filler.xml+zip+form >> Required parameters: None >> Optional parameters: None >> Encoding considerations: UTF-8 > >Please see above for the encoding considerations. Perhaps you should re- >fer to the application/zip registration here. > >> Additional information: >> >> Magic number(s): NONE >> File extension(s): FO >> Macintosh file type code(s): - > >Same as above. >-- >Bj$B�S(Bn H$B�I(Brmann $B%-(B mailto:bjoern@hoehrmann.de $B%-(B http://bjoern.hoehrmann.de >Weinh. Str. 22 $B%-(B Telefon: +49(0)621/4309674 $B%-(B http://www.bjoernsworld.de >68309 Mannheim $B%-(B PGP Pub. KeyID: 0xA4357E78 $B%-(B http://www.websitedev.de/ #-#-# Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University #-#-# http://www.sw.it.aoyama.ac.jp mailto:duerst@it.aoyama.ac.jp

2 1

Registration of media type FO and ZFO
by Jakub Hytka 10 Jun '08

10 Jun '08

Hello, I wanted to ask you whether there is any progress or comment on our registration proposal. Thank you in advance for you reply. Best regards, Jakub Hytka Product manager Software602 a.s. TEL: 222 011 296, 222 011 602 FAX: 222 011 218 hytka(a)602.cz http://www.602.cz ------------------------------------------------------------------------------------ Our company would like to apply for registration of two media types into the VENDOR tree. These two media types are bound with media files with the .fo and .zfo extensions - both files representing e-forms used by the 602XML technology. ---FO--- Type name: application Subtype name: Vendor Tree - vnd.software602.filler.xml+form Required parameters: None Optional parameters: None Encoding considerations: UTF-8 Security considerations: FO is a XML-based plain text format, secured by signing the file itself through the means of the XML Signature standard. Interoperability considerations: There are no special interoperability issues. Published specification: Not available yet. Applications that use this media type: The FO file is used by the Software602 602XML applications - 602XML Filler, 602XML Designer, 602XML Designer Express and 602XML FormServer Additional information: Magic number(s): NONE File extension(s): FO Macintosh file type code(s): - Person & email address to contact for further information: Jakub Hytka, hytka(a)602.cz Intended usage: Common Restrictions on usage: None Author: Jakub Hytka Change controller: Jakub Hytka ---ZFO--- Type name: application Subtype name: Vendor Tree - vnd.software602.filler.xml+zip+form Required parameters: None Optional parameters: None Encoding considerations: UTF-8 Security considerations: ZFO is a XML-based plain text format packed using the ZIP archive algorithms. The XML content is secured by signing the file itself through the means of the XML Signature standard. The ZIP file itself can be protected in the usual way by setting up a password. Interoperability considerations: There are no special interoperability issues. Published specification: Not available yet. Applications that use this media type: The ZFO file is used by the Software602 602XML applications - 602XML Filler, 602XML Designer, 602XML Designer Express and 602XML FormServer Additional information: Magic number(s): NONE File extension(s): FO Macintosh file type code(s): - Person & email address to contact for further information: Jakub Hytka, hytka(a)602.cz Intended usage: Common Restrictions on usage: None Author: Jakub Hytka Change controller: Jakub Hytka Best regards, Jakub Hytka Product manager Software602 a.s. TEL: 222 011 296, 222 011 602 FAX: 222 011 218 hytka(a)602.cz http://www.602.cz

3 3

Request review: draft-ietf-avt-rfc4749-dtx-update-01.txt
by Colin Perkins 04 Jun '08

04 Jun '08

The AVT working group requests review for the updated audio/g7291 media type defined in draft-ietf-avt-rfc4749-dtx-update-01.txt. This draft updates the media type registration with a new parameter to signal the use of DTX frames (G.729.1 Annex C), and also specifies how this format is framed for use with RTP. This draft is currently in working group last call, so we would be grateful if comments could be made by 20 June 2008. Thanks, Colin (AVT co-chair)

1 0

review of audio media subtypes PCMA-WB and PCMU-WB
by Even, Roni 07 May '08

07 May '08

Hi, The AVT working group requests media type review for the audio/PCMA-WB and audio/PCMU-WB media subtypes defined in section 5.1 and 5.2 of http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-g711wb-03.txt This draft is currently in AVT working group last call. We would be grateful if any comments could be made by May 27th, 2008. Thanks, Roni Even (AVT co-chair)

1 0

review of application held+xml type
by Cullen Jennings 28 Apr '08

28 Apr '08

Could folks please review the type defined in http://tools.ietf.org/html/draft-ietf-geopriv-http-location-delivery-07 and sends comments before May 18th. Thanks, Cullen

4 3

review of audio media subtype UEMCLIP
by Even, Roni 07 Apr '08

07 Apr '08

Hi, The AVT working group requests media type review for the audio/UEMCLIP media subtype defined in section 6.1 of http://tools.ietf.org/html/draft-ietf-avt-rtp-uemclip-04 . This draft is currently in AVT working group last call. We would be grateful if any comments could be made by 21 March 2008. Thanks, Roni Even (AVT co-chair)

3 2

Review request of media type application/richmediacommand+xml
by Torkel Hambraeus 01 Apr '08

01 Apr '08

Please review the following media type registration. Type name: application Subtype name: richmediacommand+xml Required parameters: none Optional parameters: charset useFullRequestHost pathComponents Encoding considerations: Same as for application/xml. See [7]RFC3023 , section 3.2. Security considerations: The media type defines update commands to data viewed by an end user. Updates from an mallicious source can performe harmful changes to the image viewed by the end user. A specific form of updates consists of scripts executed by the reciever of the media type. If the scripting language so permitts access to data can be given allowing this data to be disclosed to unintended parties. It is allso possible for content to surge computational and memory resources from the reciever. Interoperability considerations: none Published specification: OMA Rich Media Enabler Technical Specification The latest version of the specification can be found at: http://member.openmobilealliance.org/ftp/public_documents/bt/MAE/Permanent_… Applications that use this media type: Applications implementing the Rich Media Enable Technical Specification. Typically these are rich media environments on mobile devices. Additional information: Magic number(s): None File extension(s): scg Macintosh file type code(s): None Person & email address to contact for further information: torkel.hambraeus(a)ikivo.com Intended usage: COMMON Restrictions on usage: none Author: The author of this specification is the Open Mobile Alliance working group Browsers Technology. See http://www.openmobilealliance.org/Technical/browser_technologies.aspx. Change controller: Change control of this specificaiton is done by Open Mobile Alliance working group Browsers Technology. See http://www.openmobilealliance.org/Technical/browser_technologies.aspx. Torkel Hambraeus Senior Technical Lead ________________________________________________ Ikivo AB Östermalmsgatan 87 C SE-114 59 Stockholm Sweden Email: torkel.hambraeus(a)ikivo.com <mailto:torkel.hambraeus@ikivo.com> http://www.ikivo.com <http://www.ikivo.com/> The information transmitted in this email and any attachment(s) is intended solely for the addressee(s) and may contain confidential, proprietary or privileged material. Any review, retransmission, dissemination, reproduction, disclosure, reliance upon or any other use of this information by persons or entities other than the intended recipient(s) is strictly prohibited. If you received this email in error, please notify the sender and delete all related material forthwith.

2 2