Re: [IETFMIBS] IANA maintained MIB

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Wed, 20 November 2013 09:21 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: ietfmibs@ietfa.amsl.com
Delivered-To: ietfmibs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD7DF1AE39B for <ietfmibs@ietfa.amsl.com>; Wed, 20 Nov 2013 01:21:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.525
X-Spam-Level:
X-Spam-Status: No, score=-2.525 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.525] autolearn=ham
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 otighKIj5HHa for <ietfmibs@ietfa.amsl.com>; Wed, 20 Nov 2013 01:21:11 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 52F161AE38A for <ietfmibs@ietf.org>; Wed, 20 Nov 2013 01:21:11 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhQFAJB+jFKHCzI1/2dsb2JhbABZgmYhOFO+GE6BEhZ0giUBAQEBAwEBAQ8oMQMXBAIBCA0EBAEBCxQJBycLFAkIAgQBEggah18BDKQ6m3UTBI4LEQGBCTgGgxqBEgOUMIpIiyeDKIFxOQ
X-IronPort-AV: E=Sophos;i="4.93,735,1378872000"; d="scan'208";a="32442908"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 20 Nov 2013 04:21:02 -0500
Received: from unknown (HELO AZ-FFEXHC02.global.avaya.com) ([135.64.58.12]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 20 Nov 2013 04:10:35 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC02.global.avaya.com ([135.64.58.12]) with mapi id 14.03.0146.000; Wed, 20 Nov 2013 10:21:00 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "'Nobo Akiya (nobo)'" <nobo@cisco.com>, "'t.petch'" <ietfc@btconnect.com>, 'Jeffrey Haas' <jhaas@pfrc.org>, "ietfmibs@ietf.org" <ietfmibs@ietf.org>
Thread-Topic: [IETFMIBS] IANA maintained MIB
Thread-Index: AQHO5U2QTb3fDXUzd0yAPBS7oJr1GQIJPY2FAa/Jn1ACi8QA9JvVpWmA/iYJO0A=
Date: Wed, 20 Nov 2013 09:20:59 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA12942330@AZ-FFEXMB04.global.avaya.com>
References: <20131119173407.GC22285@pfrc> <073101cee553$e88ca220$4001a8c0@gateway.2wire.net> <047a01cee555$871711e0$954535a0$@olddog.co.uk> <CECE764681BE964CBE1DFF78F3CDD3941DEE8E86@xmb-aln-x01.cisco.com> <04ba01cee571$6b970e90$42c52bb0$@olddog.co.uk>
In-Reply-To: <04ba01cee571$6b970e90$42c52bb0$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.46]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [IETFMIBS] IANA maintained MIB
X-BeenThere: ietfmibs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF MIB Discussion list <ietfmibs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietfmibs>, <mailto:ietfmibs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietfmibs/>
List-Post: <mailto:ietfmibs@ietf.org>
List-Help: <mailto:ietfmibs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietfmibs>, <mailto:ietfmibs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Nov 2013 09:21:13 -0000

Hi,

I do not find any reason -- not to -- either. 

I do have some comments and answers to the questions in this discussion. 

1. An IANA maintained MIB is basically an IANA registry. The document that defines should include a non-empty IANA considerations section defining the root allocation for the MIB module, and the RFC 5226 policy for adding new entries. The last example I was involved with is RFC 6933 which changed the former PhysicalClass TC in the previous versions of the Entity MIB into a new IANA-maintained TC called IANAPhysicalClass.
2. I personally believe that Expert Review would be sufficient. The 'cost' is just nominating one or two experts to help IANA when new requests hit their desk vs. writing for each new entry or set of entries an RFC that must shepherded through the IESG as AD Sponsored or IETF WG Documents as required by IETF Review policy. Is there a strong reason to involve all the IETF (like in the IETF Review policy) when new values are added to the enumeration in the TC? 
3. It is wise to follow Juergen's advice and prefix by iana the future TC name. 

Regards,

Dan


> -----Original Message-----
> From: IETFMIBS [mailto:ietfmibs-bounces@ietf.org] On Behalf Of Adrian
> Farrel
> Sent: Tuesday, November 19, 2013 11:51 PM
> To: 'Nobo Akiya (nobo)'; 't.petch'; 'Jeffrey Haas'; ietfmibs@ietf.org
> Subject: Re: [IETFMIBS] IANA maintained MIB
> 
> I don't know about *need* but it seems like a really good idea.
> 
> Any reason not to?
> 
> A
> 
> > -----Original Message-----
> > From: Nobo Akiya (nobo) [mailto:nobo@cisco.com]
> > Sent: 19 November 2013 21:21
> > To: adrian@olddog.co.uk; 't.petch'; 'Jeffrey Haas'; ietfmibs@ietf.org
> > Subject: RE: [IETFMIBS] IANA maintained MIB
> >
> > Hi Adrian, Jeff, Tom, et al,
> >
> > Thank you for response on this thread.
> >
> > We will mimic contents from RFC 4802.
> >
> > One remaining question.
> >
> > 1. [snip from Jeff's email]
> >
> > > What's not clear is if the IANA- prefix is a requirement for the TCs
> > > that
> the BFD
> > MIBs are creating.
> >
> > Meaning, does TC MIB OID need to start with "IANA" ... i.e.
> "IANAFooBar"?
> >
> > Thanks,
> > Nobo
> >
> > > -----Original Message-----
> > > From: Adrian Farrel [mailto:adrian@olddog.co.uk]
> > > Sent: Tuesday, November 19, 2013 1:31 PM
> > > To: 't.petch'; 'Jeffrey Haas'; ietfmibs@ietf.org
> > > Cc: Nobo Akiya (nobo)
> > > Subject: RE: [IETFMIBS] IANA maintained MIB
> > >
> > > Jeff,
> > >
> > > My poster child is RFC 4802. This one I am familiar with as
> > > co-author, so I
> am
> > > happy to answer questions related to it.
> > >
> > > You'll also get good help from Michelle if you ask IANA any
> questions.
> > >
> > > A
> > >
> > > > -----Original Message-----
> > > > From: IETFMIBS [mailto:ietfmibs-bounces@ietf.org] On Behalf Of
> > > > t.petch
> > > > Sent: 19 November 2013 18:19
> > > > To: Jeffrey Haas; ietfmibs@ietf.org
> > > > Cc: Nobo Akiya (nobo)
> > > > Subject: Re: [IETFMIBS] IANA maintained MIB
> > > >
> > > > Jeff
> > > >
> > > > Have you looked at 'IANA Maintained MIBs' on the IANA website?
> > > > That has most if not all the ones I know about.
> > > >
> > > > Tom Petch
> > > >
> > > >
> > > > ----- Original Message -----
> > > > From: "Jeffrey Haas" <jhaas@pfrc.org>
> > > > To: <ietfmibs@ietf.org>
> > > > Cc: "Nobo Akiya (nobo)" <nobo@cisco.com>
> > > > Sent: Tuesday, November 19, 2013 5:34 PM
> > > > Subject: [IETFMIBS] IANA maintained MIB
> > > >
> > > >
> > > > > I'm in the midst of doing my document shepherd work for the BFD
> > > > > TC MIB (draft-ietf-bfd-tc-mib).  And yes, I caught the syntax
> > > > > error and have requested the authors to fix it. :-)
> > > > >
> > > > > One motivation to split this TC MIB off was the long term desire
> > > > > to
> > > > make
> > > > > this an IANA maintained MIB - a detail which had remained in one
> > > > > of my
> > > > old
> > > > > emails but hadn't received follow-up until now.  As I work
> > > > > through the checklist and the commentary in RFC 5226, I find
> > > > > that I'm still not
> > > > quite
> > > > > certain what we'd need to change either the draft or the IANA
> > > > > requests in order to properly make this an IANA maintained MIB.
> > > > > Policy-wise, IETF Review is the likely appropriate thing to do.
> > > > >
> > > > > Can someone recommend either a relatively recent RFC/draft that
> > > > > puts a
> > > > TC
> > > > > MIB into IANA Maintenance or alternatively lend a hand and
> > > > > suggest
> > > > some text
> > > > > for the BFD TC MIB draft?
> > > > >
> > > > > Thanks,
> > > > >
> > > > > -- Jeff (for the BFD WG)
> > > > > _______________________________________________
> > > > > IETFMIBS mailing list
> > > > > IETFMIBS@ietf.org
> > > > > https://www.ietf.org/mailman/listinfo/ietfmibs
> > > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > IETFMIBS mailing list
> > > > IETFMIBS@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/ietfmibs
> 
> _______________________________________________
> IETFMIBS mailing list
> IETFMIBS@ietf.org
> https://www.ietf.org/mailman/listinfo/ietfmibs