[Ietf-message-headers] Inquiry: registration of "body" from mailto: URI

Martin Duerst <duerst@it.aoyama.ac.jp> Tue, 07 March 2006 03:01 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGSSE-00041n-SB; Mon, 06 Mar 2006 22:01:42 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGSSD-00041c-1P for ietf-message-headers@lists.ietf.org; Mon, 06 Mar 2006 22:01:41 -0500
Received: from scmailgw1.scop.aoyama.ac.jp ([133.2.251.194]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FGSSB-0005F9-Cb for ietf-message-headers@lists.ietf.org; Mon, 06 Mar 2006 22:01:41 -0500
Received: from scmse2.scbb.aoyama.ac.jp (scmse2 [133.2.253.17]) by scmailgw1.scop.aoyama.ac.jp (secret/secret) with SMTP id k2731Wu12549; Tue, 7 Mar 2006 12:01:32 +0900 (JST)
Received: from (133.2.210.1) by scmse2.scbb.aoyama.ac.jp via smtp id 6764_ae268f22_ad86_11da_88aa_0014221f2a2d; Tue, 07 Mar 2006 12:01:31 +0900
Received: from EBOSHIIWA.it.aoyama.ac.jp (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.13.1/8.13.1) with ESMTP id k272xrUl013976; Tue, 7 Mar 2006 12:00:52 +0900
Message-Id: <6.0.0.20.2.20060307114718.04611c00@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Version 6J
Date: Tue, 07 Mar 2006 11:57:54 +0900
To: ietf-message-headers@lists.ietf.org
From: Martin Duerst <duerst@it.aoyama.ac.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: Bruce Lilly <blilly@erols.com>
Subject: [Ietf-message-headers] Inquiry: registration of "body" from mailto: URI
X-BeenThere: ietf-message-headers@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussion list for header fields used in Internet messaging applications." <ietf-message-headers.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-message-headers>, <mailto:ietf-message-headers-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-message-headers@ietf.org>
List-Help: <mailto:ietf-message-headers-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-message-headers>, <mailto:ietf-message-headers-request@ietf.org?subject=subscribe>
Errors-To: ietf-message-headers-bounces@ietf.org

The mailto: URI uses a query syntax to indicate the values
of various email headers. There is one special case, namely
that a header field name of 'body' does not indicate an
actual header field, but gives the text that should go into
the body of the (prototype) message.

Bruce Lilly suggested that, in order to avoid that anybody else
would define a header field named 'body' in the future, this
header field should be duly registered with IANA.
(see http://lists.w3.org/Archives/Public/uri/2005Apr/0002).

I think this is a very good idea. I have prepared a registration
template in my draft-duerst-mailto-bis (unfortunately, that part
didn't make it into the -02.txt version I submitted yesterday).

Because the situation is a bit special, I would like to get
your expert feedback.

The registration template currently looks as follows:

    Header field name:
       Body

    Applicable protocol:
       none

    Status:
       reserved

    Author/Change controller:
       IETF

    Specification document(s):
       Internet-Draft draft-duerst-mailto-bis-03.txt
       (Note to RFC Editor: Replace this with
        RFC YYYY (RFC number of this specification))

    Related information:
       This registration serves to reserve the
       header field name 'Body' for use only in
       mailto: URIs and in similar situations where
       the body of a message has to be given an
       explicit name.

Regards,    Martin. 


_______________________________________________
Ietf-message-headers mailing list
Ietf-message-headers@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-message-headers