AcceptDisposition Header Field draftcamarillosipacceptdisposition00 txt Gonzalo Camarilloericsson com

Motivation • • RFC 3204 defines the “handling” parameter for the Content-Disposition header field

Accept-Disposition Header Field • Lists the disposition types supported by the server – Accept-Disposition:

Discussion • SIP capabilities: four axis – Supported Methods (Allow) – Supported media types

Discussion, Cont • Ways to require support for something – Method (implicit) – Option

Slides: 5

Download presentation

Accept-Disposition Header Field draft-camarillo-sip-accept-disposition-00. txt Gonzalo. Camarillo@ericsson. com

Motivation • • RFC 3204 defines the “handling” parameter for the Content-Disposition header field If handling=required and 1. body part has an unknown content type, or 2. body part has an unknown disposition type • Return 415 (Unsupported Media Type) – – If 1, add an Accept header field If 2… undefined

Accept-Disposition Header Field • Lists the disposition types supported by the server – Accept-Disposition: render, session • Scope: applicable to the request the response applies to – E. g. , A UA will not support ‘session’ bodies in MESSAGE requests • Useful for debugging purposes

Discussion • SIP capabilities: four axis – Supported Methods (Allow) – Supported media types (Accept) – Supported disposition types (New header) – Supported extensions (Supported) • Option tags

Discussion, Cont • Ways to require support for something – Method (implicit) – Option tag – Body with handling=required • Explore which policy we want to follow to define option tags – E. g. , MESSAGE exploder • Uri-list-message option tag • Support for MESSAGE and the recipient-list disposition type – Need a mechanism to express support for combinations • Clarify content disposition handling – Currently underspecified