Re: NEW ISSUE: Define "ought to"

cowwoc <cowwoc@bbs.darktech.org> Tue, 30 July 2013 22:10 UTC

Return-Path: <ietf-http-wg-request@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7981E21F999D for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 30 Jul 2013 15:10:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.286
X-Spam-Level:
X-Spam-Status: No, score=-9.286 tagged_above=-999 required=5 tests=[AWL=1.313, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c2xmA7htL0zp for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 30 Jul 2013 15:10:05 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id EA3D421F9998 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 30 Jul 2013 15:10:04 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1V4I6g-0002vT-71 for ietf-http-wg-dist@listhub.w3.org; Tue, 30 Jul 2013 22:09:26 +0000
Resent-Date: Tue, 30 Jul 2013 22:09:26 +0000
Resent-Message-Id: <E1V4I6g-0002vT-71@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <cowwoc@bbs.darktech.org>) id 1V4I6V-0002oN-AQ for ietf-http-wg@listhub.w3.org; Tue, 30 Jul 2013 22:09:15 +0000
Received: from mail-yh0-f46.google.com ([209.85.213.46]) by maggie.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <cowwoc@bbs.darktech.org>) id 1V4I6T-0002uY-UM for ietf-http-wg@w3.org; Tue, 30 Jul 2013 22:09:15 +0000
Received: by mail-yh0-f46.google.com with SMTP id i57so1784821yha.5 for <ietf-http-wg@w3.org>; Tue, 30 Jul 2013 15:08:47 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=aVU4AELzbvUcdM87VGM7/rit54TsxLWg10N5DujYRuc=; b=HgXN+tnL4+lbMq4KO1Um1+B1bbnOuDpcUGITI10+74X47ijwpxRXGofpBumCmPskOK +rnPAANUQmXfAqM9ZWWA9Zx3dhaPnYDsFdYKpYQwJ2auzktkLliqII4loq/xof3Tqux0 bi4ev0tHq76w4BfjpoqG2m8bpxzpUHwigfhJLGjda8nUCb07h3pFf+uf8/tb4kp2hMAS jvOvKJiOgvhTkfMHZuyoGsT+vbqFFUtUDvUE12geqZCkxrYN/7Taq/VQR7/97w24ndfr 8WFDakwr0HR/K2DxogLnQ+hwUGw2R+q1ox0rkhuIsCi2HVCCJ3b0Rxx0O8XxsPrJ/GFD 8IWw==
X-Received: by 10.236.131.50 with SMTP id l38mr30905956yhi.149.1375222127367; Tue, 30 Jul 2013 15:08:47 -0700 (PDT)
Received: from [192.168.1.100] (206-248-171-209.dsl.teksavvy.com. [206.248.171.209]) by mx.google.com with ESMTPSA id d68sm94277727yhk.7.2013.07.30.15.08.45 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 30 Jul 2013 15:08:46 -0700 (PDT)
Message-ID: <51F83969.5060801@bbs.darktech.org>
Date: Tue, 30 Jul 2013 18:08:41 -0400
From: cowwoc <cowwoc@bbs.darktech.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Willy Tarreau <w@1wt.eu>
CC: Julian Reschke <julian.reschke@gmx.de>, Mike Bishop <Michael.Bishop@microsoft.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
References: <51F7D951.3050204@bbs.darktech.org> <51F7DBF5.3030403@gmx.de> <51F7E3DE.4020804@bbs.darktech.org> <51F80A4E.9040407@gmx.de> <78425d7972bb4d8f8d0ecbf1df9b55ee@BY2PR03MB025.namprd03.prod.outlook.com> <51F81A97.1090309@gmx.de> <20130730214557.GA7351@1wt.eu>
In-Reply-To: <20130730214557.GA7351@1wt.eu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQl1De1O49KSrGfZBaIWDi8Ayh3WdgWzGQpB+51qZmysXCCbsaZijd9Z9fX8mDL/o4bW2plW
Received-SPF: none client-ip=209.85.213.46; envelope-from=cowwoc@bbs.darktech.org; helo=mail-yh0-f46.google.com
X-W3C-Hub-Spam-Status: No, score=-3.7
X-W3C-Hub-Spam-Report: AWL=-3.009, RCVD_IN_DNSWL_LOW=-0.7
X-W3C-Scan-Sig: maggie.w3.org 1V4I6T-0002uY-UM 1e57f56a83a2c776668cf9e5ce515214
X-Original-To: ietf-http-wg@w3.org
Subject: Re: NEW ISSUE: Define "ought to"
Archived-At: <http://www.w3.org/mid/51F83969.5060801@bbs.darktech.org>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/18991
X-Loop: ietf-http-wg@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-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

On 30/07/2013 5:45 PM, Willy Tarreau wrote:
> I'd say that "ought to" here in the HTTP spect is generally a good friend's
> advice from some other implementors that got trapped and know how to avoid
> this. There's nothing normative in what follows "ought to" so those who
> won't follow it will not cause harm and might only suffer themselves.
> SHOULD is a MUST with an exception if you know you can safely ignore it.

     That is an excellent explanation. Please consider adding it to 
section 1.1.

Thanks,
Gili