Re: [Ietf-message-headers] provisional registration: packaged content over http (5 headers)

Julian Reschke <julian.reschke@gmx.de> Tue, 17 January 2012 09:09 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf-message-headers@ietfa.amsl.com
Delivered-To: ietf-message-headers@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79CF221F8627 for <ietf-message-headers@ietfa.amsl.com>; Tue, 17 Jan 2012 01:09:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.513
X-Spam-Level:
X-Spam-Status: No, score=-103.513 tagged_above=-999 required=5 tests=[AWL=-0.914, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FkF3-mQ6GX9p for <ietf-message-headers@ietfa.amsl.com>; Tue, 17 Jan 2012 01:09:03 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id B8AA121F8587 for <ietf-message-headers@ietf.org>; Tue, 17 Jan 2012 01:09:02 -0800 (PST)
Received: (qmail invoked by alias); 17 Jan 2012 09:09:01 -0000
Received: from p3EE27258.dip.t-dialin.net (EHLO [192.168.178.36]) [62.226.114.88] by mail.gmx.net (mp068) with SMTP; 17 Jan 2012 10:09:01 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+WXoErMLCWTu1NNNFFD6o3j1W1nXVngedfLwVg4O vqau0U7IWoWwxU
Message-ID: <4F153AA9.5020805@gmx.de>
Date: Tue, 17 Jan 2012 10:08:57 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Richard Jones <rich.d.jones@gmail.com>
References: <CACEoUB2mQpmXowez2s4mZSanALRoZLSmkNZ5JK=FoDk041kGkw@mail.gmail.com> <4F153837.5030102@gmx.de>
In-Reply-To: <4F153837.5030102@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: ietf-message-headers@ietf.org
Subject: Re: [Ietf-message-headers] provisional registration: packaged content over http (5 headers)
X-BeenThere: ietf-message-headers@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for header fields used in Internet messaging applications." <ietf-message-headers.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-message-headers>, <mailto:ietf-message-headers-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-message-headers>
List-Post: <mailto:ietf-message-headers@ietf.org>
List-Help: <mailto:ietf-message-headers-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-message-headers>, <mailto:ietf-message-headers-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jan 2012 09:09:07 -0000

On 2012-01-17 09:58, Julian Reschke wrote:
> On 2011-12-22 18:31, Richard Jones wrote:
>> ...
>> On-Behalf-Of
>>
>> Header field name: On-Behalf-Of
>> Applicable protocol: HTTP
>> Status: provisional
>> Author/Change controller: Richard Jones c/o UKOLN, University of Bath;
>> rich.d.jones@gmail.com <mailto:rich.d.jones@gmail.com>
>> Specification Document:
>> http://sword-app.svn.sourceforge.net/viewvc/sword-app/spec/tags/sword-2.0/SWORD001.html?revision=377
>>
>> Related Information:
>> http://swordapp.org/sword-v2/sword-v2-specifications/
>> ...
>
> Does this field potentially need I18N? The way it's specified now it is
> stuck with ISO8859-1 with no extension point.
> ...

Also, did you consider "From"?

"The From request-header field, if given, SHOULD contain an Internet 
e-mail address for the human user who controls the requesting user 
agent. The address SHOULD be machine-usable, as defined by "mailbox" in 
RFC 822 [9] as updated by RFC 1123 [8]:

     From   = "From" ":" mailbox

An example is:

     From: webmaster@w3.org

This header field MAY be used for logging purposes and as a means for 
identifying the source of invalid or unwanted requests. It SHOULD NOT be 
used as an insecure form of access protection. The interpretation of 
this field is that the request is being performed on behalf of the 
person given, who accepts responsibility for the method performed. In 
particular, robot agents SHOULD include this header so that the person 
responsible for running the robot can be contacted if problems occur on 
the receiving end.

The Internet e-mail address in this field MAY be separate from the 
Internet host which issued the request. For example, when a request is 
passed through a proxy the original issuer's address SHOULD be used.

The client SHOULD NOT send the From header field without the user's 
approval, as it might conflict with the user's privacy interests or 
their site's security policy. It is strongly recommended that the user 
be able to disable, enable, and modify the value of this field at any 
time prior to a request."

Best regards, Julian