Request for MIME media type Application/Vendor Tree - vnd.3gp p.sms-tl

[Biot Olivier]

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 at 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