- Ietf-types - example.com

Request for comments for Media Type registration of application/ccxml+xml
by RJ Auburn 28 Jul '04

28 Jul '04

*This message was transferred with a trial version of CommuniGate(tm) Pro* This is a request for comments on the registration of the application/ccxml+xml mime type. The request is published as part of the CCXML 1.0 specification and is copied below. The url of the request is: http://www.w3.org/TR/ccxml/#ccxml-mime-definition Please send any comments on this request to rj(a)voxeo.com Thanks, RJ Appendix I - CCXML Media Type This appendix registers a new MIME media type, "application/ccxml+xml". I.1 Registration of MIME media type application/ccxml+xml MIME media type name: application MIME subtype name: ccxml+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 [RFC3023]. Encoding considerations: By virtue of CCXML content being XML, it has the same considerations when sent as "application/ccxml+xml" as does XML. See RFC 3023, section 3.2. Security considerations: Several CCXML instructions may cause arbitrary URIs to be referenced. In this case, the security issues of RFC1738, section 6, should be considered. In addition, because of the extensibility features for CCXML, it is possible that "application/ccxml+xml" may describe content that has security implications beyond those described here. However, if the processor follows only the normative semantics of this specification, this content will 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: This specification describes processing semantics that dictate behavior that must be followed when dealing with, among other things, unrecognized elements. Because CCXML is extensible, conferment "application/ccxml+xml" processors can expect that content received is well-formed XML, but it cannot be guaranteed that the content is valid CCXML or that the processor will recognize all of the elements and attributes in the document. Published specification: This media type registration is for CCXML documents as described by this specification. Additional information: Magic number(s): There is no single initial octet sequence that is always present in CCXML documents. File extension(s): CCXML documents are most often identified with the extensions ".ccxml". Macintosh File Type Code(s): TEXT Person & email address to contact for further information: RJ Auburn, <rj(a)voxeo.com>. Intended usage: COMMON Author/Change controller: The CCXML specification is a work product of the World Wide Web Consortium's Voice Browser Working Group. The W3C has change control over these specifications.

6 9

RE: Request for comments for Media Type registration of applicati on/ccxml+xml
by Biot Olivier 28 Jul '04

28 Jul '04

|From: RJ Auburn | | |Chris: | |Comments and replies are inline. Let me know if there are any |other issues: | | |On 07/22/2004 11:05, Chris Lilley wrote: [...] |> When citing an RFC abcd, it is useful to do a Google search for |> "Obsoletes: abcd" and "Updates: abcd" because RFCs do not |have 'latest |> version' URIs (or indeed canonical URIs at all). | |Thanks for the tip... You get this information "for free" if you head to the RFC Editor (http://www.rfc-editor.org/) choose "RFC Search" and type your RFC number in the query form. You even get a list of known errata if applicable. Best regards, Olivier Biot

1 0

Request for MIME media type Application/Vendor Tree - vnd.3gpp.sm s-tl
by Biot Olivier 28 Jul '04

28 Jul '04

[NOTE: this is the registration email as returned to me on the 14th of July from the IANA registration perl script] Name : Olivier Biot Email : olivier.biot(a)siemens.com MIME media type name : Application MIME subtype name : Vendor Tree - vnd.3gpp.sms-tl Required parameters : none Optional parameters : none Encoding considerations : binary This media type may require encoding on transports not capable of handling binary. Security considerations : The Short Messaging Service Transfer Layer (SMS-TL) format may contain executable code and user confidential information. Interoperability considerations : The SMS-TL MIME type allows transport interoperability between the Short Messaging Service (SMS) and other messaging systems supporting SMS-TL, and some transport layer independence for transporting an SMS message. Published specification : ETSI TS 123 040 available at http://pda.etsi.org/pda/queryform.asp (transposition of 3GPP TS 23.040 available at http://www.3gpp.org/ftp/Specs/archive/) Applications which use this media : Applications that transport and manipulate MIME typed objects (messaging, download etc.). Additional information : 1. Magic number(s) : n/a 2. File extension(s) : .sms-tl 3. Macintosh file type code : n/a 4. Object Identifiers: n/a Person to contact for further information : 1. Name : Olivier Biot 2. Email : olivier.biot(a)siemens.com Intended usage : Common The Short Messaging Service is a very common messaging service available on most mobile networks. The registration of the associated MIME type allows a SMS message to be delivered independent of the transport network. Author/Change controller : Olivier Biot

4 3

RE: Request for MIME media type Application/Vendor Tree - vnd.3gp p.sm s-tl
by Biot Olivier 27 Jul '04

27 Jul '04

Hello Ned, Thanks for the review remarks! See comments in-line. |-----Original Message----- |From: Ned Freed | | |A couple of points in addition to the ones Larry already made... | |> [NOTE: this is the registration email as returned to me on |the 14th of July |> from the IANA registration perl script] | |> Name : Olivier Biot | |> Email : olivier.biot(a)siemens.com | |> MIME media type name : Application | |> MIME subtype name : Vendor Tree - vnd.3gpp.sms-tl | |> Required parameters : none | |> Optional parameters : |> none | |> Encoding considerations : binary |> This media type may require encoding on transports not |> capable of handling binary. | |> Security considerations : |> The Short Messaging Service Transfer Layer (SMS-TL) format |> may contain |> executable code and user confidential information. | |There's also the issue of data integrity. Would someone |tweaking this stuff |in transit be able to cause any problems? I assume the answer |is "yes" since executable code can be involved. This is correct. Changing bits of bytes within the data do compromise the message. I thought data integrity was beyond the scope of registering a MIME media type, but I'll now add a note. |There's also the issue of what, if anything, is done to prevent |tampering or leakage. Is there a preferred mechanism for adding |integrity/confidentiality services on top of this media type? Or does |the type itself include facilities for this? Normally the GSM SMS-TL traffic runs in a protected environment (carrier network), where confidentiality is a key element. Hence I did not really look at this aspect. Secure MIME, TLS, and signing are obvious means for providing (relatively) tamper-proof solutions. I will issue a new assignment proposal with the comments I received so far. Many thanks for taking the time to review! Best regards, Olivier

1 0

RE: Request for MIME media type Application/Vendor Tree - vnd.3gp p.sms-tl
by Biot Olivier 27 Jul '04

27 Jul '04

Hello Larry, Thanks a lot for your review! I provided answers in-line. |-----Original Message----- |From: Larry Masinter | | |Since this is a vendor-tree media type, review is optional. |However, here are some review comments: | | |> Published specification : |> ETSI TS 123 040 available at |> (transposition of 3GPP TS 23.040 available at |> http://www.3gpp.org/ftp/Specs/archive/) | |I had trouble finding the document using this reference. |I put "ETSI TS 123 040" into the form at |http://pda.etsi.org/pda/queryform.asp |and got another query form. | |and http://www.3gpp.org/ftp/Specs/archive/ leads |you down to |http://www.3gpp.org/ftp/Specs/archive/23_series/23.040/ |which then has 20-30 zip files, but not much clue |as to which one would contain the definition of the |MIME type. Aplologies for this. I used another 3GPP MIME media type registration as an example, tested the hyperlinks and could find the documents. It is true that for people not familiar with those specs this is somehow cumbersome. Anyway, the 3GPP specs consist of several "stages", so the entire directory in http://www.3gpp.org/ftp/Specs/archive/23_series/23.040/ is relevant. You should have sufficient information if you read 23040-600.zip: it contains 3GPP TS 23.040 V6.0.0 (2002-09) Technical Specification 3rd Generation Partnership Project; Technical Specification Group Terminals; Technical realization of the Short Message Service (SMS); (Release 6) |Do you mean 'translation' instead of 'transposition'? |I'm not sure what it means to have a 'transposition' of |a document. I have taken that text from the same registration example. Both the 3GPP and ETSI document are somehow linked. The ETSI document is based on the 3GPP document. I suppose the verb "transpose" in English does not correspond fully with the verb "transposer" in French which I suppose was intended. In this situation "transpose" means "rewrite in terms of ETSI", as far as I understand. |> Applications which use this media : |> Applications that transport and manipulate MIME typed objects |> (messaging, download etc.). |> |> |> Additional information : |> |> 1. Magic number(s) : n/a |> 2. File extension(s) : .sms-tl |> 3. Macintosh file type code : n/a |> 4. Object Identifiers: n/a NOTE: this media type is not intended for file storage. It has to be seen as something like a SOAP message. Maybe the file extension should also be "n/a" hence. |> Person to contact for further information : |> |> 1. Name : Olivier Biot |> 2. Email : olivier.biot(a)siemens.com |> |> Intended usage : Common |> The Short Messaging Service is a very common messaging |> service available on most mobile networks. |> The registration of the associated MIME type allows a SMS |> message to be |> delivered independent of the transport network. | |Currently, SMS <-> EMail gateways work by translating |to/from text/plain. This works pretty well. Is the |intention to gateway into this MIME type? It would |seem that interoperability might suffer. It is more than the well-known textual SMS body. There are many applications of non-text SMS messages, such as EMS extensions and WAP Push. In order to be interoperable for these, it makes sense to use the 3GPP SMS-TL as an envelope which you can type and send over a MIME friendly transport where a Content-Type header identifies the data type. |> Author/Change controller : Olivier Biot | |If this is really 'vnd.3gpp' and not 'vnd.oliver-biot', |wouldn't the 'change controller' be the 3GPP committee? I again used existing 3GPP registrations as an example, and I did not see "The 3GPP" as applicant. However, as the media type really represents something from 3GPP, it wouldn't make sense *not* putting it in the 3GPP vendor tree. I also consulted some of our 3GPP/IETF representatives and they told me the most important was to comply with the MIME registration procedure as published in the MIME IETF standards (which hopefully I did). (I think I should have to use the "prs." vanity tree if I wanted to register it as/for myself.) Many thanks for taking the time to review! Best regards, Olivier

1 0

MIME media type registration does not appear?
by Biot Olivier 27 Jul '04

27 Jul '04

Hi list, It looks like the MIME media type registration form at IANA does not work, as I can't find any trace of a registration I posted on the 14th of July (not even with Google). I guess this is the mailing list for discussing new MIME media type registrations. If not, please let me know. Should I post the message generated by the registration script to this list? Best regards, Olivier Biot

2 1

Submission of the application/soap_xop+xml Media Mype
by Yves Lafon 21 Jul '04

21 Jul '04

All, The media type is defined in the W3C Last Call Working Draft of "SOAP Message Transmission Optimization Mechanism" [1] Below is a full text version for convenience. [2] Please direct comments to xmlp-comments(a)w3.org. Best regards, [1] http://www.w3.org/TR/soap12-mtom/#media_type [2] A The application/soap_xop+xml Media Type A.1 Introduction SOAP version 1.2 ([SOAP Part 1] and [SOAP Part 2]) is a lightweight protocol intended for exchange of structured information between peers in a decentralized, distributed environment. It defines an extensible messaging framework that contains a message construct based on XML technologies that can be exchanged over a variety of underlying protocols. The XML-binary Optimized Packaging Mechanism [XOP] is an alternate serialization of the XML Infoset, intended to make processing and representation of certain types of content (specifically, that which is base64-encoded) more efficient. Such serializations, when free-standing, are called XOP Packages; the portion of the XOP Package that represents the structure and non-optimized content of the Infoset are called XOP Documents, and are serialized as XML. This appendix defines the media type application/soap_xop+xml which can be used to identify SOAP 1.2 message envelopes that have been serialized as XOP Documents using XML 1.0 ([XML 1.0]). The application/soap_xop+xml media type explicitly identifies the XOP Document portion of a SOAP 1.2 message envelope, serialized as XML 1.0. In other words, it identifies the serialized XML after the extraction of any content into the XOP Package; it does not identify the package itself. XOP Documents not serialized as XML 1.0 or representing message envelopes with a different SOAP namespace version MUST NOT use it. A.2 Registration * MIME media type name: application. * MIME subtype name: soap_xop+xml * Required parameters: none * Optional parameters: o "charset": This parameter has identical semantics to the charset parameter of the application/xml media type as specified in RFC 3023 [RFC 3023]. o "action": This optional parameter can be used to specify the URI that identifies the intent of the message. In SOAP 1.2, it serves a similar purpose as the SOAPAction HTTP header field did in SOAP 1.1. Namely, its value identifies the intent of the message. The value of the action parameter is an absolute URI-reference as defined by RFC 2396 [RFC 2396]. SOAP places no restrictions on the specificity of the URI or that it is resolvable. Although the purpose of the action parameter is to indicate the intent of the SOAP message there is no mechanism for automatically computing the value based on the SOAP envelope. In other words, the value has to be determined out of band. It is recommended that the same value be used to identify sets of message types that are logically connected in some manner, for example part of the same "service". It is strongly RECOMMENDED that the URI be globally unique and stable over time. The presence and content of the action parameter MAY be used by servers such as firewalls to appropriately filter SOAP messages and it may be used by servers to facilitate dispatching of SOAP messages to internal message handlers etc. It SHOULD NOT be used as an insecure form of access authorization. Use of the action parameter is OPTIONAL. SOAP Receivers MAY use it as a hint to optimize processing, but SHOULD NOT require its presence in order to operate. * Encoding considerations: Identical to those of application/xml as described in RFC 3023 [RFC 3023], section 3.2, as applied to the SOAP envelope Infoset. * Security considerations: Because SOAP can carry application defined data whose semantics is independent from that of any MIME wrapper (or context within which the MIME wrapper is used), one should not expect to be able to understand the semantics of the SOAP message based on the semantics of the MIME wrapper alone. Therefore, whenever using the application/soap_xop+xml media type, it is strongly RECOMMENDED that the security implications of the context within which the SOAP message is used is fully understood. The security implications are likely to involve both the specific SOAP binding to an underlying protocol as well as the application-defined semantics of the data carried in the SOAP message (though one must be careful when doing this, as discussed in SOAP 1.2 Part 1 [SOAP Part 1], 7.3.1 Binding to Application-Specific Protocols. Also, see SOAP 1.2 Part 1 [SOAP Part 1], 7. Security Considerations. In addition, as this media type uses the "+xml" convention, it shares the same security considerations as described in RFC 3023 [RFC 3023], section 10. * Interoperability considerations: There are no known interoperability issues. * Published specification: SOAP 1.2 Part 1 [SOAP Part 1], SOAP 1.2 Part 2, [SOAP Part 2], and XOP [XOP]. * Applications which use this media type: No known applications currently use this media type. * Additional information: o File extension: SOAP messages are not required or expected to be stored as files. o Fragment identifiers: Identical to that of application/xml as described in RFC 3023 [RFC 3023], section 5. o Base URI: As specified in RFC 3023 [RFC 3023], section 6. Also see SOAP 1.2 Part 1 [SOAP Part 1], 6. Use of URIs in SOAP. o Macintosh File Type code: TEXT * Person and email address to contact for further information: Mark Nottingham <mnot(a)pobox.com> * Intended usage: COMMON * Author/Change controller: The SOAP 1.2 specification set is a work product of the World Wide Web Consortium's XML Protocol Working Group. The W3C has change control over these specifications. -- Yves Lafon - W3C "Baroula que barouleras, au tiéu toujou t'entourneras."

1 0

ConfirmSystem: iana@icann.org [[d3172205dcd5661b179167c0013cbdde]]
by iana＠iana.org 08 Jul '04

08 Jul '04

Thank you for your message. The iana(a)iana.org address collects a tremendous amount of spam, and we have been forced to implement protective measures. In order to process your message we need to confirm that it came from a real email address. To confirm your message, you can either: 1) Reply to this message, without altering the subject line The "Re: " added by many mail clients is OK, but please note that this method is *not* foolproof. or 2) Visit the URL <http://confirm.icann.org/?s=d3172205dcd5661b179167c0013cbdde&l=iana@icann.o…> If you want to be very sure that your message gets through, do both steps above -- it does no harm to confirm more than once. For your reference, the subject of the message you sent was: "Hi ietf-types your best buying" and it arrived at IANA approximately at Thu Jul 8 00:15:02 2004. --------------------------------------------------------------- ConfirmSystem: iana(a)icann.org [[d3172205dcd5661b179167c0013cbdde]] 1

1 0

RE: ConfirmSystem: iana@icann.org [[045bf60d0988526850b2e84d8c229459]]
by Misha Wolf 07 Jul '04

07 Jul '04

What does this mean: Tue Jul 6 21:55:18 2004 ? How about a time zone? And, possibly, a more standard layout? Thanks, Misha -----Original Message----- From: ietf-types-bounces(a)alvestrand.no [mailto:ietf-types-bounces@alvestrand.no] On Behalf Of iana(a)iana.org Sent: 07 July 2004 05:55 To: ietf-types(a)iana.org Subject: ConfirmSystem: iana(a)icann.org [[045bf60d0988526850b2e84d8c229459]] Thank you for your message. The iana(a)iana.org address collects a tremendous amount of spam, and we have been forced to implement protective measures. In order to process your message we need to confirm that it came from a real email address. To confirm your message, you can either: 1) reply to this message, without altering the subject line (the "Re: " added by many mail clients is OK). or 2) visit the URL <http://confirm.icann.org/?s=045bf60d0988526850b2e84d8c229459&l=iana@ica nn.org> For your reference, the subject of the message you sent was: "Ietf-types" and it arrived at IANA approximately at Tue Jul 6 21:55:18 2004. --------------------------------------------------------------- ConfirmSystem: iana(a)icann.org [[045bf60d0988526850b2e84d8c229459]] 1 ----------------------------------------------------------------- Visit our Internet site at http://www.reuters.com Get closer to the financial markets with Reuters Messaging - for more information and to register, visit http://www.reuters.com/messaging Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Reuters Ltd.

1 0

ConfirmSystem: iana@icann.org [[045bf60d0988526850b2e84d8c229459]]
by iana＠iana.org 07 Jul '04

07 Jul '04

Thank you for your message. The iana(a)iana.org address collects a tremendous amount of spam, and we have been forced to implement protective measures. In order to process your message we need to confirm that it came from a real email address. To confirm your message, you can either: 1) reply to this message, without altering the subject line (the "Re: " added by many mail clients is OK). or 2) visit the URL <http://confirm.icann.org/?s=045bf60d0988526850b2e84d8c229459&l=iana@icann.o…> For your reference, the subject of the message you sent was: "Ietf-types" and it arrived at IANA approximately at Tue Jul 6 21:55:18 2004. --------------------------------------------------------------- ConfirmSystem: iana(a)icann.org [[045bf60d0988526850b2e84d8c229459]] 1

1 0