IETF Logo Mail Archive

Re: SHOULD vs MUST case sensitivity

"Randy Presuhn" <randy_presuhn@mindspring.com> Sun, 29 June 2008 23:44 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 742BB3A68FB; Sun, 29 Jun 2008 16:44:46 -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 047543A68FB for <ietf@core3.amsl.com>; Sun, 29 Jun 2008 16:44:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.042
X-Spam-Level:
X-Spam-Status: No, score=-2.042 tagged_above=-999 required=5 tests=[AWL=0.558, 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 xrLlVpv-+w22 for <ietf@core3.amsl.com>; Sun, 29 Jun 2008 16:44:45 -0700 (PDT)
Received: from elasmtp-masked.atl.sa.earthlink.net (elasmtp-masked.atl.sa.earthlink.net [209.86.89.68]) by core3.amsl.com (Postfix) with ESMTP id 3483C3A6835 for <ietf@ietf.org>; Sun, 29 Jun 2008 16:44:45 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=LmxfwMDN/Zy1B/vQ67Kal0Elnxv18KnSdXZP/P1jvt75jgb+jaVLmFIUIGbzbY3F; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:x-mimeole:X-ELNK-Trace:X-Originating-IP;
Received: from [69.3.145.142] (helo=oemcomputer) by elasmtp-masked.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1KD6Zj-0004CY-0Y for ietf@ietf.org; Sun, 29 Jun 2008 19:44:55 -0400
Message-ID: <00cd01c8da42$592bd280$6801a8c0@oemcomputer>
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: IETF Discussion <ietf@ietf.org>
References: <20080525020040.4DE5A5081A@romeo.rtfm.com><F66D7286825402429571678A16C2F5EE03ADF950@zrc2hxm1.corp.nortel.com><20080620195947.29D0B5081A@romeo.rtfm.com><9D9CF008-7350-4831-8F21-E08A0A7B255E@insensate.co.uk><7706.1214216391.855029@peirce.dave.cridland.net><g3ror8$2b9$1@ger.gmane.org><900B2F8D-5960-4277-9DBC-E59A05F1CFBA@cisco.com><48623304.1050008@employees.org><2D990430F5F5D3C7984BDFDF@p3.JCK.COM><48627A42.6030907@employees.org><4862920D.4060003@dcrocker.net><941D5DCD8C42014FAF70FB7424686DCF034FC969@eusrcmw721.eamcs.ericsson.se><48657683.2050608@dcrocker.net><Pine.LNX.4.64.0806271844290.22369@shell4.bayarea.net> <DBE1F9D4-FA3E-4A8F-A90C-8095AEA809DA@muada.com>
Subject: Re: SHOULD vs MUST case sensitivity
Date: Sun, 29 Jun 2008 16:46:26 -0700
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
x-mimeole: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888a63b7957ab9b23b39da69c568e45c31d5a1ac8fd86294cf1350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 69.3.145.142
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-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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Hi -

> From: "Iljitsch van Beijnum" <iljitsch@muada.com>
> To: "C. M. Heard" <heard@pobox.com>
> Cc: "IETF Discussion" <ietf@ietf.org>
> Sent: Saturday, June 28, 2008 1:57 PM
> Subject: Re: SHOULD vs MUST case sensitivity
...
> Are you saying that according to RFC 2119 "SHOULD" means something  
> different than "should"?
> 
> In what universe does that make sense?
...

One in which when the photocopier's paper jam light goes, the 
operator SHOULD open the cover and remove any crumpled
pieces of paper, which should resolve the problem.

These are very distinct senses of the word - one indicating the
desirability of a course of action, the other indicating the likelihood
of a particular result.  Only for the former does any kind of "normative"
semantic make sense.

Randy

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email