Registration of MIME media type MESSAGE/DISCLAIMER

Ravishankar Nandagopalan Ravishankar.Nandagopalan at microsoft.com
Fri Mar 20 13:57:00 CET 2009


MIME media type name: MESSAGE

     MIME subtype name: DISCLAIMER

     Required parameters: Disclaiming Domain (DD), Boundary

     Optional parameters: Disclaimer Action (DA),

                          Department Identification (DID)

     Encoding considerations: Appropriate encoding should be used based on the media being encoded as the types can include text plain, HTML, images and other multimedia contents

     Security considerations: Since disclaimers can be constructed using 'External-body' media type and can contain 'Image' media, the security considerations outlined in RFC 2046<http://www.rfc-editor.org/rfc/rfc2046.txt> and RFC 2045<http://www.rfc-editor.org/rfc/rfc2045.txt> will apply for the media type and the RFC list specified for the Image media sub-type specified here<http://www.iana.org/assignments/media-types/image/>.

     Applications which use this media type: Fax and Messaging

     Person & email address to contact for further information:

Ravishankar Nandagopalan
ravisn at microsoft.com

     Intended usage: COMMON

     Author/Change controller: Ravishankar Nandagopalan

Parameter descriptions:


1.  Disclaiming domain (DD): Defines the domain that inserts/owns the disclaimer.

2.  Boundary: Boundary delimiters, which is defined in RFC 2046<http://www.rfc-editor.org/rfc/rfc2045.txt>

3.  Disclaimer Action (DA): This optional parameter informs the user agent whether to append or prepend the disclaimer to the message body. The default action if omitted or unspecified should be 'Append'.

4.  Department Identification (DID): This parameter is used in the scenario where departments or entities disclaim using the same SMTP domain. This parameter should be populated when the aforementioned scenario exists to manage the disclaimers without duplication.

Media subtype usage:

This media sub-type is intended to make disclaimers more manageable and legible for the users by avoiding duplication of disclaimers and help manage their rich content for effective and error free encoding and transmission.
The media type will be used to treat disclaimers as a unique part of the message and all the norms that apply for a normal message body content will apply.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.alvestrand.no/pipermail/ietf-types/attachments/20090320/f3543f58/attachment.htm 


More information about the Ietf-types mailing list