F.4 IANA registration template

29.1633GPPInterworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networksTS

Within the present subclause, information required for an IANA registration at http://www.iana.org/cgi-bin/mediatypes.pl is provided.

1. Media Type Name


2. Subtype name

"vnd.etsi.pstn+xml" (Vendor Tree)

3. Required parameters


4. Optional parameters


5. Encoding considerations


6. Security considerations

The security considerations for XML in RFC 3023 apply.

Modifications of the MIME body by a man-in-the-middle can have severe consequences:

The information derived from ISUP that can be transported with this MIME body influence the call handling of the SIP session that is being setup.

However, this MIME body is used only attached to SIP messages, and modifications of other parts of the SIP signalling will lead to comparable consequences. Protection of the SIP signalling will also protect the present MIME body. The SIP signalling should be protected as described in RFC 3261.

7. Interoperability considerations


8. Published specification

3GPP TS 29.163

9. Applications which use this media type

This MIME type is used as a message body within SIP messages.

It is used for sending information derived from ISUP or DSS1 signalling with no SIP equivalent.

10. Additional information

Magic number(s): none (see RFC 3023)

File extension(s): ".xml" (see RFC 3023)

Macintosh File Type Code(s): "Text" (see RFC 3023)

Object Identifier(s) or OID(s): none

11. Intended usage

Limited Use

12. Other Information/General Comment

The content of this MIME type is UTF-8 encoded. The charset parameter is not used.

Annex G (informative):

NOTE: The former contents of this annex are now contained in 3GPP TS 24.229 [9].

Annex H (normative):
Interworking of Originating Line Information (OLI) parameter (network option)