Re: SHOULD vs MUST (was Re: Review of draft-ietf-geopriv-http-location-delivery-07)

Iljitsch van Beijnum <iljitsch@muada.com> Wed, 25 June 2008 07:30 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 33CF83A681D; Wed, 25 Jun 2008 00:30:26 -0700 (PDT)
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 41CA43A67F9 for <ietf@core3.amsl.com>; Wed, 25 Jun 2008 00:30:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.181
X-Spam-Level:
X-Spam-Status: No, score=-3.181 tagged_above=-999 required=5 tests=[AWL=-0.581, BAYES_00=-2.599]
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 7GLuLpJ7wiXe for <ietf@core3.amsl.com>; Wed, 25 Jun 2008 00:30:24 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 189473A6848 for <ietf@ietf.org>; Wed, 25 Jun 2008 00:30:23 -0700 (PDT)
Received: from [163.117.140.211] ([163.117.140.211]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m5P7UJr5021033 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 25 Jun 2008 09:30:20 +0200 (CEST) (envelope-from iljitsch@muada.com)
Message-Id: <C2F9EB05-3483-4684-9E19-775DF137F970@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Lawrence Conroy <lconroy@insensate.co.uk>
In-Reply-To: <9D9CF008-7350-4831-8F21-E08A0A7B255E@insensate.co.uk>
Mime-Version: 1.0 (Apple Message framework v924)
Subject: Re: SHOULD vs MUST (was Re: Review of draft-ietf-geopriv-http-location-delivery-07)
Date: Wed, 25 Jun 2008 09:30:14 +0200
References: <20080525020040.4DE5A5081A@romeo.rtfm.com> <F66D7286825402429571678A16C2F5EE03ADF950@zrc2hxm1.corp.nortel.com> <20080620195947.29D0B5081A@romeo.rtfm.com> <9D9CF008-7350-4831-8F21-E08A0A7B255E@insensate.co.uk>
X-Mailer: Apple Mail (2.924)
Cc: IETF Discussion <ietf@ietf.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/pipermail/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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

On 21 jun 2008, at 15:31, Lawrence Conroy wrote:

> the SHOULD means "do this unless...",
> and the last phrase covers the "unless".

> I had read 2119 to mean that a MUST was unconditional
> - do this or be non-complaint.
> Do you believe that MUST can have an "unless" clause?
> Doesn't this mean that any SHOULD with an explicit "unless" will
> need to be changed into a MUST - could you expand on this, please?

The difference is that with a SHOULD, the reader may come up with her  
own "unless".

Also note the difference between the two sides in a client-server  
protocol. I recently used SHOULD where I would have liked to use MUST  
but existing clients don't conform to the MUST so I used SHOULD to  
indicate that servers must support clients that don't have the feature.
_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf