IETF Logo Mail Archive

Re: [IETFMIBS] Extending InetAddress(Type) for BGP Multicast VPNs

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Tue, 10 January 2012 10:52 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: ietfmibs@ietfa.amsl.com
Delivered-To: ietfmibs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8ADF21F860F for <ietfmibs@ietfa.amsl.com>; Tue, 10 Jan 2012 02:52:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.291
X-Spam-Level:
X-Spam-Status: No, score=-103.291 tagged_above=-999 required=5 tests=[AWL=0.308, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cU93Oc+f+Dns for <ietfmibs@ietfa.amsl.com>; Tue, 10 Jan 2012 02:52:45 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 3850321F85A7 for <ietfmibs@ietf.org>; Tue, 10 Jan 2012 02:52:45 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAAAYDE+HCzI1/2dsb2JhbABDrFeBBYFyAQEBAQMBAQEPHgo0CwwEAgEIDQEDBAEBAQoGDAsBBgEmHwkIAQEEARIIGodgmnubVYsuYwSae4xK
X-IronPort-AV: E=Sophos;i="4.71,486,1320642000"; d="scan'208";a="323618351"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 10 Jan 2012 05:52:44 -0500
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 10 Jan 2012 05:39:35 -0500
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 10 Jan 2012 11:52:41 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A0406F48D38@307622ANEX5.global.avaya.com>
In-Reply-To: <52539B15-9568-486D-9E04-5F753DA2BFAC@juniper.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [IETFMIBS] Extending InetAddress(Type) for BGP Multicast VPNs
Thread-Index: AczPK52shvkES1LgSrqnUhhEQ5RUUgAWTgeg
References: <CBFBAE7D-EFBC-4833-9DD5-C2659C00F419@juniper.net><20120109234012.GA93650@elstar.local> <52539B15-9568-486D-9E04-5F753DA2BFAC@juniper.net>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Jeff Haas <jhaas@juniper.net>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Cc: ietfmibs@ietf.org
Subject: Re: [IETFMIBS] Extending InetAddress(Type) for BGP Multicast VPNs
X-BeenThere: ietfmibs@ietf.org
X-Mailman-Version: 2.1.12
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, 10 Jan 2012 10:52:45 -0000

Jeff,

I think that it would be useful however to provide an example of the
extensions that you have in mind, even if it's sketchy and not
syntactically perfect. I think that you are talking about extending the
InetAddressType TC with new values in order to use the BGPv2 MIB 'as
is', but I may be wrong. Putting more complexity in one of the most
commonly used set of TCs does not come for free either. 

Dan




> -----Original Message-----
> From: ietfmibs-bounces@ietf.org [mailto:ietfmibs-bounces@ietf.org] On
> Behalf Of Jeff Haas
> Sent: Tuesday, January 10, 2012 2:06 AM
> To: Juergen Schoenwaelder
> Cc: ietfmibs@ietf.org
> Subject: Re: [IETFMIBS] Extending InetAddress(Type) for BGP Multicast
> VPNs
> 
> Juergen,
> 
> On Jan 9, 2012, at 6:40 PM, Juergen Schoenwaelder wrote:
> > I have no clue what change you think is needed. Please excuse my
> > ignorance of BGP Multicast VPNs - but for me it is easier to
> > understand what you propose to change if there is a more concrete
> > description of the change you envision.
> 
> Reference:
> http://tools.ietf.org/html/draft-ietf-l3vpn-2547bis-mcast-bgp-08
> 
> BGP MVPN routes are basically 7 types of routing information
> distributed in BGP as prefixes.  Some of these routes are effectively
> fixed length but that's a minor detail.  Please refer to section 4 for
> the different route formats to avoid significant copy and paste.
> 
> My proposal is that 7 code points are allocated for MVPN routes for
> InetAddressType for these 7 types of information.  Textual conventions
> would be defined to cover each of the appropriate types.
> 
> One small annoyance is that the DISPLAY-HINT syntax isn't quite
> flexible enough to cover the variable-length types in a fully pleasing
> format.  There's not much we can do about that.
> 
> If this proposal seems to have merit and would be likely to get
> traction, we'll submit some text for the MIB.
> 
> -- Jeff
> 
> _______________________________________________
> IETFMIBS mailing list
> IETFMIBS@ietf.org
> https://www.ietf.org/mailman/listinfo/ietfmibs

v2.23.0 | Report a Bug | By Email