IETF Logo Mail Archive

Re: [IETFMIBS] IANA maintained MIB

"Nobo Akiya (nobo)" <nobo@cisco.com> Tue, 19 November 2013 21:21 UTC

Return-Path: <nobo@cisco.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 4FEF71ADF4B for <ietfmibs@ietfa.amsl.com>; Tue, 19 Nov 2013 13:21:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.426
X-Spam-Level:
X-Spam-Status: No, score=-9.426 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_15=0.6, RP_MATCHES_RCVD=-0.525, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 IW2Qj3sRKC-q for <ietfmibs@ietfa.amsl.com>; Tue, 19 Nov 2013 13:21:34 -0800 (PST)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) by ietfa.amsl.com (Postfix) with ESMTP id DF53F1AE168 for <ietfmibs@ietf.org>; Tue, 19 Nov 2013 13:21:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2942; q=dns/txt; s=iport; t=1384896088; x=1386105688; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=JHHsvwdzjlxwMaDNudUEbFrBzc0pgSdKVpH0npeDk0Y=; b=cIzNIzNWnfJZ2+/aD2AurqREQYdyglLEx8xjLliQ2MN0sRLdcsxKX0Rr OQpRZelxlilexi5D2xxcWf2n+VG/EdUwigDD6d0cBwtoVliZQx+t16ZPb tVGT+bjhjEXDRYwybQto7SRNBUeh8Z4zAdFu0HoQaQ8GPyxi1XkuWqKDj M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhQFAI3Vi1KtJXG9/2dsb2JhbABZgmYhOFO+ck6BIRZ0giUBAQEDAQEBATc0EAcEAgEIEQQBAQsUCQcnCxQJCAIEARIIh3MGAQy/UhMEjgsRAYEJOAaDGoESA5QwlW+DKIFxOQ
X-IronPort-AV: E=Sophos;i="4.93,732,1378857600"; d="scan'208";a="735607"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by alln-iport-7.cisco.com with ESMTP; 19 Nov 2013 21:21:27 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id rAJLLRcV026755 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 19 Nov 2013 21:21:27 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.03.0123.003; Tue, 19 Nov 2013 15:21:26 -0600
From: "Nobo Akiya (nobo)" <nobo@cisco.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "'t.petch'" <ietfc@btconnect.com>, 'Jeffrey Haas' <jhaas@pfrc.org>, "ietfmibs@ietf.org" <ietfmibs@ietf.org>
Thread-Topic: [IETFMIBS] IANA maintained MIB
Thread-Index: AQHO5U2O9cQd167QikegXfT0KWJafZos3f7ogABnBoD//8oGsA==
Date: Tue, 19 Nov 2013 21:21:26 +0000
Message-ID: <CECE764681BE964CBE1DFF78F3CDD3941DEE8E86@xmb-aln-x01.cisco.com>
References: <20131119173407.GC22285@pfrc> <073101cee553$e88ca220$4001a8c0@gateway.2wire.net> <047a01cee555$871711e0$954535a0$@olddog.co.uk>
In-Reply-To: <047a01cee555$871711e0$954535a0$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [161.44.213.104]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 20 Nov 2013 02:00:58 -0800
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: Tue, 19 Nov 2013 21:21:42 -0000

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

v2.23.0 | Report a Bug | By Email