Request for MIME media type Application/Vendor Tree - vnd.3gpp.sm s-tl
[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@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@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
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. Do you mean 'translation' instead of 'transposition'? I'm not sure what it means to have a 'transposition' of a document.
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@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.
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? Regards, Larry -- http://larry.masinter.net
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@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. 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? Ned
Hello Olivier, At 14:27 04/07/27 +0200, Biot Olivier wrote:
[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@siemens.com
MIME media type name : Application
MIME subtype name : Vendor Tree - vnd.3gpp.sms-tl
Encoding considerations : binary This media type may require encoding on transports not capable of handling binary.
This is okay, but with respect to how characters are encoded, it may mean anything or nothing at all. Can you please add a short section that discusses how character conding is handled? Thanks, Martin.
participants (4)
-
Biot Olivier -
Larry Masinter -
Martin Duerst -
ned.freed＠mrochek.com