Registration request for MIME media type tag 3gpp-ims+xml

[John M Meredith]

This proposed registration is being distributed to this list
(ietf-types at iana.org) for preliminary review, in accordance with the
instructions given by IANA.  It is cc'ed, as suggested by IANA, to Chris
Newman.  It is also cc'ed to 3GPP delegates to TSG CT WG1
(http://www.3gpp.org/tb/home.htm, http://www.3gpp.org/tb/CT/CT1/CT1.htm)
who have a technical interest in the matter.

Best regards

John M Meredith
3GPP Specifications Manager, ETSI

========================================================================
========================================


> Name : John M Meredith (3GPP Specifications Manager)
> 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:
> ETSI TS 124 229 version 8.4.1, being a formal transposition of 3GPP TS
24.229 version 8.4.1: 
>    "Internet Protocol (IP) multimedia call control protocol based on
Session Initiation Protocol (SIP) and Session 
>     Description Protocol (SDP); Stage 3"
> 
> Available via
http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0124229v841
(http://www.3gpp.org/ftp/Specs/html-info/24229.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
>