Dear IESG Following the instructions provided by IANA's Amanda Baber (below) and successful resolution of all comments raised in response to the original posting to ietf-types@iana.org on 8 July 2008, I am pleased to request formal registration of MIME media type tag 3gpp-ims+xml (agreed details immediately below). Thanks to all contributors. John M Meredith 3GPP Specifications Manager ETSI ======================================================================== ================================= MIME media type name: Application MIME subtype name: 3gpp-ims+xml Required parameters: None Optional parameters: "charset" the parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in RFC 3023. "sv" or "schemaversion" the parameter's value indicates versions corresponding to 3GPP IM CN Subsystem XML schema documents as specified in 3GPP TS 24.228. Encoding considerations: Same as encoding considerations of application/xml as specified in RFC 3023 [132] Security considerations: 3GPP has defined mechanisms for ensuring the privacy and integrity protection of the bodies of SIP messages used in the 3GPP IM CN Subsystem. Interoperability considerations: This content type provides a format for exchanging information in SIP Requests and Responses and used within the 3GPP IM CN Subsystem. Published specification: 3GPP TS 24.229 version 8.4.1: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP), stage 3" Available via http://www.3gpp.org/specs/numbering.htm. Applications which use this media: Applications that use the 3GPP IM CN Subsystem as defined by 3GPP. Additional information : 1. Magic number(s) : none 2. File extension(s) : none 3. Macintosh file type code : none 4. Object Identifiers: none Application submitted on behalf of the Organizational Partners of 3GPP. Person to contact for further information : 1. Name : John M Meredith, 3GPP Specifications Manager 2. Email : john.meredith&etsi.org Intended usage: This content type provides a format for exchanging information in SIP Requests and Responses as used within the 3GPP IM CN Subsystem. Author/Change controller : 3GPP Specifications Manager via www.3gpp.org Technical contact: jbakker&rim.com ======================================================================== ================================= -----Original Message----- From: Amanda Baber via RT [mailto:iana-questions@icann.org] Sent: Monday, July 07, 2008 7:26 PM To: John M Meredith Subject: [IANA #178083] Registration request for MIME media type tag 3gpp-ims+xml Dear John, IANA is unable to process requests for media type registrations in the standards tree. Standards tree registrations must instead be submitted directly to the IESG, which will instruct us to add them to the registry upon approval. Standards tree applicants should follow these steps, as outlined by Applications Area Director Chris Newman: * Write registration that complies with mandatory features of RFC 4288. <http://tools.ietf.org/html/rfc4288#section-4> * Post registration form on ietf-types@iana.org list for preliminary review. <http://www.alvestrand.no/mailman/listinfo/ietf-types> <http://tools.ietf.org/html/rfc4288#section-5.1> * Respond to review comments and re-post as necessary. * Send an email to iesg@ietf.org pointing to the final version of the registration template, and preferably pointing to the review posting in the ietf-types archive. You may also wish to contact Chris Newman directly at chris.newman@sun.com. Best regards, Amanda Baber Internet Assigned Numbers Authority (IANA) On Mon Jul 07 13:18:30 2008, John.Meredith@etsi.org wrote:
Name : John M Meredith Email : john.meredith&etsi.org
MIME media type name: Application
MIME subtype name: 3gpp-ims+xml
Required parameters: None
Optional parameters: "charset" the parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in RFC 3023 [132]. "sv" or "schemaversion" the parameter's value is used to indicate: - the versions of the 3GPP IM CN Subsystem XML schema that can be used to validate the 3GPP IM CN subsystem XML body (if the MIME type and parameter are present in the Content-Type header) or - the accepted versions of the 3GPP IM CN Subsystem XML body (if the MIME type and parameter are present in the Accept header).
If the "sv" or "schemaversion" parameter is absent, it shall be assumed that version 1 of the XML Schema for the IM CN subsystem XML body is supported.
This registration entry includes ABNF that modifies the m-parameter definition in RFC 3261 [26]. m-parameter allows for attribute/value pairs that are applicable to the media range. In particular, the ABNF below is given for a media range application/3gpp-ims+xml specific m-parameter.
m-parameter /= ("sv" / "schemaversion") EQUAL LDQUOT [ sv-value- list ] RDQUOT sv-value-list = sv-value-range *( "," sv-value ) sv-value-range = sv-value [ "-" sv-value ] sv-value = number / token number = 1*DIGIT [ "." 1*DIGIT ]
Encoding considerations: Same as encoding considerations of application/xml as specified in RFC 3023 [132]
Security considerations: 3GPP has defined mechanisms for ensuring the privacy and integrity protection of the bodies of SIP messages used in the 3GPP IM CN Subsystem.
Interoperability considerations: This content type provides a format for exchanging information in SIP Requests and Responses and used within the 3GPP IM CN Subsystem.
Published specification: 3GPP TS 24.229 version 8.4.1: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP), stage 3"
Available via http://www.3gpp.org/specs/numbering.htm.
Applications which use this media: Applications that use the 3GPP IM CN Subsystem as defined by 3GPP.
Additional information :
1. Magic number(s) : none 2. File extension(s) : none 3. Macintosh file type code : none 4. Object Identifiers: none
Application submitted on behalf of the Organizational Partners of 3GPP.
Person to contact for further information :
1. Name : John M Meredith, 3GPP Specifications Manager 2. Email : john.meredith&etsi.org
Intended usage: This content type provides a format for exchanging information in SIP Requests and Responses as used within the 3GPP IM CN Subsystem.
Author/Change controller : 3GPP Specifications Manager via www.3gpp.org Technical contact: jbakker&rim.com