Re: [Ietf-message-headers] HTTP 'Origin' permanent and provisional

Julian Reschke <julian.reschke@gmx.de> Wed, 13 February 2013 20:12 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 2723621F86B8 for <ietf-message-headers@ietfa.amsl.com>; Wed, 13 Feb 2013 12:12:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.398
X-Spam-Level:
X-Spam-Status: No, score=-106.398 tagged_above=-999 required=5 tests=[AWL=-3.799, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7+hSqXLeLnd4 for <ietf-message-headers@ietfa.amsl.com>; Wed, 13 Feb 2013 12:12:27 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) by ietfa.amsl.com (Postfix) with ESMTP id E923021F8688 for <ietf-message-headers@ietf.org>; Wed, 13 Feb 2013 12:12:25 -0800 (PST)
Received: from mailout-de.gmx.net ([10.1.76.20]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0MEHXK-1U7sPY27Xk-00FPP2 for <ietf-message-headers@ietf.org>; Wed, 13 Feb 2013 21:12:24 +0100
Received: (qmail invoked by alias); 13 Feb 2013 20:12:24 -0000
Received: from p5DD94DF5.dip.t-dialin.net (EHLO [192.168.1.102]) [93.217.77.245] by mail.gmx.net (mp020) with SMTP; 13 Feb 2013 21:12:24 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1++20QRp82+f143WopqzsqC3I9+51ZTzdyjCcHZmj 0wBLGkDtoZ2TKl
Message-ID: <511BF3A3.2090005@gmx.de>
Date: Wed, 13 Feb 2013 21:12:19 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: SM <sm@resistor.net>
References: <iljnh8d2cisqlsqvai0662974a0ei71qsn@hive.bjoern.hoehrmann.de> <6.2.5.6.2.20130213113549.0afcce60@resistor.net>
In-Reply-To: <6.2.5.6.2.20130213113549.0afcce60@resistor.net>
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, Bjoern Hoehrmann <derhoermi@gmx.net>, websec@ietf.org
Subject: Re: [Ietf-message-headers] HTTP 'Origin' permanent and provisional
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: Wed, 13 Feb 2013 20:12:27 -0000

On 2013-02-13 20:44, SM wrote:
> Hi Bjoern,
>
> [Cc to Websec as it is their document]
>
> At 09:37 13-02-2013, Bjoern Hoehrmann wrote:
>>   http://www.iana.org/assignments/message-headers/prov-headers.html and
>> http://www.iana.org/assignments/message-headers/perm-headers.html list
>> the "Origin" header for HTTP, one per RFC 6454 and one from an earlier
>> W3C registration. Is that as it should be?
>
> No.  IANA did what it was requested to do.  Anyway, in my opinion, it
> would have to be fixed (process stuff).
> ...

Yes and no.

The core task is running the registries, and those really should be set 
up such that things like that simply can not happen. Seems like a 
software problem to me -- apparently there are two registries where 
there should be only one.

Best regards, Julian