Re: [rtcweb] Uppercase question for RFC2119 words

Eliot Lear <lear@cisco.com> Wed, 30 March 2016 14:52 UTC

Return-Path: <lear@cisco.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 C913212D136; Wed, 30 Mar 2016 07:52:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.531
X-Spam-Level:
X-Spam-Status: No, score=-14.531 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 dHWRV_c60G78; Wed, 30 Mar 2016 07:52:51 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C0EA12D107; Wed, 30 Mar 2016 07:52:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3039; q=dns/txt; s=iport; t=1459349571; x=1460559171; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=KViRNqo1yEipDAfPwefUX3ZgHKn+YusRbHENoOzRVLE=; b=W37HycHLVPnRCRmPkzZ7Qu8zeM71vhQ7s5QESK02XhNM6s0fhK5VLDx6 Ag6eWJyOw2a+J5yOxDc2DdhQcX+0gbKxfC0MWqAr3B6URfFqSd99Zi1Qz /RdQNm5Vgk9H8FYThyP+oRFPDr4vUVDIgDVcIBXchivplfUk7ja6avBm8 8=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CoBADT5/tW/xbLJq1dwXuGDQKCFQEBA?= =?us-ascii?q?QEBAWUnhEIBAQQjVQEQCxgJFgsCAgkDAgECAUUGAQwIAQGII7AjkG0BAQEBAQE?= =?us-ascii?q?BAQEBAQEBAQEBAQEBDwiKY4E3hgeCVgEEl26DH4FmiQKBZodSI4UyjxBiggQND?= =?us-ascii?q?IFMOohvAQEB?=
X-IronPort-AV: E=Sophos;i="5.24,416,1454976000"; d="asc'?scan'208";a="634852468"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Mar 2016 14:52:49 +0000
Received: from [10.61.88.94] (ams3-vpn-dhcp6239.cisco.com [10.61.88.94]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id u2UEqmBS012426; Wed, 30 Mar 2016 14:52:48 GMT
Subject: Re: [rtcweb] Uppercase question for RFC2119 words
To: Adam Roach <adam@nostrum.com>, dcrocker@bbiw.net, Barry Leiba <barryleiba@computer.org>, "Scott O. Bradner" <sob@sobco.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> <56FBE6C3.6040506@nostrum.com>
From: Eliot Lear <lear@cisco.com>
Message-ID: <56FBE83F.8030609@cisco.com>
Date: Wed, 30 Mar 2016 16:52:47 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <56FBE6C3.6040506@nostrum.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="mi8EaJKACSISVAXPTqSlRPbR5lH702lpf"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/7SkHEDAcoidcalOZZ2vw9ZEE1YI>
Cc: "Heather Flanagan \(RFC Series Editor\)" <rse@rfc-editor.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>, IETF discussion list <ietf@ietf.org>, IESG <iesg@ietf.org>
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 14:52:53 -0000


On 3/30/16 4:46 PM, Adam Roach wrote:
> On 3/30/16 09:34, Dave Crocker wrote:
>> It's worth distinguishing between rules that make the writers more
>> comfortable, from rules that aid the reading efficacy in practical
>> terms. 
>
> Forcing implementors to read through the linguistic contortions
> authors make to avoid using perfectly good English words doesn't do
> them any favors. This odd game of charades -- "one syllable... sounds
> like... desk? wood?" -- does not aid clarity. Much the opposite.

Ok.  But neither should authors and editors be afraid of 2119.  Those
definitions are there to help both the reader and the writer, so that
intent is clear.

Eliot