Re: [Idr] BGP MIBv2 updates
"tom.petch" <cfinss@dial.pipex.com> Tue, 24 February 2009 12:25 UTC
Return-Path: <cfinss@dial.pipex.com>
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 088E83A682D for <idr@core3.amsl.com>; Tue, 24 Feb 2009 04:25:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.879
X-Spam-Level:
X-Spam-Status: No, score=-0.879 tagged_above=-999 required=5 tests=[AWL=0.077, BAYES_00=-2.599, RCVD_IN_NJABL_PROXY=1.643]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sMLFyZz68PGO for <idr@core3.amsl.com>; Tue, 24 Feb 2009 04:25:31 -0800 (PST)
Received: from mk-outboundfilter-6.mail.uk.tiscali.com (mk-outboundfilter-6.mail.uk.tiscali.com [212.74.114.14]) by core3.amsl.com (Postfix) with ESMTP id ECC623A6A21 for <idr@ietf.org>; Tue, 24 Feb 2009 04:25:30 -0800 (PST)
X-Trace: 78925207/mk-outboundfilter-6.mail.uk.tiscali.com/PIPEX/$PIPEX-ACCEPTED/pipex-customers/62.188.17.158/None/cfinss@dial.pipex.com
X-SBRS: None
X-RemoteIP: 62.188.17.158
X-IP-MAIL-FROM: cfinss@dial.pipex.com
X-MUA: Microsoft Outlook Express 6.00.2800.1106Produced By Microsoft MimeOLE V6.00.2800.1106
X-IP-BHB: Once
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhkFAOx1o0k+vBGe/2dsb2JhbACDQ0GKEMhWB4QKBg
X-IronPort-AV: E=Sophos;i="4.38,259,1233532800"; d="scan'208";a="78925207"
X-IP-Direction: IN
Received: from 1cust158.tnt1.lnd3.gbr.da.uu.net (HELO allison) ([62.188.17.158]) by smtp.pipex.tiscali.co.uk with SMTP; 24 Feb 2009 12:25:47 +0000
Message-ID: <014b01c99672$7438fde0$0601a8c0@allison>
From: "tom.petch" <cfinss@dial.pipex.com>
To: idr@ietf.org, Yakov Rekhter <yakov@juniper.net>
References: <200902231534.n1NFYSM53254@magenta.juniper.net>
Date: Tue, 24 Feb 2009 12:24:18 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Subject: Re: [Idr] BGP MIBv2 updates
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: "tom.petch" <cfinss@dial.pipex.com>
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Feb 2009 12:25:35 -0000
----- Original Message ----- From: "Yakov Rekhter" <yakov@juniper.net> To: <idr@ietf.org> Sent: Monday, February 23, 2009 4:34 PM Subject: Re: [Idr] BGP MIBv2 updates > Folks, > > Please comment on the attached request. The deadline for comments > is March 9, 2009. > I think that this is a sensible idea (and yes I understood it the first time:-). I take it that Yakov's e-mail is in pursuance to RFC4020 3.1 3). A question; RFC4181 discourages this approach, preferring experimental (which I think inappropriate here). Has the IESG approved early allocation for MIB Modules as per RFC4020 2 a)? This topic came up on another list recently and there was no mention of early allocation. I see no mention of approval on the IANA website. Tom Petch > Yakov. > ------- Forwarded Message > > Date: Mon, 23 Feb 2009 10:24:09 -0500 > From: Jeffrey Haas <jhaas@pfrc.org> > To: idr@ietf.org > Subject: Re: [Idr] BGP MIBv2 updates > > I was requested to be a little more clear here. > > On Sat, Feb 21, 2009 at 11:50:42PM -0500, Jeffrey Haas wrote: > > In order to encourage implementation of these drafts, I'd like to request an > > early allocation from the mib-2 space for these MIBs. > > I'd like to request an early allocation from mib-2 for the following > SNMP MODULE-IDENTITYs. > > > bgp4V2, published in draft-ietf-idr-bgp4-mibv2-09. > bgp4V2TC, published in draft-ietf-idr-bgp4-mibv2-tc-mib-00. > > > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www.ietf.org/mailman/listinfo/idr > > ------- End of Forwarded Message > > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www.ietf.org/mailman/listinfo/idr
- Re: [Idr] BGP MIBv2 updates Yakov Rekhter
- Re: [Idr] BGP MIBv2 updates tom.petch
- Re: [Idr] BGP MIBv2 updates Jeffrey Haas
- Re: [Idr] BGP MIBv2 updates tom.petch
- [Idr] Withdrawing request for early assignment of… Jeffrey Haas