July 2004 - Ietf-types

Request For Registration of Media Type
by Marc Clifton 16 Sep '04

16 Sep '04

2 1

draft-hodges-saml-mediatype-01
by Jeff Hodges 21 Aug '04

21 Aug '04

Any feedback on the below draft? thanks, JeffH ----- http://www.ietf.org/internet-drafts/draft-hodges-saml-mediatype-01.txt ----------------------------------------------------------------------------- Network Working Group J. Hodges Internet-Draft Sun Microsystems, Inc. Expires: December 16, 2004 June 17, 2004 application/saml+xml Media Type Registration draft-hodges-saml-mediatype-01 Status of this Memo By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3667. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http:// www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on December 16, 2004. Copyright Notice Copyright (C) The Internet Society (2004). All Rights Reserved. Abstract This document describes a MIME media type -- application/saml+xml -- for use with the XML serialization of SAML (Security Assertion Markup Language) assertions, or other SAML-defined objects. Hodges Expires December 16, 2004 [Page 1] Internet-Draft application/saml+xml June 2004 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1 Discussion of this Document . . . . . . . . . . . . . . . 3 1.2 Document Conventions . . . . . . . . . . . . . . . . . . . 3 2. Usage of the application/saml+xml MIME Media Type . . . . . . 4 3. application/saml+xml MIME Media Type Registration . . . . . . 4 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 5. Security Considerations . . . . . . . . . . . . . . . . . . . 6 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 Normative References . . . . . . . . . . . . . . . . . . . . . 6 Informative References . . . . . . . . . . . . . . . . . . . . 8 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 8 A. Revision History . . . . . . . . . . . . . . . . . . . . . . . 8 Intellectual Property and Copyright Statements . . . . . . . . 9 Hodges Expires December 16, 2004 [Page 2] Internet-Draft application/saml+xml June 2004 1. Introduction This document defines a MIME media type -- application/saml+xml -- for use with the XML serialization of SAML (Security Assertion Markup Language) assertions, or other SAML-defined objects. The SAML specification sets, SAML V1.0 [5] and SAML V1.1 [9], are work products of the OASIS [13] Security Services Technical Committee (SSTC) [14]. The SAML specifications define XML-based constructs with which one may make, and convey, security assertions. For example, one can assert that an authentication event pertaining to some subject has occured and convey said assertion to a relying party. 1.1 Discussion of this Document Please send comments on this document to the "security services comment" email distribution list: <mailto:security-services-comment@lists.oasis-open.org> The "security services comment" mailing list is publically archived here [15]. To post to the "security services comment" mailing list, one must subscribe to it. To subscribe, send a message with the single word "subscribe" in the message body, to: <mailto:security-services-comment-request@lists.oasis-open.org> Additionally, the SAML developer community email distribution list: <mailto:saml-dev@lists.oasis-open.org> may be employed to discuss usage of the application/saml+xml MIME media type. The "saml-dev" mailing list is publically archived here [16]. To post to the "saml-dev" mailing list, one must subscribe to it. To subscribe, send a message with the single word "subscribe" in the message body, to: <mailto:saml-dev-request@lists.oasis-open.org> 1.2 Document Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", Hodges Expires December 16, 2004 [Page 3] Internet-Draft application/saml+xml June 2004 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [2]. 2. Usage of the application/saml+xml MIME Media Type Application protocols capable of conveying MIME entities, such as HTTP [3], SHOULD use the media type defined in this document when conveying SAML-defined objects. 3. application/saml+xml MIME Media Type Registration This is a media type registration as defined in Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures [1] and XML Media Types [4]. MIME media type name: application MIME subtype name: saml+xml Required parameters: none Optional parameters: charset Same as charset parameter of application/xml. Encoding considerations: Same as charset parameter of application/xml. Security considerations: Security considerations include many of those described in section 10 of RFC 3023 [4] as well as those specifically described in: SAML V1.0 Assertions and Protocol [6] SAML V1.0 Bindings and Profiles [7] SAML V1.0 Security and Privacy Considerations [8] ..and/or.. Hodges Expires December 16, 2004 [Page 4] Internet-Draft application/saml+xml June 2004 SAML V1.1 Assertions and Protocol [10] SAML V1.1 Bindings and Profiles [11] SAML V1.1 Security and Privacy Considerations [12] . ..depending on the version of the SAML object (see the next item). Interoperability considerations: SAML assertions are explicitly versioned. Relying parties SHOULD ensure that they observe assertion version information and behave accordingly. See "Chapter 4 SAML Versioning" in SAML V1.0 Assertions and Protocol [6], and/or SAML V1.1 Assertions and Protocol [10], as appropriate. Published specification: See the SAML V1.0 [5] and SAML V1.1 [9] specification sets. Applications which use this media type: SAML is device-, platform-, and vendor-neutral and is supported by a range of server- and client-side applications and tools. Additional information: Magic number(s): none, but.. Although no byte sequences can be counted on to consistently identify SAML objects, i.e. assertions and/or protocol messages, they will contain either one, or both of, the strings: urn:oasis:names:tc:SAML:1.0:assertion urn:oasis:names:tc:SAML:1.0:protocol to identify the SAML XML namespace(s). File extension(s): none Macintosh File Type Code(s): none Hodges Expires December 16, 2004 [Page 5] Internet-Draft application/saml+xml June 2004 Person & email address to contact for further information: Use the email distribution lists identified in Section 1.1 above. Additionally, or otherwise, refer to the Security Services Technical Committee website [14]. Intended usage: COMMON Author/Change controller: The SAML specification sets are a work product of the OASIS Security Services Technical Committee (SSTC). OASIS and the SSTC have change control over the SAML specification sets. 4. IANA Considerations This document calls for registration of a new MIME content-type, according to the registration information given above in Section 3. 5. Security Considerations See the "Security Considerations" item in Section 3 above. 6. Acknowledgements This doc is based on Aaron Schwartz' internet-draft for the application/rdf+xml MIME media type [18]. Thanks to Graham Klyne for pointing me to the latter, to Scott Cantor and John Kemp for volunteering me to write this, and to Marshall Rose for his xml2rfc document converter gizmo [17]. Artists whose music contributed to the writing of this spec ranged from John Coltrane [19] to Trapt [20]. Normative References [1] Freed, N., Klensin, J. and J. Postel, "Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures", BCP 13, RFC 2048, November 1996. [2] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [3] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P. and T. Berners-Lee, "Hypertext Transfer Protocol -- Hodges Expires December 16, 2004 [Page 6] Internet-Draft application/saml+xml June 2004 HTTP/1.1", RFC 2616, June 1999. [4] Murata, M., St. Laurent, S. and D. Kohn, "XML Media Types", RFC 3023, January 2001. [5] OASIS, "Security Assertion Markup Language (SAML) Version 1.0 Specification Set", OASIS Standard 200205, September 2003, <http://www.oasis-open.org/committees/download.php/2290/ oasis-sstc-saml-1.0.zip>. [6] Hallam-Baker, P., Ed. and E. Maler, Ed., "Assertions and Protocol for the OASIS Security Assertion Markup Language (SAML) V1.0", OASIS Standard 200205, November 2002, <http:// www.oasis-open.org/apps/org/workgroup/security/download.php/ 1371/oasis-sstc-saml-core-1.0.pdf>. [7] Mishra, P., Ed., "Bindings and Profiles for the OASIS Security Assertion Markup Language (SAML) V1.0", OASIS Standard 200205, November 2002, <http://www.oasis-open.org/apps/org/workgroup/ security/download.php/1372/oasis-sstc-saml-bindings-1.0.pdf>. [8] McLaren, C., Ed., "Security and Privacy Considerations for the OASIS Security Assertion Markup Language (SAML) V1.0", OASIS Standard 200205, November 2002, <http://www.oasis-open.org/ apps/org/workgroup/security/download.php/1375/ oasis-sstc-saml-sec-consider-1.0.pdf>. [9] OASIS, "Security Assertion Markup Language (SAML) Version 1.1 Specification Set", OASIS Standard 200308, September 2003, <http://www.oasis-open.org/committees/download.php/3400/ oasis-sstc-saml-1.1-pdf-xsd.zip>. [10] Maler, E., Ed., Mishra, P., Ed. and R. Philpott, Ed., "Assertions and Protocol for the OASIS Security Assertion Markup Language (SAML) V1.1", OASIS Standard 200308, September 2003, <http://www.oasis-open.org/apps/org/workgroup/security/ download.php/3406/oasis-sstc-saml-core-1.1.pdf>. [11] Maler, E., Ed., Mishra, P., Ed. and R. Philpott, Ed., "Bindings and Profiles for the OASIS Security Assertion Markup Language (SAML) V1.1", OASIS Standard 200308, September 2003, <http:// www.oasis-open.org/apps/org/workgroup/security/download.php/ 3405/oasis-sstc-saml-bindings-1.1.pdf>. [12] Maler, E., Ed. and R. Philpott, Ed., "Security and Privacy Considerations for the OASIS Security Assertion Markup Language (SAML) V1.1", OASIS Standard 200308, September 2003, <http://www.oasis-open.org/apps/org/workgroup/security/ Hodges Expires December 16, 2004 [Page 7] Internet-Draft application/saml+xml June 2004 download.php/3404/oasis-sstc-saml-sec-consider-1.1.pdf>. Informative References [13] "Organization for the Advancement of Structured Information Systems (OASIS)", <http://www.oasis-open.org/>. [14] "Security Services Technical Committee (SSTC/SAML)", <http:// www.oasis-open.org/committees/security/>. [15] "SSTC/SAML 'comment' Mailing List Archives", <http:// lists.oasis-open.org/archives/security-services-comment/>. [16] "SSTC/SAML 'saml-dev' Mailing List Archives", <http:// lists.oasis-open.org/archives/saml-dev/>. [17] "Marshall Rose's xml2rfc tool", <http://xml.resource.org>. URIs [18] <http://www.aaronsw.com/2002/ draft-w3c-rdfcore-rdfxml-mediatype-01> [19] <http://www.johncoltrane.com/> [20] <http://www.trapt.com/> Author's Address Jeff Hodges Sun Microsystems, Inc. 4220 Network Circle, Bldg 22, USCA22-212 Santa Clara, CA 95054 USA Phone: +1 408.276.5467 EMail: Jeff.Hodges(a)sun.com URI: http://www.sun.com/ Appendix A. Revision History Hodges Expires December 16, 2004 [Page 8] Internet-Draft application/saml+xml June 2004 Intellectual Property Statement The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the IETF's procedures with respect to rights in IETF Documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr(a)ietf.org. Disclaimer of Validity This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Copyright Statement Copyright (C) The Internet Society (2004). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society. Hodges Expires December 16, 2004 [Page 9] -----------------------------------------------------------------------------

2 2

Request for MIME media type application/vnd.3gpp.sms-tl
by Biot Olivier 29 Jul '04

29 Jul '04

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 is 8-bit binary by design, hence it may require encoding on transports not capable of handling binary. The SMS service allows transport of text messages; however the character encoding used in such an SMS message (including the message text itself) is part of the binary data and must not be specified with a charset parameter. Security considerations : The Short Messaging Service Transfer Layer (SMS-TL) format may contain executable code and user confidential information. The associated media type does not provide mechanisms for detection and prevention of eavesdropping, spoofing and tampering. In situations where tampering, eavesdropping and spoofing are possible and may cause problems, it is advised to use a secure transport protocol (such as HTTP over TLS), and/or to use a safe integrity verification mechanism (such as digital signing of the body). 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. This media type contains headers and a SMS message body. The headers specify among others how the message body has to be interpreted. The message body can for example be a text message, but also a WAP Push message or an Enhanced Message Service (EMS) message for example. 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. Published specification : ETSI TS 123 040 is the technical realization of 3GPP TS 23.040. Note that both specifications follow a similar versioning system. For instance, ETSI TS 123 040 V4.6.0 is the technical realization of 3GPP TS 23.040 V4.6.0. The ETSI specifications can be retrieved from http://pda.etsi.org/pda/queryform.asp (Search for "TS 123 040" and tick "Standard Type and Doc Number" for the search query). The 3GPP specifications can be retrieved from http://www.3gpp.org/ftp/Specs/archive/23_series/23.040/ (choose matching 3GPP and ETSI version). Applications which use this media : Applications that transport and manipulate MIME typed objects (messaging, download etc.). Additional information : This (binary) media type is not intended for file storage. 1. Magic number(s) : n/a 2. File extension(s) : n/a 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 (SMS) is a very common messaging service available on most mobile networks. SMS is not limited to the popular transport of text-only messages. The registration of the associated MIME type allows a SMS message to be delivered independent of the transport network. Author/Change controller : 3GPP/ETSI The SMS-TL specifications are written and maintained by 3GPP and ETSI.

1 0

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

29 Jul '04

|From: Martin Duerst | | |At 11:52 04/07/28 +0200, Biot Olivier wrote: | |>The SMS service allows transport of text messages; however |the character set |>used in such an SMS message (including the message text |itself) is part of |>the binary data and must not be specified with the charset parameter. | |Thanks for the clarification. Apart from the change suggested by Ned, |I would change "character set" to "character encoding". I agree. |I would also be interested to know (doesn't necessarily need to show |up in the registration) what kind of encodings are supported. For |example, does SMS allow message text to be encoded in an Unicode- |based encoding? Are all the encodings supported registered as |IANA 'charset's, or are there others? According to 3GPP TS 23.038 (alphabets and language-specific information), the GSM SMS data coding allows GSM 7-bit alphabet (which allows to stuff up to 160 characters in 140 bytes), 8-bit data and 16-bit Unicode UCS-2 character encoding. The used data coding is encoded in binary fashion in the GSM SMS "data coding scheme", and has no relationship with (read: does not use) the "charset" tokens registered at IANA (although the used character encodings are identical). Best regards, Olivier

1 0

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

29 Jul '04

Hi list, Many thanks to all for your valuable review input. Please find an updated MIME media type registration application for "application/vnd.3gpp.sms-tl". I think I dealt with all the issues raised during the review. Please let me know if the application below is OK! Best regards, Olivier Biot ------------------------------------------------------------ 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 is 8-bit binary by design, hence it may require encoding on transports not capable of handling binary. The SMS service allows transport of text messages; however the character set used in such an SMS message (including the message text itself) is part of the binary data and must not be specified with the charset parameter. Security considerations : The Short Messaging Service Transfer Layer (SMS-TL) format may contain executable code and user confidential information. The associated media type does not foresee mechanisms for detection and prevention of eavesdropping, spoofing and tampering. In situations where tampering, eavesdropping and spoofing are possible and may cause problems, it is advised to use a secure transport protocol (such as HTTP over TLS), and/or to use a safe integrity verification mechanism (such as digital signing of the body). 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. This media type contains headers and a SMS message body. The headers specify among others how the message body has to be interpreted. The message body can for example be a text message, but also a WAP Push message or an Enhanced Message Service (EMS) message for example. 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. Published specification : ETSI TS 123 040 is the technical realization of 3GPP TS 23.040. Note that both specifications follow a similar versioning system. For instance, ETSI TS 123 040 V4.6.0 is the technical realization of 3GPP TS 23.040 V4.6.0. The ETSI specifications can be retrieved from http://pda.etsi.org/pda/queryform.asp (Search for "TS 123 040" and tick "Standard Type and Doc Number" for the search query). The 3GPP specifications can be retrieved from http://www.3gpp.org/ftp/Specs/archive/23_series/23.040/ (choose matching 3GPP and ETSI version). Applications which use this media : Applications that transport and manipulate MIME typed objects (messaging, download etc.). Additional information : This (binary) media type is not intended for file storage. 1. Magic number(s) : n/a 2. File extension(s) : n/a 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 (SMS) is a very common messaging service available on most mobile networks. SMS is not limited to the popular transport of text-only messages. The registration of the associated MIME type allows a SMS message to be delivered independent of the transport network. Author/Change controller : 3GPP/ETSI The SMS-TL specifications are written and maintained by 3GPP and ETSI.

3 2

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