IETF Logo Mail Archive

Re: [IETFMIBS] IANA maintained MIB

"Adrian Farrel" <adrian@olddog.co.uk> Tue, 19 November 2013 18:31 UTC

Return-Path: <adrian@olddog.co.uk>
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 5C6681AE014 for <ietfmibs@ietfa.amsl.com>; Tue, 19 Nov 2013 10:31:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.3
X-Spam-Level:
X-Spam-Status: No, score=-1.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=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 TirBNZ05rA7m for <ietfmibs@ietfa.amsl.com>; Tue, 19 Nov 2013 10:31:27 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 21B7F1AE113 for <ietfmibs@ietf.org>; Tue, 19 Nov 2013 10:31:26 -0800 (PST)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id rAJIVE3j013794; Tue, 19 Nov 2013 18:31:14 GMT
Received: from 950129200 (unsi-72-29-212-251.unsi.net [72.29.212.251] (may be forged)) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id rAJIVC61013770 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 19 Nov 2013 18:31:13 GMT
From: Adrian Farrel <adrian@olddog.co.uk>
To: "'t.petch'" <ietfc@btconnect.com>, 'Jeffrey Haas' <jhaas@pfrc.org>, ietfmibs@ietf.org
References: <20131119173407.GC22285@pfrc> <073101cee553$e88ca220$4001a8c0@gateway.2wire.net>
In-Reply-To: <073101cee553$e88ca220$4001a8c0@gateway.2wire.net>
Date: Tue, 19 Nov 2013 18:31:11 -0000
Message-ID: <047a01cee555$871711e0$954535a0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQDhi3d2T8vekSfJQ0dEfr8V2PK4OAIJPY2Fm/dJ3NA=
Content-Language: en-gb
Cc: "'Nobo Akiya (nobo)'" <nobo@cisco.com>
Subject: Re: [IETFMIBS] IANA maintained MIB
X-BeenThere: ietfmibs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
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: Tue, 19 Nov 2013 18:31:29 -0000

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

v2.23.0 | Report a Bug | By Email