
From derhoermi@gmx.net  Wed Feb 13 09:37:11 2013
Return-Path: <derhoermi@gmx.net>
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 6ADC921F8844 for <ietf-message-headers@ietfa.amsl.com>; Wed, 13 Feb 2013 09:37:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 LWMrnmnyNthB for <ietf-message-headers@ietfa.amsl.com>; Wed, 13 Feb 2013 09:37:10 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by ietfa.amsl.com (Postfix) with ESMTP id 9365221F8842 for <ietf-message-headers@ietf.org>; Wed, 13 Feb 2013 09:37:07 -0800 (PST)
Received: from mailout-de.gmx.net ([10.1.76.20]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0Lur0x-1V4pTX1Z1V-01061B for <ietf-message-headers@ietf.org>; Wed, 13 Feb 2013 18:37:06 +0100
Received: (qmail invoked by alias); 13 Feb 2013 17:37:06 -0000
Received: from p5B23193A.dip.t-dialin.net (EHLO netb.Speedport_W_700V) [91.35.25.58] by mail.gmx.net (mp020) with SMTP; 13 Feb 2013 18:37:06 +0100
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX18c15oQiSkcn/O5svaAyYtywW8XFlT7HanegpGZTK C4sffZ++IBHCkP
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: ietf-message-headers@ietf.org
Date: Wed, 13 Feb 2013 18:37:07 +0100
Message-ID: <iljnh8d2cisqlsqvai0662974a0ei71qsn@hive.bjoern.hoehrmann.de>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Subject: [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 17:37:11 -0000

Hi,

  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?

regards,
-- 
Björn Höhrmann · mailto:bjoern@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/ 

From sm@resistor.net  Wed Feb 13 11:48:33 2013
Return-Path: <sm@resistor.net>
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 0FDA121E8055; Wed, 13 Feb 2013 11:48:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.575
X-Spam-Level: 
X-Spam-Status: No, score=-102.575 tagged_above=-999 required=5 tests=[AWL=0.025, 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 VPSGLjo87ZvJ; Wed, 13 Feb 2013 11:48:29 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id CAE9621F852C; Wed, 13 Feb 2013 11:48:29 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r1DJmJpr001254; Wed, 13 Feb 2013 11:48:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1360784904; bh=mmzsCLn2r8UjQDgXt9elQzA9QYrXgTEnyrcO/r+06eQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=t1LBkNTK/E/D4dz7dIM4IZMqs7LpOMWIvpNdD8w8yaF4GDP6kuJ2cO0X98ZbMaYcu GkynNMvu3tSVC51INdSm3Zard8rXf5r4Vqrmxat3DUGaXkW/EmEI7zb8QHAgcGMD1P QNhT665mPioMKeOYcac6egG0ia5GP7Lq9ztzPwm0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1360784904; i=@resistor.net; bh=mmzsCLn2r8UjQDgXt9elQzA9QYrXgTEnyrcO/r+06eQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=KReMLv4xsl0kDuUGq0n0x4qLis2YHNaYivpgjRp7si1t24cQlGwS7IFAazTTEA17R DKnWNF9ii+lyZlO91d9VfqM4IlAkjRhJZpmB7pUXMRP7WnpW43Y+JXT/GNHnDCfoC6 NQPmayQqsVFoEYaylltqIMeKBt1a8OLymnL/wUwM=
Message-Id: <6.2.5.6.2.20130213113549.0afcce60@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 13 Feb 2013 11:44:59 -0800
To: Bjoern Hoehrmann <derhoermi@gmx.net>
From: SM <sm@resistor.net>
In-Reply-To: <iljnh8d2cisqlsqvai0662974a0ei71qsn@hive.bjoern.hoehrmann.d e>
References: <iljnh8d2cisqlsqvai0662974a0ei71qsn@hive.bjoern.hoehrmann.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: websec@ietf.org, ietf-message-headers@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 19:48:33 -0000

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

Regards,
-sm





From julian.reschke@gmx.de  Wed Feb 13 12:12:27 2013
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

From julian.reschke@gmx.de  Wed Feb 13 12:24:35 2013
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 752A821F8715 for <ietf-message-headers@ietfa.amsl.com>; Wed, 13 Feb 2013 12:24:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.225
X-Spam-Level: 
X-Spam-Status: No, score=-106.225 tagged_above=-999 required=5 tests=[AWL=-3.626, 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 ydLN-Tnd45n6 for <ietf-message-headers@ietfa.amsl.com>; Wed, 13 Feb 2013 12:24:35 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) by ietfa.amsl.com (Postfix) with ESMTP id 733DF21F870E for <ietf-message-headers@ietf.org>; Wed, 13 Feb 2013 12:24:33 -0800 (PST)
Received: from mailout-de.gmx.net ([10.1.76.17]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0M52QK-1UqFU61v02-00zIuL for <ietf-message-headers@ietf.org>; Wed, 13 Feb 2013 21:24:24 +0100
Received: (qmail invoked by alias); 13 Feb 2013 20:24:24 -0000
Received: from p5DD97762.dip.t-dialin.net (EHLO [192.168.1.102]) [93.217.119.98] by mail.gmx.net (mp017) with SMTP; 13 Feb 2013 21:24:24 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19hIQptt4ph4XaW5KcQ+eGEXE2el5tJeeuQh9NcOi 4huYAU22kivyfd
Message-ID: <511BF66F.5070100@gmx.de>
Date: Wed, 13 Feb 2013 21:24:15 +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: Yoav Nir <ynir@checkpoint.com>
References: <iljnh8d2cisqlsqvai0662974a0ei71qsn@hive.bjoern.hoehrmann.de> <6.2.5.6.2.20130213113549.0afcce60@resistor.net> <4613980CFC78314ABFD7F85CC3027721119A6FFE@IL-EX10.ad.checkpoint.com>
In-Reply-To: <4613980CFC78314ABFD7F85CC3027721119A6FFE@IL-EX10.ad.checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, "<ietf-message-headers@ietf.org>" <ietf-message-headers@ietf.org>, "<websec@ietf.org>" <websec@ietf.org>
Subject: Re: [Ietf-message-headers] [websec] 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:24:35 -0000

On 2013-02-13 21:12, Yoav Nir wrote:
> Hi SM
>
> The W3C one is from a very old document, the first draft of which dates back to 2005. Anne van Kesteren has been editing it since 2007.
>
> The Origin header was first mentioned in the draft from September 2008. There it is sully explained.
> In 2009 the name of the document was changed to "Cross-Origin Resource Sharing".
> Starting with the version from July 2010, that document references the WebSec draft, and later the RFC.
>
> I suppose the provisional header should be removed, but the now-defunct W3C group is no longer available to request this.
>
> I'll see what can be done.
>
> Yoav
> ...

Well.

You make it sound as if it's ok to run two different registries with 
partly overlapping values. It's not. It's a bug in the way IANA handles 
this. This is what needs to be fixed.

Best regards, Julian

From barryleiba.mailing.lists@gmail.com  Wed Feb 13 12:31:00 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
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 1D2FF21E803D; Wed, 13 Feb 2013 12:31:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.924
X-Spam-Level: 
X-Spam-Status: No, score=-102.924 tagged_above=-999 required=5 tests=[AWL=0.053, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, 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 9JL4jTiGcppK; Wed, 13 Feb 2013 12:30:59 -0800 (PST)
Received: from mail-vb0-f41.google.com (mail-vb0-f41.google.com [209.85.212.41]) by ietfa.amsl.com (Postfix) with ESMTP id 76C4021F8651; Wed, 13 Feb 2013 12:30:59 -0800 (PST)
Received: by mail-vb0-f41.google.com with SMTP id l22so1048183vbn.0 for <multiple recipients>; Wed, 13 Feb 2013 12:30:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=EbnrH0X4v4eHS46L/TYIFw2BaG4lzfFixibliOeAXUM=; b=gzUSof1wEutfiKiPHqC37nlF/n2wvJGJuxJCgHUbxczHKXimtB85eGn4VgHchbbETO M2rJTin9Q8G3y8IeBKu3cmoqNi4xJB71XPKvWcamwy/LUOc+X7mT153blZk7M3KX41Np pXklERlv/TeWYREnKaengtUput5bo3+qThogiyURnkSEys61Kv5dX++MctuZzmC9vxDS lm2BpVOIiP8vOVyQCj7pbSZO86VVSKcjStQXCN3VxGntc+jokvJYaGpxyErTaoAOTeim VcdpS2fA8i9sQiltLibwnPQFfsCO2/HDwKJK3on1BxTXTdvU5GAKAUq0+UU88aDBKye2 CgvA==
MIME-Version: 1.0
X-Received: by 10.52.67.133 with SMTP id n5mr26480552vdt.24.1360787458415; Wed, 13 Feb 2013 12:30:58 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.59.3.41 with HTTP; Wed, 13 Feb 2013 12:30:58 -0800 (PST)
In-Reply-To: <511BF66F.5070100@gmx.de>
References: <iljnh8d2cisqlsqvai0662974a0ei71qsn@hive.bjoern.hoehrmann.de> <6.2.5.6.2.20130213113549.0afcce60@resistor.net> <4613980CFC78314ABFD7F85CC3027721119A6FFE@IL-EX10.ad.checkpoint.com> <511BF66F.5070100@gmx.de>
Date: Wed, 13 Feb 2013 15:30:58 -0500
X-Google-Sender-Auth: NQeZCNWjnkmBz7DO40y9i1yf7e0
Message-ID: <CAC4RtVBqhkgK=Ygy0J=jmN=7nMARsYEiU+C47UO_oX9pAFKFew@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Julian Reschke <julian.reschke@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "<ietf-message-headers@ietf.org>" <ietf-message-headers@ietf.org>, Bjoern Hoehrmann <derhoermi@gmx.net>, Yoav Nir <ynir@checkpoint.com>, "<websec@ietf.org>" <websec@ietf.org>
Subject: Re: [Ietf-message-headers] [websec] 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:31:00 -0000

> You make it sound as if it's ok to run two different registries with partly
> overlapping values. It's not. It's a bug in the way IANA handles this. This
> is what needs to be fixed.

Indeed.  I've already suggested to Yoav, off list, how to get this
fixed in this case.

I will talk with IANA in Orlando about dealing with it systematically.

Barry, Applications AD

From sm@resistor.net  Wed Feb 13 12:32:43 2013
Return-Path: <sm@resistor.net>
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 E2E0B21F862A; Wed, 13 Feb 2013 12:32:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.575
X-Spam-Level: 
X-Spam-Status: No, score=-102.575 tagged_above=-999 required=5 tests=[AWL=0.024, 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 fq52B15z7SeQ; Wed, 13 Feb 2013 12:32:42 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id D968521F8628; Wed, 13 Feb 2013 12:32:42 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r1DKWNAk022825; Wed, 13 Feb 2013 12:32:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1360787550; bh=rKCQeBEaYrM6QabYxf4Be641CyHF8zAzK8R7/pBgjF0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=2r1JVwcmdmQhVM76wyeXITjKwzJntFNx6ka08T465l21/7k0AtuyQno5nxRlRA3F3 h7CrpuQpGgnPh7xrA+hG9NAfGbBOMiNxkI/gN2sD9o0c4MwRmWGHr7V0C9WE6CZxDk vpHeVyqz4HzetrNzNNBt9I4HKAuY9lh7kZwGQDDk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1360787550; i=@resistor.net; bh=rKCQeBEaYrM6QabYxf4Be641CyHF8zAzK8R7/pBgjF0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=MCUI+R3iAdM79XZyCchYaAzJO0zo/ah1Q8G8lfZVWTaEALaV6efBICwB6cP8aqPCy k1qClCLiWGd+WEH3NRhm1hrX99ZQoaL6+7Vr08Edl+2csu76glDMl8qSwgi+JmrQRW AO7GRIKH+uleg/UjH22k4FUY8VGly+O5/1LyYlTQ=
Message-Id: <6.2.5.6.2.20130213122642.0a997470@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 13 Feb 2013 12:32:12 -0800
To: Julian Reschke <julian.reschke@gmx.de>
From: SM <sm@resistor.net>
In-Reply-To: <511BF66F.5070100@gmx.de>
References: <iljnh8d2cisqlsqvai0662974a0ei71qsn@hive.bjoern.hoehrmann.de> <6.2.5.6.2.20130213113549.0afcce60@resistor.net> <4613980CFC78314ABFD7F85CC3027721119A6FFE@IL-EX10.ad.checkpoint.com> <511BF66F.5070100@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: websec@ietf.org, Bjoern Hoehrmann <derhoermi@gmx.net>, ietf-message-headers@ietf.org, Yoav Nir <ynir@checkpoint.com>
Subject: Re: [Ietf-message-headers] [websec] 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:32:44 -0000

Hi Julian,
At 12:24 13-02-2013, Julian Reschke wrote:
>You make it sound as if it's ok to run two different registries with 
>partly overlapping values. It's not. It's a bug in the way IANA 
>handles this. This is what needs to be fixed.

It's easier to fix the bug first.

The following could be used:

   "When a new entry is recorded in the permanent message header field
    registry, IANA will remove any corresponding entries (with the same
    field name and protocol) from the provisional registry."

That avoids overlapping values.

Regards,
-sm 


From julian.reschke@gmx.de  Wed Feb 13 12:54:34 2013
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 BD29621E8084 for <ietf-message-headers@ietfa.amsl.com>; Wed, 13 Feb 2013 12:54:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.266
X-Spam-Level: 
X-Spam-Status: No, score=-105.266 tagged_above=-999 required=5 tests=[AWL=-2.667, 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 l93u5fV7psQC for <ietf-message-headers@ietfa.amsl.com>; Wed, 13 Feb 2013 12:54:30 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by ietfa.amsl.com (Postfix) with ESMTP id C3AD821F86A8 for <ietf-message-headers@ietf.org>; Wed, 13 Feb 2013 12:54:22 -0800 (PST)
Received: from mailout-de.gmx.net ([10.1.76.24]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0MeNF3-1UGuGY2cJz-00QEyG for <ietf-message-headers@ietf.org>; Wed, 13 Feb 2013 21:54:21 +0100
Received: (qmail invoked by alias); 13 Feb 2013 20:54:21 -0000
Received: from p54BB23EA.dip.t-dialin.net (EHLO [192.168.1.102]) [84.187.35.234] by mail.gmx.net (mp024) with SMTP; 13 Feb 2013 21:54:21 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1//u1c9QC3/09hyMt/VD+h6S0jCmxa21cISX4bpwP YD860z/RZ0ZZbg
Message-ID: <511BFD7B.40101@gmx.de>
Date: Wed, 13 Feb 2013 21:54: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: Yoav Nir <ynir@checkpoint.com>
References: <iljnh8d2cisqlsqvai0662974a0ei71qsn@hive.bjoern.hoehrmann.de> <6.2.5.6.2.20130213113549.0afcce60@resistor.net> <4613980CFC78314ABFD7F85CC3027721119A6FFE@IL-EX10.ad.checkpoint.com> <511BF66F.5070100@gmx.de> <4613980CFC78314ABFD7F85CC3027721119A7198@IL-EX10.ad.checkpoint.com>
In-Reply-To: <4613980CFC78314ABFD7F85CC3027721119A7198@IL-EX10.ad.checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: "<websec@ietf.org>" <websec@ietf.org>, Bjoern Hoehrmann <derhoermi@gmx.net>, "<ietf-message-headers@ietf.org>" <ietf-message-headers@ietf.org>
Subject: Re: [Ietf-message-headers] [websec] 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:54:34 -0000

On 2013-02-13 21:43, Yoav Nir wrote:
>
> On Feb 13, 2013, at 10:24 PM, Julian Reschke <julian.reschke@gmx.de>
>   wrote:
>
>> Well.
>>
>> You make it sound as if it's ok to run two different registries with partly overlapping values. It's not. It's a bug in the way IANA handles this. This is what needs to be fixed.
>>
>> Best regards, Julian
>
> I don't want to turn this into a process debate, but having a provisional registry like this allows you to create interoperable implementations while the document is still at draft. I often see a push to get a document published because we need the IANA assignments for products.

Yes.

> Of course they could still do this with a single registry where provisional entries are somehow marked (with an asterisk?). That way we wouldn't get to a situation where we have double entries.

The key thing being that both registries share the same namespace, so, 
by definition, an entry can not appear in both. If it does, there's a 
process/software problem.

Of course the trivial way to do this right is to implement a *single* 
registry, and to just store a flag for each entry.

Best regards, Julian


From mnot@mnot.net  Wed Feb 13 21:04:51 2013
Return-Path: <mnot@mnot.net>
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 E5C3221E80DE; Wed, 13 Feb 2013 21:04:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.504
X-Spam-Level: 
X-Spam-Status: No, score=-105.504 tagged_above=-999 required=5 tests=[AWL=-2.905, 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 BlagYeXpRbIg; Wed, 13 Feb 2013 21:04:50 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id CF1C021E80D5; Wed, 13 Feb 2013 21:04:47 -0800 (PST)
Received: from [192.168.1.80] (unknown [118.209.202.79]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 5AFB522E200; Thu, 14 Feb 2013 00:04:39 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <511BFD7B.40101@gmx.de>
Date: Thu, 14 Feb 2013 16:04:34 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <94E75F54-CA07-4276-98BD-F34C99A11A4A@mnot.net>
References: <iljnh8d2cisqlsqvai0662974a0ei71qsn@hive.bjoern.hoehrmann.de> <6.2.5.6.2.20130213113549.0afcce60@resistor.net> <4613980CFC78314ABFD7F85CC3027721119A6FFE@IL-EX10.ad.checkpoint.com> <511BF66F.5070100@gmx.de> <4613980CFC78314ABFD7F85CC3027721119A7198@IL-EX10.ad.checkpoint.com> <511BFD7B.40101@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.1499)
Cc: "<websec@ietf.org>" <websec@ietf.org>, Bjoern Hoehrmann <derhoermi@gmx.net>, Yoav Nir <ynir@checkpoint.com>, "<ietf-message-headers@ietf.org>" <ietf-message-headers@ietf.org>
Subject: Re: [Ietf-message-headers] [websec] 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: Thu, 14 Feb 2013 05:04:52 -0000

We've been talking for a while about revising 3864; it needs a lot more =
than this done.

Cheers,


On 14/02/2013, at 7:54 AM, Julian Reschke <julian.reschke@gmx.de> wrote:

> On 2013-02-13 21:43, Yoav Nir wrote:
>>=20
>> On Feb 13, 2013, at 10:24 PM, Julian Reschke <julian.reschke@gmx.de>
>>  wrote:
>>=20
>>> Well.
>>>=20
>>> You make it sound as if it's ok to run two different registries with =
partly overlapping values. It's not. It's a bug in the way IANA handles =
this. This is what needs to be fixed.
>>>=20
>>> Best regards, Julian
>>=20
>> I don't want to turn this into a process debate, but having a =
provisional registry like this allows you to create interoperable =
implementations while the document is still at draft. I often see a push =
to get a document published because we need the IANA assignments for =
products.
>=20
> Yes.
>=20
>> Of course they could still do this with a single registry where =
provisional entries are somehow marked (with an asterisk?). That way we =
wouldn't get to a situation where we have double entries.
>=20
> The key thing being that both registries share the same namespace, so, =
by definition, an entry can not appear in both. If it does, there's a =
process/software problem.
>=20
> Of course the trivial way to do this right is to implement a *single* =
registry, and to just store a flag for each entry.
>=20
> Best regards, Julian
>=20
> _______________________________________________
> Ietf-message-headers mailing list
> Ietf-message-headers@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-message-headers

--
Mark Nottingham   http://www.mnot.net/




From julian.reschke@gmx.de  Wed Feb 13 23:57:06 2013
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 E265F21F8722 for <ietf-message-headers@ietfa.amsl.com>; Wed, 13 Feb 2013 23:57:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.199
X-Spam-Level: 
X-Spam-Status: No, score=-104.199 tagged_above=-999 required=5 tests=[AWL=-1.600, 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 V2hVlDl8sCru for <ietf-message-headers@ietfa.amsl.com>; Wed, 13 Feb 2013 23:57:06 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by ietfa.amsl.com (Postfix) with ESMTP id 40C7D21F8BB5 for <ietf-message-headers@ietf.org>; Wed, 13 Feb 2013 23:57:06 -0800 (PST)
Received: from mailout-de.gmx.net ([10.1.76.35]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0LnEWZ-1UXVnw0Xfh-00hNY0 for <ietf-message-headers@ietf.org>; Thu, 14 Feb 2013 08:57:05 +0100
Received: (qmail invoked by alias); 14 Feb 2013 07:57:04 -0000
Received: from p54BB23EA.dip.t-dialin.net (EHLO [192.168.1.102]) [84.187.35.234] by mail.gmx.net (mp035) with SMTP; 14 Feb 2013 08:57:04 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18EjsAJ7/IEntCMCmHoBkkkaBpWCHIEdfI763rXI0 QI8M9oSoWXAbHZ
Message-ID: <511C98CC.1020801@gmx.de>
Date: Thu, 14 Feb 2013 08:57:00 +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: Mark Nottingham <mnot@mnot.net>
References: <iljnh8d2cisqlsqvai0662974a0ei71qsn@hive.bjoern.hoehrmann.de> <6.2.5.6.2.20130213113549.0afcce60@resistor.net> <4613980CFC78314ABFD7F85CC3027721119A6FFE@IL-EX10.ad.checkpoint.com> <511BF66F.5070100@gmx.de> <4613980CFC78314ABFD7F85CC3027721119A7198@IL-EX10.ad.checkpoint.com> <511BFD7B.40101@gmx.de> <94E75F54-CA07-4276-98BD-F34C99A11A4A@mnot.net>
In-Reply-To: <94E75F54-CA07-4276-98BD-F34C99A11A4A@mnot.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>" <ietf-message-headers@ietf.org>, Bjoern Hoehrmann <derhoermi@gmx.net>, "<websec@ietf.org>" <websec@ietf.org>
Subject: Re: [Ietf-message-headers] [websec] 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: Thu, 14 Feb 2013 07:57:07 -0000

On 2013-02-14 06:04, Mark Nottingham wrote:
> We've been talking for a while about revising 3864; it needs a lot more than this done.
>
> Cheers,
> ...

True, but the issue applies to all registries that are split into 
categories.

Best regards, Julian


From derhoermi@gmx.net  Thu Feb 14 10:18:53 2013
Return-Path: <derhoermi@gmx.net>
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 8777421F883F for <ietf-message-headers@ietfa.amsl.com>; Thu, 14 Feb 2013 10:18:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 s0gLL95qpmYg for <ietf-message-headers@ietfa.amsl.com>; Thu, 14 Feb 2013 10:18:52 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by ietfa.amsl.com (Postfix) with ESMTP id 5A00521F8523 for <ietf-message-headers@ietf.org>; Thu, 14 Feb 2013 10:18:52 -0800 (PST)
Received: from mailout-de.gmx.net ([10.1.76.20]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0MXTLc-1URYZJ001u-00WWID for <ietf-message-headers@ietf.org>; Thu, 14 Feb 2013 19:18:51 +0100
Received: (qmail invoked by alias); 14 Feb 2013 18:18:50 -0000
Received: from p5B233AC3.dip.t-dialin.net (EHLO netb.Speedport_W_700V) [91.35.58.195] by mail.gmx.net (mp020) with SMTP; 14 Feb 2013 19:18:50 +0100
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX19C9d5RcZNCMTQ1SjmVAU+q9YGc6cT+7GaDbkAwdu ql5v+7ALJRw2hp
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Graham Klyne <GK@ninebynine.org>
Date: Thu, 14 Feb 2013 19:18:50 +0100
Message-ID: <6u9qh814bhlc8cfm3961dirk41ncj78s88@hive.bjoern.hoehrmann.de>
References: <iljnh8d2cisqlsqvai0662974a0ei71qsn@hive.bjoern.hoehrmann.de> <6.2.5.6.2.20130213113549.0afcce60@resistor.net> <4613980CFC78314ABFD7F85CC3027721119A6FFE@IL-EX10.ad.checkpoint.com> <511BF66F.5070100@gmx.de> <6.2.5.6.2.20130213122642.0a997470@resistor.net> <511D0BB9.3010907@ninebynine.org>
In-Reply-To: <511D0BB9.3010907@ninebynine.org>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: ietf-message-headers@ietf.org, websec@ietf.org
Subject: Re: [Ietf-message-headers] [websec] 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: Thu, 14 Feb 2013 18:18:53 -0000

* Graham Klyne wrote:
>On 13/02/2013 20:32, SM wrote:
>> It's easier to fix the bug first.
>>
>> The following could be used:
>>
>>    "When a new entry is recorded in the permanent message header field
>>     registry, IANA will remove any corresponding entries (with the same
>>     field name and protocol) from the provisional registry."
>>
>> That avoids overlapping values.
>
>Just for the record:
>
>   http://www.rfc-editor.org/rfc/rfc3864.txt, section 4.3

Excellent. I gave up grepping for "same" after the first couple of hits.
I agree that Graham should just go ahead and ask IANA to remove the re-
dundant entry (I'd have done that, copying ietf-message-headers, had I
found the text above).
-- 
Björn Höhrmann · mailto:bjoern@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/ 
