RE: NEW ISSUE: Define "ought to"
Mike Bishop <Michael.Bishop@microsoft.com> Tue, 30 July 2013 19:48 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 0772011E811B for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 30 Jul 2013 12:48:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.466
X-Spam-Level:
X-Spam-Status: No, score=-7.466 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, UNRESOLVED_TEMPLATE=3.132]
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 I4p05hFnNMuQ for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 30 Jul 2013 12:48:49 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id E562D11E8116 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 30 Jul 2013 12:48:48 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1V4FtV-000089-CH for ietf-http-wg-dist@listhub.w3.org; Tue, 30 Jul 2013 19:47:41 +0000
Resent-Date: Tue, 30 Jul 2013 19:47:41 +0000
Resent-Message-Id: <E1V4FtV-000089-CH@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <Michael.Bishop@microsoft.com>) id 1V4FtJ-0008U5-3E for ietf-http-wg@listhub.w3.org; Tue, 30 Jul 2013 19:47:29 +0000
Received: from mail-db8lp0188.outbound.messaging.microsoft.com ([213.199.154.188] helo=db8outboundpool.messaging.microsoft.com) by maggie.w3.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from <Michael.Bishop@microsoft.com>) id 1V4FtH-0007DM-Nc for ietf-http-wg@w3.org; Tue, 30 Jul 2013 19:47:29 +0000
Received: from mail91-db8-R.bigfish.com (10.174.8.250) by DB8EHSOBE003.bigfish.com (10.174.4.66) with Microsoft SMTP Server id 14.1.225.22; Tue, 30 Jul 2013 19:47:01 +0000
Received: from mail91-db8 (localhost [127.0.0.1]) by mail91-db8-R.bigfish.com (Postfix) with ESMTP id 6C229DA012B for <ietf-http-wg@w3.org>; Tue, 30 Jul 2013 19:47:01 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:131.107.125.8; KIP:(null); UIP:(null); IPV:NLI; H:TK5EX14MLTC104.redmond.corp.microsoft.com; RD:autodiscover.service.exchange.microsoft.com; EFVD:NLI
X-SpamScore: 0
X-BigFish: VS0(zz98dI9371I936eIc85fh542I1432Ic1dM26b7nzz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1d7338h1de098h17326ah18c673h1de096h8275bh8275dh1de097hz2fh2a8h683h839hd24hf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h1b0ah1bceh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh17ej9a9j1155h)
Received-SPF: pass (mail91-db8: domain of microsoft.com designates 131.107.125.8 as permitted sender) client-ip=131.107.125.8; envelope-from=Michael.Bishop@microsoft.com; helo=TK5EX14MLTC104.redmond.corp.microsoft.com ; icrosoft.com ;
X-Forefront-Antispam-Report-Untrusted: CIP:157.56.240.21; KIP:(null); UIP:(null); (null); H:BL2PRD0310HT002.namprd03.prod.outlook.com; R:internal; EFV:INT
Received: from mail91-db8 (localhost.localdomain [127.0.0.1]) by mail91-db8 (MessageSwitch) id 137521361977945_22711; Tue, 30 Jul 2013 19:46:59 +0000 (UTC)
Received: from DB8EHSMHS025.bigfish.com (unknown [10.174.8.228]) by mail91-db8.bigfish.com (Postfix) with ESMTP id 0441CD8004A for <ietf-http-wg@w3.org>; Tue, 30 Jul 2013 19:46:59 +0000 (UTC)
Received: from TK5EX14MLTC104.redmond.corp.microsoft.com (131.107.125.8) by DB8EHSMHS025.bigfish.com (10.174.4.35) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 30 Jul 2013 19:46:56 +0000
Received: from CO9EHSOBE028.bigfish.com (157.54.51.80) by mail.microsoft.com (157.54.79.159) with Microsoft SMTP Server (TLS) id 14.3.136.1; Tue, 30 Jul 2013 19:46:39 +0000
Received: from mail182-co9-R.bigfish.com (10.236.132.245) by CO9EHSOBE028.bigfish.com (10.236.130.91) with Microsoft SMTP Server id 14.1.225.22; Tue, 30 Jul 2013 19:44:29 +0000
Received: from mail182-co9 (localhost [127.0.0.1]) by mail182-co9-R.bigfish.com (Postfix) with ESMTP id E64418401B5 for <ietf-http-wg@w3.org.FOPE.CONNECTOR.OVERRIDE>; Tue, 30 Jul 2013 19:44:28 +0000 (UTC)
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(13464003)(377454003)(377424004)(199002)(189002)(51704005)(31014004)(24454002)(19580395003)(47446002)(4396001)(54356001)(77982001)(74876001)(83322001)(46102001)(80976001)(79102001)(76482001)(33646001)(19580405001)(63696002)(54316002)(59766001)(65816001)(19580385001)(83072001)(56816003)(53806001)(74366001)(49866001)(74706001)(77096001)(31966008)(16406001)(81342001)(19300405004)(81542001)(74502001)(74662001)(76576001)(80022001)(56776001)(50986001)(51856001)(47736001)(47976001)(76786001)(69226001)(15202345003)(74316001)(16236675002)(76796001)(99114002)(3826001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BY2PR03MB025; H:BY2PR03MB025.namprd03.prod.outlook.com; CLIP:2001:4898:80e0:ed43::e4; RD:InfoNoRecords; A:1; MX:1; LANG:en;
Received: from mail182-co9 (localhost.localdomain [127.0.0.1]) by mail182-co9 (MessageSwitch) id 1375213466639196_26210; Tue, 30 Jul 2013 19:44:26 +0000 (UTC)
Received: from CO9EHSMHS029.bigfish.com (unknown [10.236.132.238]) by mail182-co9.bigfish.com (Postfix) with ESMTP id 97882D8004A; Tue, 30 Jul 2013 19:44:26 +0000 (UTC)
Received: from BL2PRD0310HT002.namprd03.prod.outlook.com (157.56.240.21) by CO9EHSMHS029.bigfish.com (10.236.130.39) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 30 Jul 2013 19:44:24 +0000
Received: from BY2PR03MB025.namprd03.prod.outlook.com (10.255.240.39) by BL2PRD0310HT002.namprd03.prod.outlook.com (10.255.97.37) with Microsoft SMTP Server (TLS) id 14.16.341.1; Tue, 30 Jul 2013 19:44:12 +0000
Received: from BY2PR03MB025.namprd03.prod.outlook.com (10.255.240.39) by BY2PR03MB025.namprd03.prod.outlook.com (10.255.240.39) with Microsoft SMTP Server (TLS) id 15.0.731.16; Tue, 30 Jul 2013 19:43:52 +0000
Received: from BY2PR03MB025.namprd03.prod.outlook.com ([169.254.8.202]) by BY2PR03MB025.namprd03.prod.outlook.com ([169.254.8.202]) with mapi id 15.00.0731.000; Tue, 30 Jul 2013 19:43:52 +0000
From: Mike Bishop <Michael.Bishop@microsoft.com>
To: Julian Reschke <julian.reschke@gmx.de>, cowwoc <cowwoc@bbs.darktech.org>
CC: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Thread-Topic: NEW ISSUE: Define "ought to"
Thread-Index: AQHOjTiycGt01E2HEEK07VX0t7v2MJl9WNmAgAAJbgCAAC3SAIAADqBQ
Date: Tue, 30 Jul 2013 19:43:51 +0000
Message-ID: <78425d7972bb4d8f8d0ecbf1df9b55ee@BY2PR03MB025.namprd03.prod.outlook.com>
References: <51F7D951.3050204@bbs.darktech.org> <51F7DBF5.3030403@gmx.de> <51F7E3DE.4020804@bbs.darktech.org> <51F80A4E.9040407@gmx.de>
In-Reply-To: <51F80A4E.9040407@gmx.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [2001:4898:80e0:ed43::e4]
x-forefront-prvs: 0923977CCA
Content-Type: multipart/alternative; boundary="_000_78425d7972bb4d8f8d0ecbf1df9b55eeBY2PR03MB025namprd03pro_"
MIME-Version: 1.0
X-OrganizationHeadersPreserved: BY2PR03MB025.namprd03.prod.outlook.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%W3.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%BBS.DARKTECH.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%GMX.DE$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-CrossPremisesHeadersPromoted: TK5EX14MLTC104.redmond.corp.microsoft.com
X-CrossPremisesHeadersFiltered: TK5EX14MLTC104.redmond.corp.microsoft.com
X-OriginatorOrg: microsoft.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Received-SPF: pass client-ip=213.199.154.188; envelope-from=Michael.Bishop@microsoft.com; helo=db8outboundpool.messaging.microsoft.com
X-W3C-Hub-Spam-Status: No, score=-0.8
X-W3C-Hub-Spam-Report: HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.544, SPF_PASS=-0.001, UNRESOLVED_TEMPLATE=0.716
X-W3C-Scan-Sig: maggie.w3.org 1V4FtH-0007DM-Nc d67861e3b7b97d9ec854ea70718a1edc
X-Original-To: ietf-http-wg@w3.org
Subject: RE: NEW ISSUE: Define "ought to"
Archived-At: <http://www.w3.org/mid/78425d7972bb4d8f8d0ecbf1df9b55ee@BY2PR03MB025.namprd03.prod.outlook.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/18985
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>
If I'm following you correctly, this could be restated: * "MAY" - Strictly at your discretion based on what matters to you * "ought to" - Or your implementation will be less effective/efficient than it could be, without hurting anyone else * "SHOULD" - Or your implementation will cause peers / the network to suffer for your stupidity * "MUST" - Or you won't be able to interoperate with anyone -----Original Message----- From: Julian Reschke [mailto:julian.reschke@gmx.de] Sent: Tuesday, July 30, 2013 11:48 AM To: cowwoc Cc: ietf-http-wg@w3.org Subject: Re: NEW ISSUE: Define "ought to" On 2013-07-30 18:03, cowwoc wrote: > Julian, > > I understand the "legal" difference between the two but your > reply didn't actually explain the benefit of using "ought to" instead > of "SHOULD" (especially in light of the fact that the former causes > confusion). > > Gili The reason we don't use SHOULD is that BCP14 keywords SHOULD be used sparingly: Imperatives of the type defined in this memo must be used with care and sparingly. In particular, they MUST only be used where it is actually required for interoperation or to limit behavior which has potential for causing harm (e.g., limiting retransmisssions) For example, they must not be used to try to impose a particular method on implementors where the method is not required for interoperability. Best regards, Julian
- Re: NEW ISSUE: Define "ought to" cowwoc
- NEW ISSUE: Define "ought to" cowwoc
- Re: NEW ISSUE: Define "ought to" cowwoc
- Re: NEW ISSUE: Define "ought to" Julian Reschke
- Re: NEW ISSUE: Define "ought to" cowwoc
- Re: NEW ISSUE: Define "ought to" cowwoc
- Re: NEW ISSUE: Define "ought to" Julian Reschke
- Re: NEW ISSUE: Define "ought to" Julian Reschke
- RE: NEW ISSUE: Define "ought to" Mike Bishop
- Re: NEW ISSUE: Define "ought to" Julian Reschke
- Re: NEW ISSUE: Define "ought to" cowwoc
- Re: NEW ISSUE: Define "ought to" Julian Reschke
- Re: NEW ISSUE: Define "ought to" Willy Tarreau
- Re: NEW ISSUE: Define "ought to" Willy Tarreau
- Re: NEW ISSUE: Define "ought to" Julian Reschke
- Re: NEW ISSUE: Define "ought to" Dave Crocker
- Re: NEW ISSUE: Define "ought to" Martin Thomson
- Re: NEW ISSUE: Define "ought to" cowwoc
- Re: NEW ISSUE: Define "ought to" Dave Crocker
- Re: NEW ISSUE: Define "ought to" Julian Reschke
- Re: NEW ISSUE: Define "ought to" Dave Crocker
- Re: NEW ISSUE: Define "ought to" Willy Tarreau
- Re: NEW ISSUE: Define "ought to" Yoav Nir
- Re: NEW ISSUE: Define "ought to" Eliot Lear
- Re: NEW ISSUE: Define "ought to" Mark Nottingham
- Re: NEW ISSUE: Define "ought to" Michael Sweet
- Re: NEW ISSUE: Define "ought to" Eliot Lear
- Re: NEW ISSUE: Define "ought to" cowwoc