Mail Content Disposition Values and Parameters

(last updated 2008-09-02)

In [RFC2183] there is a discussion of the "Content-Disposition" header
field and the description of the initial values allowed in this
header.  Additional values may be registered with the IANA
following the procedures in section 9 of [RFC2183].


Registry Name: Mail Content Disposition Values
Reference: [RFC2183]

Registry:
Name                     Description                                   Reference
-----------------------  --------------------------------------------  ---------
inline                   displayed automatically                       [RFC2183]
attachment               user controlled display                       [RFC2183]
form-data                process as form response                      [RFC2388]
signal                   tunneled content to be processed silently     [RFC3204]
alert                    the body is a custom ring tone to alert the   [RFC3261]
                         user
icon                     the body is displayed as an icon to the user  [RFC3261]
render                   the body should be displayed to the user      [RFC3261]
recipient-list-history   the body contains a list of URIs that         [RFC-ietf-sipping-capacity-attribute-07.txt]
                         indicates the recipients of the request
session                  the body describes a communications session,  [RFC3261]
                         for example, an RFC2327 SDP body
signed-receipt-protocol  requested signature format for signed         [RFC3335]
                         receipt
signed-receipt-micalg    requested signature algorithm for signed      [RFC3335]
                         receipt
aib                      Authenticated Identity Body                   [RFC3893]
early-session            the body describes an early communications    [RFC3959]
                         session, for example, and [RFC2327] SDP body 
recipient-list           The body contains a list of URIs to which     [RFC-ietf-sipping-uri-services-07.txt]
                         URI-List Services are to be applied.


Registry Name: Mail Content Disposition Parameters
Reference: [RFC2183]

Name                      Description                                  Reference
------------------------  -------------------------------------------  ---------
filename                  name to be used when creating file           [RFC2183]
creation-date             date when content was created                [RFC2183]
modification-date         date when content was last modified          [RFC2183]
read-date                 date when content was last read              [RFC2183]
size                      approximate size of content in octets        [RFC2183]
name                      original field name in form                  [RFC2388]
voice                     type or use of audio content                 [RFC2421]
handling                  wheter or not processing is required         [RFC3204]


Mail Content Disposition Parameter Values
-----------------------------------------

Voice Parameter Values
  Voice-Message               [RFC2421]
  Voice-Message-Notification  [RFC2421]
  Originator-Spoken-Name      [RFC2421]
  Recipient-Spoken-Name       [RFC2421]
  Spoken-Subject              [RFC2421]

Handling Parameter Values
  required - body must be understood                           [RFC3204]
  optional - body may be silently discarded                    [RFC3204]


References
----------
[RFC2183]  Troost, R., S. Dorner, and K. Moore, "Communicating
           Presentation Information in Internet Messages: The
           Content-Disposition Header Field", RFC 2183, New Century
           Systems, QUALCOMM Incorporated, University of Tennessee,
           August 1997.

[RFC2327]  M. Handley and V. Jacobson, "SDP: Session Description 
           Protocol", RFC 2327, April 1998.

[RFC2388]  L. Masinter, "Returning Values from Forms: 
           multipart/form-data", RFC 2388, August 1998.

[RFC2421]  G. Vaudreuil and G. Parsons, "Voice Profile for 
           Internet Mail - version 2, RFC 2421, September 1998.

[RFC3204]  E. Zimmerer, J. Peterson, A. Vemuri, L. Ong, F. Audet, 
           M. Watson, and M. Zonoun, "MIME media types for ISUP 
           and QSIG Objects", RFC 3204, Decmeber 2001.

[RFC3261]  J. Rosenberg, H. Schulzrinne, G. Camarillo, A. Johnston, 
           J. Peterson, R. Sparks, M. Handley, and E. Schooler,
           "SIP: Session Initiation Protocol", RFC 3261, June 2002.

[RFC3335]  T. Harding, R. Drummond, and Chuck Shih, "MIME-based 
           Secure Peer-to-Peer Business Data Interchange over the
           Internet", RFC 3335, August 2002.

[RFC3893]   J. Peterson, "SIP Authenticated Identity Body (AIB) Format",
            RFC 3893, September 2004.

[RFC3959]   G. Camarillo, "The Early Session Disposition Type for the 
            Session Initiation Protocol (SIP)", RFC 3959, December 2004.

[RFC-ietf-sipping-uri-services-07.txt]
            G. Camarillo, A. Roach, "Framework and Security Considerations 
            for Session Initiation Protocol (SIP) Uniform Resource 
            Identifier (URI)-List Services", RFC XXXX, Month Year.

[RFC-ietf-sipping-capacity-attribute-07.txt]
            M. Garcia-Martin, G. Camarillo, "Extensible Markup Language 
            (XML) Format Extension for Representing Copy Control Attributes 
            in Resource Lists", RFC XXXX, Month Year.

[]