Re: [MIB-DOCTORS] [IETFMIBS] Formatted Text of Security Guidelines for IETF MIB Modules

Glenn Mansfield Keeni <glenn@cysols.com> Mon, 08 October 2018 12:04 UTC

Return-Path: <glenn@cysols.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61FC0130DC8; Mon, 8 Oct 2018 05:04:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 jQD2teLKQiMY; Mon, 8 Oct 2018 05:04:00 -0700 (PDT)
Received: from niseko.cysol.co.jp (niseko.cysol.co.jp [210.233.3.236]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7668129AB8; Mon, 8 Oct 2018 05:03:59 -0700 (PDT)
Received: from [192.168.0.94] (cysvpn07.priv.cysol.co.jp [192.168.0.94]) (authenticated bits=0) by aso.priv.cysol.co.jp (8.14.9/8.14.9) with ESMTP id w98C3hhK020776 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 8 Oct 2018 21:03:44 +0900 (JST) (envelope-from glenn@cysols.com)
To: Hiroshi Tsunoda <tsuno@m.ieice.org>, ietfmibs@ietf.org, "mib-doctors@ietf.org" <mib-doctors@ietf.org>
References: <CAPbjwky66vuaPm2Pv5GvFdveggNzY6EEmU2Soyy-uCwypJ25=g@mail.gmail.com>
From: Glenn Mansfield Keeni <glenn@cysols.com>
Message-ID: <86d771d1-c66a-3b17-5e89-ec1fa12e790c@cysols.com>
Date: Mon, 8 Oct 2018 21:03:38 +0900
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <CAPbjwky66vuaPm2Pv5GvFdveggNzY6EEmU2Soyy-uCwypJ25=g@mail.gmail.com>
Content-Type: text/plain; charset=iso-2022-jp; format=flowed; delsp=yes
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mib-doctors/da1RCy8pLPknbsT9wJL9wWGShd4>
Subject: Re: [MIB-DOCTORS] [IETFMIBS] Formatted Text of Security Guidelines for IETF MIB Modules
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Oct 2018 12:04:02 -0000

Hi,
Got this. I am copying this to the Mib-doctors list.
We are working on fixing some nits in
https://trac.ietf.org/trac/ops/wiki/mib-security
Good timing!
Thanks.

Glenn
On 2018/10/03 15:43, Hiroshi Tsunoda wrote:
> Hi,
> 
> I think that https://trac.ietf.org/trac/ops/wiki/mib-security needs to be
> updated so that it refers RFC8174 which updates RFC2119.
> RFC8174 gives the new phrase to specifies common key words.
> 
> Concretely speaking, the beginning of  "Formatted Text" needs to be
> updated as follows.
> 
> ----------------------------------------------------------------------------------------------------------
> <OLD>
>     The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>     "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
>     this document are to be interpreted as described in BCP 14,
>     RFC 2119 [RFC2119].
> 
>     The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>     "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
>     in this document are to be interpreted as described in [KEYWORDS].
> 
>    [KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate
>                Requirement Levels", BCP 14, RFC 2119,
>                DOI 10.17487/RFC2119, March 1997,
>                <http://www.rfc-editor.org/info/rfc2119>;.
> ----------------------------------------------------------------------------------------------------------
> <NEW>
>     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.
> 
>     [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
>                Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
>                RFC2119, March 1997, <https://www.rfc-editor.org/info/
>                rfc2119>.
> 
>     [RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
>                2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
>                May 2017, <https://www.rfc-editor.org/info/rfc8174>;.
> ----------------------------------------------------------------------------------------------------------
> 
> Thanks,
> 
> -- tsuno
> 
> _______________________________________________
> IETFMIBS mailing list
> IETFMIBS@ietf.org
> https://www.ietf.org/mailman/listinfo/ietfmibs
>