Re: [MIB-DOCTORS] Doubt on naming convention

Glenn Mansfield Keeni <glenn@cysols.com> Wed, 05 September 2018 08:34 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 121F3130DC5 for <mib-doctors@ietfa.amsl.com>; Wed, 5 Sep 2018 01:34:53 -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 zS5TiHEr920u for <mib-doctors@ietfa.amsl.com>; Wed, 5 Sep 2018 01:34:51 -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 6873F130DDD for <mib-doctors@ietf.org>; Wed, 5 Sep 2018 01:34:51 -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 w858YaKg029424 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <mib-doctors@ietf.org>; Wed, 5 Sep 2018 17:34:36 +0900 (JST) (envelope-from glenn@cysols.com)
To: mib-doctors@ietf.org
References: <CANSkkOmTD7F3ioxuccKUMq5tVUZh-MwvaDLyL0=59NTPiy2J9Q@mail.gmail.com> <5743c7d8-2de1-5739-c279-7f64091a3f02@cysols.com> <20180905082056.63ik553dxy5cpuj2@anna.jacobs.jacobs-university.de>
From: Glenn Mansfield Keeni <glenn@cysols.com>
Message-ID: <960ffdfd-48df-f143-3ce3-60d76a8edb5e@cysols.com>
Date: Wed, 5 Sep 2018 17:34:31 +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: <20180905082056.63ik553dxy5cpuj2@anna.jacobs.jacobs-university.de>
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/9GmKEYZASIJ4IjhoDa3H2Aa5uqk>
Subject: Re: [MIB-DOCTORS] Doubt on naming convention
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: Wed, 05 Sep 2018 08:34:53 -0000

Juergen,
       Thanks. That was helpful.
Glenn
On 2018/09/05 17:20, Juergen Schoenwaelder wrote:
> On Wed, Sep 05, 2018 at 04:59:58PM +0900, Glenn Mansfield Keeni wrote:
>> Hi,
>> Is there a rule or a convention for naming the MIB
>> definitions in the DEFINITIONS clause below?
>>
>>      XXXXXX-YYYYY-MIB DEFINITIONS ::= BEGIN
>>
>> More specifically does it have to
>> be all capitals?
>> Is
>>      Multicast-VPN-MIB DEFINITIONS ::= BEGIN
>> OK ?
>>
> 
> Technically, Multicast-VPN-MIB is a legal name. Practically speaking,
> I count ~300 MIB modules in RFCs that have no lowercase characters in
> their module name and ~15 MIB modules in RFCs that have a lowercase
> character in their module name. And out of these, a common usage of
> lowercase letters is to indicate a version number, e.g. NTPv4-MIB,
> RIPv2-MIB, SNMPv2-CONF, SNMPv2-MIB, SNMPv2-SMI, SNMPv2-TC, SNMPv2-TM,
> SNMPv2-USEC-MIB. And the remaining modules tend to be rather old
> modules (or modules with a long history).
> 
> RFC 4181 (BCP 111) says in Appendix C:
> 
>     - The module name should be of the form XXX-MIB (or XXX-TC-MIB for a
>       module with TCs only), where XXX is a unique prefix (usually all
>       caps with hyphens for separators) that is not used by any existing
>       module.
> 
> So the common convention is to all caps with hyphens for separators.
> 
> /js
>