Specification of 3GPP IM CN Subsystem XML body handling
draft-bakker-dispatch-3gpp-ims-xml-body-handling-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | John-Luc Bakker | ||
Last updated | 2013-03-11 (Latest revision 2012-09-04) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document registers new disposition-types for the Content- Disposition header field that apply to the application/3gpp-ims+xml body (part) used by 3GPP [5]. The applicability of these content- disposition values are limited to 3GPP IMS [5]. The application/ 3gpp-ims+xml body (part) has the following three distinct uses: (1) for redirecting the emergency session to use a different domain (e.g. using a Circuit Switched call), (2) for delivering user profile specific information from the SIP registrar to an Application Server, and (3) for causing a UAC to attempt to re-register with the IMS.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)