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

Mykyta Yevstifeyev <evnikita2@gmail.com> Sun, 09 January 2011 06:20 UTC

Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E5EA23A6935 for <ietf@core3.amsl.com>; Sat, 8 Jan 2011 22:20:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.333
X-Spam-Level:
X-Spam-Status: No, score=-2.333 tagged_above=-999 required=5 tests=[AWL=-0.694, BAYES_00=-2.599, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_DNSWL_LOW=-1]
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 rdIWYtXb7fAm for <ietf@core3.amsl.com>; Sat, 8 Jan 2011 22:20:29 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id F0FA63A6930 for <ietf@ietf.org>; Sat, 8 Jan 2011 22:20:28 -0800 (PST)
Received: by bwz12 with SMTP id 12so18267827bwz.31 for <ietf@ietf.org>; Sat, 08 Jan 2011 22:22:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=Drx1E/Wt/qQ0d6aLU/5Qeu/80CuRG0nUP3iTnKv9Ql0=; b=hPhBdMTT1gziA+r0tR1zGmO5fKWAZiu0uBZvL/VDRMmAhtGczD4+ao5sJDpjNYv/C9 aTALLd/8olPrVZm39wKrQcjNvP8luXGZbvAXH4ArgHX6zxsLCk4TXZLGJ8Po1ZYmJE83 8SMIX0TXUJqIw9NAFLt6EBONZg0EvE0rVWQdU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=I+UgCwgxrMdAx5Vbe6LP9LJNVddMw1k225bo0N8kpWwB4hU+5FIGhpUyd6ij65W6To +oYYWPDZYJVajYNifrt0V32Dai7qw7r12hfvwA1cWD7dgOuBrq4ITQMcagc5mHFlrT0n PFeoTreOUq0qQRDhaaChkF/KA4XAEOYcOBPko=
Received: by 10.204.64.208 with SMTP id f16mr3918556bki.61.1294554156736; Sat, 08 Jan 2011 22:22:36 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id a17sm15057447bku.23.2011.01.08.22.22.35 (version=SSLv3 cipher=RC4-MD5); Sat, 08 Jan 2011 22:22:35 -0800 (PST)
Message-ID: <4D29543D.5060503@gmail.com>
Date: Sun, 09 Jan 2011 08:22:53 +0200
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: [Ietf-message-headers] Last Call Summary on draft-yevstifeyev-http-headers-not-recognized
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>
In-Reply-To: <4D289DC9.70208@gmx.de>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>, httpbis Group <ietf-http-wg@w3.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Jan 2011 06:20:37 -0000

08.01.2011 19:24, Julian Reschke wrote:
> On 08.01.2011 16:58, Mykyta Yevstifeyev wrote:
>> ...
>> Many LC comments referred to that it would be uninteresting and useless
>> to implement this.  Maybe one of them seems the most interesting for me
>> - it said about the 'Warning' headers that should be used in this
>> occasion.  This, IMO, is one of the most suitable for me and this
>> technology.  But if we implement this now using Warning, one problem is
> > ...
>
> I don't see how (a) using HTTP warnings would resolve the problems 
> other people see, (b) how the use of warnings makes this proposal any 
> better, nor (c) that warnings are actually applicable here (see 
> <http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p6-cache-12.html#rfc.section.3.6>).
At the moment no any, and I want to define a new one.  In spite of this 
there is no any registry (see below).  I ask the WG for opinion on 
should we create it or not?
>
>> 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?
>
>> ...
>
> Best regards, Julian
>