Registration of MIME media type MESSAGE/DISCLAIMER

Wed Mar 25 11:46:14 CET 2009

Hi Bjorn,

I did not read carefully then, though I'm in the process of writing a RFC, here goes the answers to you queries:

A example message:

Content-Type: Message/Disclaimer;
Disclaiming-Domain= Microsoft.com; Disclaimer-Action: Prepend; Department-Identification= Finance;      boundary="--sample boundary"

----sample boundary
Content-Type: multipart/mixed;             boundary="--first boundary"

This is a multi-part message in MIME format.

----first boundary
Content-Type: multipart/alternative;      boundary="--second boundary"

----second boundary
Content-Type: text/plain;
              charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<the plain text disclaimer goes here>

----second boundary
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML version of Disclaimer goes here along with CID for usage of Images as defined in RFC 2392>

--second boundary--
--first boundary--
--sample boundary--

In simple terms, the disclaimer media subtype is intended to sanitize the handling of message disclaimer and avoid duplicates and organize them in a better way as advancements in Email clients and server demand in clear as well as rich messages, that catches the attention of the reader.

Disclaimer content apart from its purpose/usage it is simply a extension of message body and has all the properties and norms of a message body.

Cheers,
Ravishankar

-----Original Message-----
From: Bjoern Hoehrmann [mailto:derhoermi at gmx.net]
Sent: 24 March 2009 22:46
To: Ravishankar Nandagopalan
Cc: ietf-types at iana.org
Subject: Re: Registration of MIME media type MESSAGE/DISCLAIMER

* Ravishankar Nandagopalan wrote:
>MIME media type name: MESSAGE

Please note that procedures for registering media types are specified in
RFC 4288 <http://www.ietf.org/rfc/rfc4288.txt>. Specifically, note that
registration in the standards tree requires the type to be defined in an
RFC or comparable standards document. Without such a document the type
should probably be registered in some other tree. Also note differences
between the RFC 4288 template there and the one you've provided.

There does not seem to be an actual description of the general format
for messages of this type. Could you perhaps give an example of a proper
message?

>     Required parameters: Disclaiming Domain (DD), Boundary
>
>     Optional parameters: Disclaimer Action (DA),
>
>                          Department Identification (DID)

It is unclear what the names and syntax requirements are for these
parameters, the parameter descriptions later in your message do not
help much.

>     Encoding considerations: Appropriate encoding should be used ...

The value should be one of 7bit, 8bit, binary, framed.

>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>

Could you comment on why, then, this is not a multipart type?
--
Björn Höhrmann · mailto:bjoern at hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/