Re: [Ietf-message-headers] Last Call Summary on draft-yevstifeyev-http-headers-not-recognized

Ben Niven-Jenkins <ben@niven-jenkins.co.uk> Sun, 09 January 2011 11:04 UTC

Return-Path: <ietf-http-wg-request@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@core3.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EF5723A696D for <ietfarch-httpbisa-archive-bis2Juki@core3.amsl.com>; Sun, 9 Jan 2011 03:04:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.536
X-Spam-Level:
X-Spam-Status: No, score=-6.536 tagged_above=-999 required=5 tests=[AWL=4.063, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RnPv2btu4mp0 for <ietfarch-httpbisa-archive-bis2Juki@core3.amsl.com>; Sun, 9 Jan 2011 03:04:12 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by core3.amsl.com (Postfix) with ESMTP id 1C6363A696A for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sun, 9 Jan 2011 03:04:11 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.69) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1Pbt5h-0007Kn-9n for ietf-http-wg-dist@listhub.w3.org; Sun, 09 Jan 2011 11:05:41 +0000
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.69) (envelope-from <ben@niven-jenkins.co.uk>) id 1Pbt48-0006d8-VH for ietf-http-wg@listhub.w3.org; Sun, 09 Jan 2011 11:04:04 +0000
Received: from mailex.mailcore.me ([94.136.40.64]) by lisa.w3.org with esmtp (Exim 4.69) (envelope-from <ben@niven-jenkins.co.uk>) id 1Pbt44-0001d1-7e for ietf-http-wg@w3.org; Sun, 09 Jan 2011 11:04:03 +0000
Received: from cpc22-cmbg15-2-0-cust173.5-4.cable.virginmedia.com ([86.27.176.174] helo=[192.168.0.205]) by mail10.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1Pbt3d-0000dR-2A; Sun, 09 Jan 2011 11:03:33 +0000
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="us-ascii"
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <4D298BDD.40209@gmx.de>
Date: Sun, 09 Jan 2011 11:03:31 +0000
Cc: Mykyta Yevstifeyev <evnikita2@gmail.com>, httpbis Group <ietf-http-wg@w3.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <5139EF8D-DA8B-4DB9-9172-2303C8DFC394@niven-jenkins.co.uk>
References: <4D280272.6090402@gmail.com> <4D28218A.2020406@gmx.de> <4D283A42.3080303@gmail.com> <4D2847E1.9090004@gmx.de> <4D288998.9020001@gmail.com> <4D289DC9.70208@gmx.de> <4D29543D.5060503@gmail.com> <4D298BDD.40209@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.1082)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Received-SPF: none
X-SPF-Guess: pass
X-W3C-Hub-Spam-Status: No, score=-2.6
X-W3C-Hub-Spam-Report: BAYES_00=-2.599
X-W3C-Scan-Sig: lisa.w3.org 1Pbt44-0001d1-7e 122c6768d04debfa54bf36901c681855
X-Original-To: ietf-http-wg@w3.org
Subject: Re: [Ietf-message-headers] Last Call Summary on draft-yevstifeyev-http-headers-not-recognized
Archived-At: <http://www.w3.org/mid/5139EF8D-DA8B-4DB9-9172-2303C8DFC394@niven-jenkins.co.uk>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/10026
X-Loop: ietf-http-wg@w3.org
Sender: ietf-http-wg-request@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
Resent-Message-Id: <E1Pbt5h-0007Kn-9n@frink.w3.org>
Resent-Date: Sun, 09 Jan 2011 11:05:41 +0000

On 9 Jan 2011, at 10:20, Julian Reschke wrote:
> On 09.01.2011 07:22, Mykyta Yevstifeyev wrote:
>> 08.01.2011 19:24, Julian Reschke wrote:
>>> On 08.01.2011 16:58, Mykyta Yevstifeyev wrote:
>>>> absence of IANA registry for Warning codes, such as for Status codes.
>>>> As this message is now sent to httpbis WG mailing list, I ask you if
>>>> there is a sense in creating such registry?
>>> 
>>> We might create a registry when/if when there are actually requests
>>> for new Warning values.
>> However no one can actually do this since there is no such registry. So
>> I think there should be the appropriate registry. Will the WG agree with
>> me?
> 
> See above: no, *I* don't think we should create a registry at this point.

Agreed, we don't need to create a registry until we have something to put in it.

If someone writes an I-D that creates additional Warning codes, that same I-D can:
1) Note that a registry needs to be created, or
2) Suggest creating the registry and contain the relevant IANA guidelines etc.

In the case of (1) what I would expect is *if* the I-D progresses then at some point in the future before it is sent to IESG, either
a) a separate I-D is produced & progressed in parallel to create the registry and IANA guidelines
b) the IANA guidelines etc are put in the original I-D (essentially the same as (2) above but the original I-D author does not expend time writing IANA guidelines before receiving feedback on their actual proposal).

Ben