IETF Logo Mail Archive

Re: [Idr] BGP MIBv2 updates

"Joan Cucchiara" <jcucchiara@mindspring.com> Wed, 25 February 2009 13:45 UTC

Return-Path: <jcucchiara@mindspring.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 B546C28C19B for <idr@core3.amsl.com>; Wed, 25 Feb 2009 05:45:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.104
X-Spam-Level:
X-Spam-Status: No, score=-0.104 tagged_above=-999 required=5 tests=[AWL=1.005, BAYES_05=-1.11, STOX_REPLY_TYPE=0.001]
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 3ohrFT-vQOAx for <idr@core3.amsl.com>; Wed, 25 Feb 2009 05:45:01 -0800 (PST)
Received: from elasmtp-spurfowl.atl.sa.earthlink.net (elasmtp-spurfowl.atl.sa.earthlink.net [209.86.89.66]) by core3.amsl.com (Postfix) with ESMTP id E169F28C13F for <idr@ietf.org>; Wed, 25 Feb 2009 05:45:00 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=RhunthbfppB3hVEPPYS6jJTLLMznmmZdOaE+2S8d63w5+N9WIe0c8rpRZzhDizTg; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [141.154.112.219] (helo=JoanPC) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <jcucchiara@mindspring.com>) id 1LcK4e-0005td-TC; Wed, 25 Feb 2009 08:45:21 -0500
Message-ID: <015c01c9974f$4d407410$6401a8c0@JoanPC>
From: Joan Cucchiara <jcucchiara@mindspring.com>
To: Jeffrey Haas <jhaas@pfrc.org>, idr@ietf.org
References: <20090222043001.40A7C3A6829@core3.amsl.com><20090222045041.GA26110@slice> <20090223152409.GA9207@slice>
Date: Wed, 25 Feb 2009 08:45:20 -0500
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-ELNK-Trace: 4d68bbe9cb71969ea344cf2d1a8e60840a9da525759e265490232586cda6d51d5a8b95323abe648d3122699149cfe979350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 141.154.112.219
Subject: Re: [Idr] BGP MIBv2 updates
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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: Wed, 25 Feb 2009 13:45:01 -0000

Hi Jeff,

Are the objects' names going to changed for the drafts which
receive an early mib-2 subid allocation vs. the RFC versions?

The reason that I'm asking is that not all the tools identify
objects using their OIDs, many use the objects' names.   If the
objects' names remain the same between the draft MIB Modules
and the RFC MIB Modules, then this could cause problems.


   Thanks,
      -Joan


----- Original Message ----- 
From: "Jeffrey Haas" <jhaas@pfrc.org>
To: <idr@ietf.org>
Sent: Monday, February 23, 2009 10:24 AM
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

v2.23.0 | Report a Bug | By Email