Re: [ippm] Ben Campbell's No Objection on draft-ietf-ippm-2330-ipv6-05: (with COMMENT)

"MORTON, ALFRED C (AL)" <acm@research.att.com> Thu, 21 June 2018 19:14 UTC

Return-Path: <acm@research.att.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92CEE130DDF; Thu, 21 Jun 2018 12:14:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 RduZuCyLIGIG; Thu, 21 Jun 2018 12:14:15 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (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 15B18130DCD; Thu, 21 Jun 2018 12:14:15 -0700 (PDT)
Received: from pps.filterd (m0049459.ppops.net [127.0.0.1]) by m0049459.ppops.net-00191d01. (8.16.0.22/8.16.0.22) with SMTP id w5LJ6fbw005708; Thu, 21 Jun 2018 15:14:03 -0400
Received: from tlpd255.enaf.dadc.sbc.com (sbcsmtp3.sbc.com [144.160.112.28]) by m0049459.ppops.net-00191d01. with ESMTP id 2jrgsmhug5-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 21 Jun 2018 15:14:02 -0400
Received: from enaf.dadc.sbc.com (localhost [127.0.0.1]) by tlpd255.enaf.dadc.sbc.com (8.14.5/8.14.5) with ESMTP id w5LJE1Nf008676; Thu, 21 Jun 2018 14:14:01 -0500
Received: from zlp30496.vci.att.com (zlp30496.vci.att.com [135.46.181.157]) by tlpd255.enaf.dadc.sbc.com (8.14.5/8.14.5) with ESMTP id w5LJDs1L008462; Thu, 21 Jun 2018 14:13:55 -0500
Received: from zlp30496.vci.att.com (zlp30496.vci.att.com [127.0.0.1]) by zlp30496.vci.att.com (Service) with ESMTP id DB90541AE6A8; Thu, 21 Jun 2018 19:13:54 +0000 (GMT)
Received: from clpi183.sldc.sbc.com (unknown [135.41.1.46]) by zlp30496.vci.att.com (Service) with ESMTP id BBE5D41AE6A2; Thu, 21 Jun 2018 19:13:54 +0000 (GMT)
Received: from sldc.sbc.com (localhost [127.0.0.1]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id w5LJDsGk001033; Thu, 21 Jun 2018 14:13:54 -0500
Received: from mail-green.research.att.com (mail-green.research.att.com [135.207.255.15]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id w5LJDj1j000545; Thu, 21 Jun 2018 14:13:46 -0500
Received: from exchange.research.att.com (njbdcas1.research.att.com [135.197.255.61]) by mail-green.research.att.com (Postfix) with ESMTP id E41BBE14C7; Thu, 21 Jun 2018 15:12:22 -0400 (EDT)
Received: from njmtexg4.research.att.com ([fe80::8cd:baa3:219e:5bd4]) by njbdcas1.research.att.com ([fe80::8c6b:4b77:618f:9a01%11]) with mapi id 14.03.0399.000; Thu, 21 Jun 2018 15:13:29 -0400
From: "MORTON, ALFRED C (AL)" <acm@research.att.com>
To: Ben Campbell <ben@nostrum.com>, The IESG <iesg@ietf.org>
CC: "draft-ietf-ippm-2330-ipv6@ietf.org" <draft-ietf-ippm-2330-ipv6@ietf.org>, Brian Trammell <ietf@trammell.ch>, Nevil Brownlee <n.brownlee@auckland.ac.nz>, "ippm-chairs@ietf.org" <ippm-chairs@ietf.org>, "n.brownlee@auckland.ac.nz" <n.brownlee@auckland.ac.nz>, "ippm@ietf.org" <ippm@ietf.org>
Thread-Topic: Ben Campbell's No Objection on draft-ietf-ippm-2330-ipv6-05: (with COMMENT)
Thread-Index: AQHUCEZkikQJI1/xF0m1DPdNMYVxQKRrEr6Q
Date: Thu, 21 Jun 2018 19:13:43 +0000
Message-ID: <4D7F4AD313D3FC43A053B309F97543CF4A92F15A@njmtexg4.research.att.com>
References: <152946514936.32242.15260380803081346147.idtracker@ietfa.amsl.com>
In-Reply-To: <152946514936.32242.15260380803081346147.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [64.201.95.59]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-06-21_08:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=939 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1805220000 definitions=main-1806210205
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/omWJ0rb1chqzPjt5EyqVI0viJA8>
Subject: Re: [ippm] Ben Campbell's No Objection on draft-ietf-ippm-2330-ipv6-05: (with COMMENT)
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2018 19:14:17 -0000

Hi Ben,

> -----Original Message-----
> From: Ben Campbell [mailto:ben@nostrum.com]
...
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Requirements Language: Please use the actual boilerplate specified in RFC
> 8174.
>
[acm] 
We have:
32	Requirements Language

34	   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
35	   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
36	   document are to be interpreted as described in [RFC2119] and updated
37	   by [RFC8174].

and RFC 8174 says:


   Authors who follow these guidelines should incorporate this phrase
   near the beginning of their document:

      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.

Noting that RFC 8174 uses a lower-case "should", there's no requirement
to use this exact wording, right?  

But you said "please", and that means much more than "should".

I've updated the working text (and I have many others in-flight
that need this update, too).

regards,
Al