Re: [hybi] Ticket#1 Http Compliance

Greg Wilkins <gregw@webtide.com> Thu, 13 May 2010 08:32 UTC

Return-Path: <gregw@webtide.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D11103A6AF3 for <hybi@core3.amsl.com>; Thu, 13 May 2010 01:32:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.437
X-Spam-Level:
X-Spam-Status: No, score=-0.437 tagged_above=-999 required=5 tests=[AWL=-0.252, BAYES_40=-0.185]
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 QA6gHGw4QByi for <hybi@core3.amsl.com>; Thu, 13 May 2010 01:32:02 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id A71C03A6C65 for <hybi@ietf.org>; Thu, 13 May 2010 01:28:32 -0700 (PDT)
Received: by wwb28 with SMTP id 28so760459wwb.31 for <hybi@ietf.org>; Thu, 13 May 2010 01:28:19 -0700 (PDT)
Received: by 10.227.154.83 with SMTP id n19mr7970154wbw.147.1273739299286; Thu, 13 May 2010 01:28:19 -0700 (PDT)
Received: from [192.168.0.100] (host116-234-static.43-88-b.business.telecomitalia.it [88.43.234.116]) by mx.google.com with ESMTPS id y22sm7315301wby.23.2010.05.13.01.28.18 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 13 May 2010 01:28:18 -0700 (PDT)
Message-ID: <4BEBB81F.4010506@webtide.com>
Date: Thu, 13 May 2010 10:28:15 +0200
From: Greg Wilkins <gregw@webtide.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: "hybi@ietf.org" <hybi@ietf.org>
References: <4BEAB021.5030600@webtide.com> <op.vcmr0hge64w2qv@annevk-t60>
In-Reply-To: <op.vcmr0hge64w2qv@annevk-t60>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Subject: Re: [hybi] Ticket#1 Http Compliance
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 May 2010 08:32:02 -0000

Anne van Kesteren wrote:
> On Wed, 12 May 2010 15:41:53 +0200, Greg Wilkins <gregw@webtide.com> wrote:
>> Attached is a proposed diff (from me as individual - not as
>> requirements editor) to the requirements document for HTTP Compliance.
> 
> I think it would be good if proposals for new requirements indicated
> that to satisfy them changes to the draft would be required. This
> especially has been a long-standing debate and having it as a debate on
> requirements does not seem like a good idea to me.


Anne,

I believe that the intent of the chairs to focus the discussion on
requirements is exactly to help resolve such long standing
debates as HTTP compliance.

If some believe that HTTP compliance is a requirement, while others
think that it is not, then we will never reach agreement on a mechanism
that breaks HTTP compliance.    We first need to resolve if it
is a requirement or not.

It may be that consensus is that we don't need to be HTTP compliant and
then the next time I argue "but you can't do that because it is
not HTTP compliant", I can be politely told that it is not a
requirement and thus we can get on with the rest of the protocol.


regards