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

Julian Reschke <julian.reschke@gmx.de> Sat, 08 January 2011 08:39 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf-message-headers@core3.amsl.com
Delivered-To: ietf-message-headers@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7E12A3A699E for <ietf-message-headers@core3.amsl.com>; Sat, 8 Jan 2011 00:39:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.158
X-Spam-Level:
X-Spam-Status: No, score=-104.158 tagged_above=-999 required=5 tests=[AWL=-2.159, BAYES_00=-2.599, J_CHICKENPOX_42=0.6, USER_IN_WHITELIST=-100]
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 dZMu6Miyvop4 for <ietf-message-headers@core3.amsl.com>; Sat, 8 Jan 2011 00:39:06 -0800 (PST)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id DC1553A698E for <ietf-message-headers@ietf.org>; Sat, 8 Jan 2011 00:39:05 -0800 (PST)
Received: (qmail invoked by alias); 08 Jan 2011 08:34:31 -0000
Received: from p508FD294.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.210.148] by mail.gmx.net (mp049) with SMTP; 08 Jan 2011 09:34:31 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/JU8RhosvJkz8wecMebLmfNl1PNwEif5xkfrQRMT 3Udu9E0+AzGRFf
Message-ID: <4D28218A.2020406@gmx.de>
Date: Sat, 08 Jan 2011 09:34:18 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
References: <4D280272.6090402@gmail.com>
In-Reply-To: <4D280272.6090402@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: iesg@ietf.org, ietf-message-headers@ietf.org, IETF Discussion <ietf@ietf.org>, httpbis Group <ietf-http-wg@w3.org>
Subject: Re: [Ietf-message-headers] Last Call Summary on draft-yevstifeyev-http-headers-not-recognized
X-BeenThere: ietf-message-headers@ietf.org
X-Mailman-Version: 2.1.9
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/listinfo/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: Sat, 08 Jan 2011 08:39:06 -0000

On 08.01.2011 07:21, Mykyta Yevstifeyev wrote:
> Hello all,
>
> This document summarizes the Last Call for
> draft-yevstifeyev-http-headers-not-recognized.
>
> The Last Call was requested on 11 December, 2010 by Alexey Melnikov and
> was announced on 13 November, 2010. The period of 32 days has been
> assigned for this Last Call, that ends on 14 January, 2011.
>
> The Last call has been requested for version -08. However during the
> Last Call 3 new versions appeared. The latest one is -11, submitted on 8
> January, 2011

If a draft changes three times during LC, there may be a problem. I 
encourage you to go back to the drawing board, and think hard(er about 
the feedback you got, in particular 
<http://lists.w3.org/Archives/Public/ietf-http-wg/2010OctDec/0645.html>.

I also mentioned at least once that in many frameworks this is 
essentially un-implementable, as different types of header fields are 
processed by different, independent layers in the code, and thus there's 
no way some part of the code will ever *know* which headers have been 
"processed". Do you think that this is not a problem?

> ...
>     * Syntax: Changed. Now is not /token**/but /1*VCAHR /for definition
>       of the name of the header.
> ...

Why?

Best regards, Julian