Re: [Int-dir] Intdir early review of draft-ietf-ipwave-ipv6-over-80211ocb-34 - KeyWords BCP 14 text

Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 08 April 2019 11:10 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: int-dir@ietfa.amsl.com
Delivered-To: int-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6D7C1200D7; Mon, 8 Apr 2019 04:10:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level:
X-Spam-Status: No, score=-2.633 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665] autolearn=ham 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 UAAkuy0v98Vu; Mon, 8 Apr 2019 04:10:13 -0700 (PDT)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69D5012006D; Mon, 8 Apr 2019 04:10:13 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x38BA9Ti023979; Mon, 8 Apr 2019 13:10:09 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 8B57D203864; Mon, 8 Apr 2019 13:10:09 +0200 (CEST)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 64853203C1F; Mon, 8 Apr 2019 13:10:09 +0200 (CEST)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x38BA9dL018628; Mon, 8 Apr 2019 13:10:09 +0200
To: Pascal Thubert <pthubert@cisco.com>
Cc: int-dir@ietf.org, ietf@ietf.org, its@ietf.org, draft-ietf-ipwave-ipv6-over-80211ocb.all@ietf.org
References: <155169869045.5118.3508360720339540639@ietfa.amsl.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <31dd2bba-a7f2-e72d-4ef3-6ad4094f46a6@gmail.com>
Date: Mon, 08 Apr 2019 13:10:09 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <155169869045.5118.3508360720339540639@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-dir/qCzgBo0tunf981bT1gR_Mr-FnKQ>
Subject: Re: [Int-dir] Intdir early review of draft-ietf-ipwave-ipv6-over-80211ocb-34 - KeyWords BCP 14 text
X-BeenThere: int-dir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This list is for discussion between the members of the Internet Area directorate." <int-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-dir>, <mailto:int-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-dir/>
List-Post: <mailto:int-dir@ietf.org>
List-Help: <mailto:int-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-dir>, <mailto:int-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Apr 2019 11:10:16 -0000

Le 04/03/2019 à 12:24, Pascal Thubert a écrit :
> Reviewer: Pascal Thubert
> Review result: Not Ready
> 
[...]
> BCP 14 text:
> 
> Suggest to use this text:
> “
>     The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>     "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
>     "OPTIONAL" in this document are to be interpreted as described in
>     https://tools.ietf.org/html/bcp14 https://tools.ietf.org/html/bcp14
>     [https://tools.ietf.org/html/rfc2119][RFC8174] when, and only when, they
>     appear in all capitals, as shown here.
> 
> “

I will add it, thank you.  I want to be up to date with most recent specs.

But here are my worries about it for what is worth:

- I dont understand though why the need to say 'capitals' when in 
CAPITALS is it written.

- I thought that a BCP document was just one RFC.  Here we seem to be 
talking about BCP-14 being both RFC2119 and RFC8174.

A google search on BCP-14 hits first on RFC 2119, and a document called 
'bcp14' (not on RFC8174). https://tools.ietf.org/html/bcp14

The second hit is a page at RFC Editor which points to a "Canonical URL" 
towards https://www.rfc-editor.org/bcp/bcp14.txt which does not talk 
about RFC8174 either.

It then points to https://www.rfc-editor.org/refs/ref-bcp14.txt
That ref points back to a web page telling the "Canonical URL".

- finally, the text ends with 'as shown here', which invites my reading 
to think that what follows needs to be understood with these capitals. 
And what follows is the definition of terms like "IP-OBU", etc.  That is 
worrisome.  You can understand the worry if you read it as a whole:
>    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>    "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
>    "OPTIONAL" in this document are to be interpreted as described in BCP
>    14 [RFC2119] [RFC8174] when, and only when, they appear in all
>    capitals, as shown here.
> 
>    IP-OBU (Internet Protocol On-Board Unit): an IP-OBU is a computer
>    situated in a vehicle such as an automobile, bicycle, or similar.  It
>    has at least one IP interface that runs in mode OCB of 802.11, and
>    that has an "OBU" transceiver.  See the definition of the term "OBU"
>    in section Appendix I.

The dot after 'here' is very important, but so small.  A quick or 
low-sighted reader may see it as double dots.  And that would be a 
problem, because the "IP-OBU" term definition is not suject to that 
capitalization.

Alex