IETF Logo Mail Archive

Re: [Idr] 4byte ASN support in RFC4273

Jeffrey Haas <jhaas@pfrc.org> Wed, 23 August 2006 20:30 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GFzMn-0004rP-KY; Wed, 23 Aug 2006 16:30:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GFzMm-0004rI-7C for idr@ietf.org; Wed, 23 Aug 2006 16:30:24 -0400
Received: from manos.scc.mi.org ([204.11.140.250]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFzMi-00088U-VX for idr@ietf.org; Wed, 23 Aug 2006 16:30:24 -0400
Received: by manos.scc.mi.org (Postfix, from userid 1025) id 914AB4E7E6; Wed, 23 Aug 2006 16:30:13 -0400 (EDT)
Date: Wed, 23 Aug 2006 16:30:13 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Henk Uijterwaal <henk@ripe.net>
Subject: Re: [Idr] 4byte ASN support in RFC4273
Message-ID: <20060823203013.GK13706@scc.mi.org>
References: <7.0.1.0.2.20060822105158.03521e78@ripe.net> <20060822164321.GA3647@scc.mi.org> <7.0.1.0.2.20060823180856.03548898@ripe.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <7.0.1.0.2.20060823180856.03548898@ripe.net>
User-Agent: Mutt/1.3.28i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: idr@ietf.org, asn32@ripe.net
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
Errors-To: idr-bounces@ietf.org

Henk,

On Wed, Aug 23, 2006 at 06:11:11PM +0200, Henk Uijterwaal wrote:
> Are you planning to write this draft/MIB?

A version of this mib was proposed:
draft-ietf-idr-bgp4-mib-v2-05 was the last version published.

It didn't receive much support due to its complexity.

I've factored the complex functionality out, removed configuration
objects and am planning no a republish of the components within
the next two weeks, work permitting.  Your review would be greatly
appreciated.

> I have several products using
> the current MIB and it'd really help if I could point maintainers to
> a new MIB and ask them to upgrade?  I can even provide a list of things
> that need to be changed (but I'm no MIB expert, so I don't think I
> could write the MIB myself).

Inputs on the MIB features would be appreciated.  Core features of
the base mib include:

- Support for multiple bgp instances
- Support for multiple route instances
- 4 byte as path support
- ipv6 support
- prefix counters
- hooks for extension mibs
  + communities
  + extended-communities
  + confederations
  + route reflect
  + etc.

Long term, this may also support other uses of bgp to transport non-ipv4/v6
nlri, but that isn't the focus of this work.

-- Jeff

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr

v2.23.0 | Report a Bug | By Email