Re: [rtcweb] Uppercase question for RFC2119 words

Mark Andrews <marka@isc.org> Wed, 30 March 2016 19:26 UTC

Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6C9412D8DA; Wed, 30 Mar 2016 12:26:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.911
X-Spam-Level:
X-Spam-Status: No, score=-6.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TIlXtHtBtdRw; Wed, 30 Mar 2016 12:26:43 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACCC612D8DD; Wed, 30 Mar 2016 12:19:29 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx.pao1.isc.org (Postfix) with ESMTPS id E2C6E3493BE; Wed, 30 Mar 2016 19:19:27 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id D24BB160044; Wed, 30 Mar 2016 19:19:27 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id BB5BC1600A3; Wed, 30 Mar 2016 19:19:27 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id IbPY4y66j2JX; Wed, 30 Mar 2016 19:19:27 +0000 (UTC)
Received: from rock.dv.isc.org (host224.200-117-110.telecom.net.ar [200.117.110.224]) by zmx1.isc.org (Postfix) with ESMTPSA id 51E4F160044; Wed, 30 Mar 2016 19:19:27 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 5AEBF45A5010; Thu, 31 Mar 2016 06:19:26 +1100 (EST)
To: Ole Jacobsen <olejacobsen@me.com>
From: Mark Andrews <marka@isc.org>
References: <20160320223116.8946.76840.idtracker@ietfa.amsl.com> <949EF20990823C4C85C18D59AA11AD8BADEAFFC7@FR712WXCHMBA11.zeu.alcatel-lucent.com> <CA+9kkMCsT43ZCSdq8gdKXu1k4pJgbf0ab5tE=dDiFfrTT2gtkA@mail.gmail.com> <949EF20990823C4C85C18D59AA11AD8BADEB0D16@FR712WXCHMBA11.zeu.alcatel-lucent.com> <56F79D05.8070004@alvestrand.no> <326E6502-28E5-4D09-BB99-4A5D80625EB0@stewe.org> <56F88E18.2060506@it.aoyama.ac.jp> <20160328104731.GO88304@verdi> <CALaySJ+hYMMsKE7Ws-NJbyqH55E-mQM-duTEcJGc0TWvTP88Ew@mail.gmail.com> <20160328132859.GP88304@verdi> <28975138-9EA1-4A9F-A6C0-BC1416B8EA44@sobco.com> <CALaySJJkNj2jfm0gJpuDzq8oFDjTNn-uQ5MHdmEOLwTiFZUyQQ@mail.gmail.com> <56FBDE33.5000706@nostrum.com> <56FBE3F2.10507@dcrocker.net> <CAKHUCzyhUwxvk3sQzZGHHZf-vh8B9wtp4DQ9qRcJ0sdi3o1UNw@mail.gmail.com> <56FC0441.5090207@nostrum.com> <CAJt_5Eicpb=01uAxRobO9cjUE578_xDacDxnOPO+RZUvyXLhew@mail.gmail.com> <alpine.OSX.2.01.1603301022030.6545@rabdullah.local>
Subject: Re: [rtcweb] Uppercase question for RFC2119 words
In-reply-to: Your message of "Wed, 30 Mar 2016 10:24:53 -0700." <alpine.OSX.2.01.1603301022030.6545@rabdullah.local>
Date: Thu, 31 Mar 2016 06:19:26 +1100
Message-Id: <20160330191926.5AEBF45A5010@rock.dv.isc.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/jcQieeoiu-TnntBR9ReBTa2rQnQ>
Cc: IETF discussion list <ietf@ietf.org>, "Heather Flanagan \(RFC Series Editor\)" <rse@rfc-editor.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>, IESG <iesg@ietf.org>, Barry Leiba <barryleiba@computer.org>, Dave Crocker <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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>
X-List-Received-Date: Wed, 30 Mar 2016 19:26:44 -0000

In message <alpine.OSX.2.01.1603301022030.6545@rabdullah.local>al>, Ole Jacobsen writes:
> 
> On Wed, 30 Mar 2016, Pat Thaler wrote:
> 
> > "must" has multiple meanings - it can indicate a requirement but it also
> > can be used to state the inevitable: e.g., "What goes up must come down."
> > 
> > Though in general, I'm not a fan of writing in all caps, "MUST" removes the
> > ambiguity indicating that it is to be understood as defined, rather than
> > having its regular English meaning.
> > 
> > All caps for the words also helps the requirement statements stand out when
> > scanning through a document.
> > 
> 
> +1
> 
> A few years ago I stayed in a B&B in England. The owner asked me: "Do 
> you require toast in the morning?" This particular use of "require"
> is not commonly used in the US (at least not on the West Coast) unless
> toast is some kind of medical substance.
> 
> All of which goes to show that words have different meaning and also 
> different USAGE, often location-based.

"table" can mean "to put aside" or to "make the focus of discussion"
or can be the actual physical item.

> Ole
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org