[MIB-DOCTORS] Fix of Security Guidelines for IETF MIB Modules

Glenn Mansfield Keeni <glenn@cysols.com> Sat, 29 September 2018 06:53 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 24172130DDE for <mib-doctors@ietfa.amsl.com>; Fri, 28 Sep 2018 23:53:35 -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 OSrGsGiORdLz for <mib-doctors@ietfa.amsl.com>; Fri, 28 Sep 2018 23:53:33 -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 B339F126CC7 for <mib-doctors@ietf.org>; Fri, 28 Sep 2018 23:53:31 -0700 (PDT)
Received: from [192.168.0.92] (cysvpn05.priv.cysol.co.jp [192.168.0.92]) (authenticated bits=0) by aso.priv.cysol.co.jp (8.14.9/8.14.9) with ESMTP id w8T6qvko026064 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sat, 29 Sep 2018 15:52:58 +0900 (JST) (envelope-from glenn@cysols.com)
To: warren@kumari.net, ibagdona@gmail.com, "mib-doctors@ietf.org" <mib-doctors@ietf.org>
From: Glenn Mansfield Keeni <glenn@cysols.com>
Message-ID: <7f59ba0b-1358-1015-cd85-4c470ad73d9a@cysols.com>
Date: Sat, 29 Sep 2018 15:52:52 +0900
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
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/gVCcRyRyj9SFi1xZeqRbCyerkK0>
Subject: [MIB-DOCTORS] Fix 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: Sat, 29 Sep 2018 06:53:35 -0000

Warren,Ignas,
        Hi. The Security Guidelines for IETF MIB Modules
needs a fix in the text that is generally used verbatim
in MIB documents.
The proposed fix is

OLD: Some of the readable objects in this MIB module
      (i.e., objects with a MAX-ACCESS other than
       not-accessible)
NEW: Some of the readable objects in this MIB module
      (e.g., objects with a MAX-ACCESS other than
       not-accessible)

The above is a significant nit. It appears in the
Security Considerations sections section of every
MIB document.

There has been some discussion on the IETF MIB-DOCTORS
mailing list on this matter. There is no disagreement
on the proposed fix.

Please advise on how to proceed on this matter.

Thanks,
Glenn