Re: [rtcweb] Uppercase question for RFC2119 words

Barry Leiba <barryleiba@computer.org> Wed, 30 March 2016 17:59 UTC

Return-Path: <barryleiba@gmail.com>
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 94F4B12D84E; Wed, 30 Mar 2016 10:59:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level:
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=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 (2048-bit key) header.d=gmail.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 HpeiOlk1R10R; Wed, 30 Mar 2016 10:59:31 -0700 (PDT)
Received: from mail-yw0-x22f.google.com (mail-yw0-x22f.google.com [IPv6:2607:f8b0:4002:c05::22f]) (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 D216912D849; Wed, 30 Mar 2016 10:59:30 -0700 (PDT)
Received: by mail-yw0-x22f.google.com with SMTP id h65so68099320ywe.0; Wed, 30 Mar 2016 10:59:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=jyFvXvplKgU7qcoSZUsr2gr/WGNOElarbzTb+KRIiS0=; b=VoMsCirnsRhtCg7NY7SDZYQdCkJFQHPTBcis1Bei7wxN1+d4mLTedwrngDK+lzs0Ln LxitiEY/wDCqTMHil06upULBXX3EfntBgQGriA0v5acnhDLvQ9QQfehIx+h20RnvVtnQ CqRzIJfDu9sqSfag9it9dmVr+iV2iIkSlznV1YStESSzYlOXXE9pPw/bpuJRu+hwsnCL drImV+QV1OUXORC7Dkr26DlNkz/RAb+o887f5bdWqShBwDW1KUDClKAkta2LXliFZSwo zzfsR780IZ42iYnuhqkP7pBddUOa0IByDHVhUssuqpXVHdXolfeexYQAN0oPrwZqOyJz q28w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=jyFvXvplKgU7qcoSZUsr2gr/WGNOElarbzTb+KRIiS0=; b=Pa461u20jyaPrwKvTFzPa31nj/Rphrjug/SB8ICjuKxF04kH4EB25PDUqryEaWyH0q oZTzyhyg67Ex7kCmnUyLCc7fD+5M/uffVrN+GG8BDNxNJgE1YhiK53awA2tdpCzr2b6H VSxX5UlYftbtNKxYqKsxIRaD3hRL/EYC/s2kVXnXkTD8C0ID0nR2/it0E9kak7yongEJ xgzsJPWhwFeUpZfRh0z5GkTxBwYHBytreI03Gtu6deC7MqRBIblvFH03hUcVqM3oN2V5 v+y4TOrTJhP+CxSC66HF7g3EOIkWstEIpSIEzQxaUuyH9B+ih2X0fbiP8UIhGzucKVxi y8GA==
X-Gm-Message-State: AD7BkJJghtkMmRDIzoycy/1agRDTyC75wL3dzZmMLNvfLx7aHwc+KVx0+zt0AhtFIoqKnrdN/pEhxKRlv2aY9Q==
MIME-Version: 1.0
X-Received: by 10.13.214.81 with SMTP id y78mr4744102ywd.227.1459360770068; Wed, 30 Mar 2016 10:59:30 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.83.28.67 with HTTP; Wed, 30 Mar 2016 10:59:29 -0700 (PDT)
In-Reply-To: <CAKHUCzyhUwxvk3sQzZGHHZf-vh8B9wtp4DQ9qRcJ0sdi3o1UNw@mail.gmail.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>
Date: Wed, 30 Mar 2016 13:59:29 -0400
X-Google-Sender-Auth: 01EzBFcKkqDR_9ty4yllqHS6rRQ
Message-ID: <CALaySJJkTEc3xPA_V3yHauq8vSM_hwG-1nQCAPNUThORqm-vpw@mail.gmail.com>
Subject: Re: [rtcweb] Uppercase question for RFC2119 words
From: Barry Leiba <barryleiba@computer.org>
To: Dave Cridland <dave@cridland.net>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/5htkJ4oFIG8ucA7ImeKp9tJ7s7Y>
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>, 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 17:59:32 -0000

>> That such a rule differs from natural English -- which does not typically
>> alter semantics based on case -- and that most readers of RFCs will not have
>> such detailed knowledge of RFC2119 nor read RFCs with the care such a rule
>> demands, my question BARRY and adam and EveryOne Else, is what makes anyone
>> think that such a rule must (MUST?) ensure proper reading of RFCs so as to
>> distinguish between normative portions and advisory portions?
>
> Sorry, I think that's nonsense. RFC 2119 and its capitalized keywords are
> well known to anyone reading any specifications, these days. I think we can
> actually assume a priori knowledge of RFC 2119, for the most part. What I
> think would be far more surprising is this notion that the keywords, noted
> and referenced in capitals, also have the same precise meaning and force
> when written normally.

I agree with the first and third sentences of what Dave Cridland said,
but I think we have to be a little careful about the second.  What I
think we can assume is an a priori knowledge of some of what 2119
says: that there are these capitalized key words that have special
meanings.  But it's quite clear from reviewing a lot of documents (one
of the fun things one gets to do as AD) that many writers do not know
how 2119 actually defines those.  I see significant misunderstandings
about "SHOULD" and "MAY" all the time, examples of which I can give
you if you like.  And one of my favourites is when someone used
"RECOMMENDED", I questioned it in a comment, and the response was,
"Yes, maybe we should switch that to 'SHOULD'."

As a complete side thing, I wonder how this all seems to
German-speakers, as German uses initial caps for all nouns.  I wonder
if anyone even notices if someone fails to do that.  I wonder if it
becomes puzzling, perhaps in some instances.

Barry