Re: [rtcweb] Uppercase question for RFC2119 words

Pat Thaler <pat.thaler@broadcom.com> Wed, 30 March 2016 17:12 UTC

Return-Path: <pat.thaler@broadcom.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEA3312D7FA for <rtcweb@ietfa.amsl.com>; Wed, 30 Mar 2016 10:12:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=broadcom.com
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 ZXdMk55u3gdL for <rtcweb@ietfa.amsl.com>; Wed, 30 Mar 2016 10:12:37 -0700 (PDT)
Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90DBA12D7F3 for <rtcweb@ietf.org>; Wed, 30 Mar 2016 10:12:37 -0700 (PDT)
Received: by mail-io0-x234.google.com with SMTP id g185so82630212ioa.2 for <rtcweb@ietf.org>; Wed, 30 Mar 2016 10:12:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=iX7Ph5cMdtru6SGA6VNG9811sKXkT8sNFqnlapzfJPc=; b=ADgifoDho5FBmLea69dHtxivhWC7VZWyGwvzxA/ayPBPbOMfk/QOJ4Sod5C1m7XAV3 i2zIJ/GS8c1qgeeROTxL3leGK49YXju39dnVOmlKzxXuzToFdkNN+vr+RZcpLIMxKBT7 lVmVuItcHMqFzrUQrzLgDzyoPdQ1qeAq3YD/8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=iX7Ph5cMdtru6SGA6VNG9811sKXkT8sNFqnlapzfJPc=; b=GP5jyqHB1ftBscsnAXb1wv99hMpWLzvJ7V4ENhgl7G4F1C2MokgwPRCcjd/JUHZDt6 2Sf8UZq9/ucVcDHS5Hlx899KyEyupDCm34KXQWLECkjKnDkwBPWPoBzqXdLtF23UKRRG 2Kr4CFiLN7u0zFkrvewVPAydcKTRRDPfoVLf1XLjn485v9bpnZSn4c7GnXt6ng22LDLZ r1Al09HzBSShOwKxXVVmAzl0XzANphv6KKOn4HX5naOPNFZFesdfO6c9ga93kLef2qRA yCPBAPr3Jsrg2XBW9vBqMeYwtW8zKQVjpfYKaCp8sq6RVQhJaAcVwV4r+iekVks7n/Dg VyCQ==
X-Gm-Message-State: AD7BkJJTgpaUyxpqRN3gvdjMbj7b3Wy/pOnrx1dexa9lmRlspDfQDe+V07z/IJ4Hyfl0clRlD9Am+DdD5IFtrMSp
MIME-Version: 1.0
X-Received: by 10.107.132.88 with SMTP id g85mr1465691iod.95.1459357956464; Wed, 30 Mar 2016 10:12:36 -0700 (PDT)
Received: by 10.36.130.1 with HTTP; Wed, 30 Mar 2016 10:12:36 -0700 (PDT)
In-Reply-To: <56FC0441.5090207@nostrum.com>
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>
Date: Wed, 30 Mar 2016 10:12:36 -0700
Message-ID: <CAJt_5Eicpb=01uAxRobO9cjUE578_xDacDxnOPO+RZUvyXLhew@mail.gmail.com>
From: Pat Thaler <pat.thaler@broadcom.com>
To: Adam Roach <adam@nostrum.com>
Content-Type: multipart/alternative; boundary="001a113f323c994804052f47401b"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/07Styj4JL5IhQhjpZLXdgYPwKCE>
X-Mailman-Approved-At: Wed, 30 Mar 2016 11:27:11 -0700
Cc: IETF discussion list <ietf@ietf.org>, "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>, Dave Cridland <dave@cridland.net>, "rtcweb@ietf.org" <rtcweb@ietf.org>, IESG <iesg@ietf.org>, Barry Leiba <barryleiba@computer.org>, Dave Crocker <dcrocker@bbiw.net>
Subject: Re: [rtcweb] Uppercase question for RFC2119 words
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2016 17:12:50 -0000

"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.

On Wed, Mar 30, 2016 at 9:52 AM, Adam Roach <adam@nostrum.com> wrote:

> On 3/30/16 11:32, Dave Cridland wrote:
>
>> Finally, I'd note in passing that "bill" and "Bill", "will" and "Will",
>> "heather" and "Heather", all have different semantics based on case - not
>> that this is particular relevant.
>>
>
> It's actually quite relevant, since it shows that we already have
> significant cases in which merely changing letter case can alter meaning
> nontrivially. There's a somewhat bawdy example of this that you can find by
> typing "capitalization matters" into Google Image Search. (Probably not
> safe to do in many workplaces).
>
> It kind of takes the wind out of arguments that people will miss the
> difference between letter cases.
>
> /a
>
>