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

Glenn Mansfield Keeni <glenn@cysols.com> Mon, 01 October 2018 02:22 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 480471294D7 for <mib-doctors@ietfa.amsl.com>; Sun, 30 Sep 2018 19:22:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=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 YSI2OfCl8AFC for <mib-doctors@ietfa.amsl.com>; Sun, 30 Sep 2018 19:22:09 -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 E39BA12872C for <mib-doctors@ietf.org>; Sun, 30 Sep 2018 19:22:08 -0700 (PDT)
Received: from [192.168.0.200] (Lenovo-X1Carbon.win2004.cysol.co.jp [192.168.0.200]) (authenticated bits=0) by aso.priv.cysol.co.jp (8.14.9/8.14.9) with ESMTP id w912Le2d040835 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 1 Oct 2018 11:21:40 +0900 (JST) (envelope-from glenn@cysols.com)
To: Warren Kumari <warren@kumari.net>
Cc: Ignas Bagdonas <ibagdona@gmail.com>, mib-doctors@ietf.org
References: <7f59ba0b-1358-1015-cd85-4c470ad73d9a@cysols.com> <CAHw9_iKDmk4McQrzvOjd83KzYw9MutK4Yk+-2dQk2S1xeOdsqA@mail.gmail.com>
From: Glenn Mansfield Keeni <glenn@cysols.com>
Message-ID: <eafee7ed-8d2b-dfc7-ef72-cf789b613144@cysols.com>
Date: Mon, 1 Oct 2018 11:21:35 +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: <CAHw9_iKDmk4McQrzvOjd83KzYw9MutK4Yk+-2dQk2S1xeOdsqA@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/2EehbU94ljJOcevgtpO3WjwR_X0>
Subject: Re: [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: Mon, 01 Oct 2018 02:22:11 -0000

Hi,
 > I propose we fix this nit now, and the larger discussion can
 > continue - 'tis trivial to update the boilerplate again once
 > the larger discussion has gelled.
 >
 > Sound reasonable? I'll let Ignas to make the call (it's more
 > on his side of the house than mine).

Absolutely! Thanks.

Glenn

On 2018/10/01 3:33, Warren Kumari wrote:
> On Sat, Sep 29, 2018 at 2:53 AM Glenn Mansfield Keeni <glenn@cysols.com>;
> wrote:
> 
>> 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.
>>
> 
> I'm obviously not Igans (he's got more, and better hair), but this is
> clearly a nit that is easy to address.
> I propose we fix this nit now, and the larger discussion can continue -
> 'tis trivial to update the boilerplate again once the larger discussion has
> gelled.
> 
> Sound reasonable? I'll let Ignas to make the call (it's more on his side of
> the house than mine).
> 
> W
> 
> 
> 
>>
>> Thanks,
>> Glenn
>>
>>
>