IETF Logo Mail Archive

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

Jeff Haas <jhaas@juniper.net> Sat, 14 January 2012 16:17 UTC

Return-Path: <jhaas@juniper.net>
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 9EF4921F8570 for <ietfmibs@ietfa.amsl.com>; Sat, 14 Jan 2012 08:17:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 aTc8Hn834OC1 for <ietfmibs@ietfa.amsl.com>; Sat, 14 Jan 2012 08:17:20 -0800 (PST)
Received: from exprod7og125.obsmtp.com (exprod7og125.obsmtp.com [64.18.2.28]) by ietfa.amsl.com (Postfix) with ESMTP id EB95521F8578 for <ietfmibs@ietf.org>; Sat, 14 Jan 2012 08:17:19 -0800 (PST)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob125.postini.com ([64.18.6.12]) with SMTP ID DSNKTxGqix6YY3xWLKM9Ceo/fyXbG0rhIIRB@postini.com; Sat, 14 Jan 2012 08:17:20 PST
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB02-HQ.jnpr.net ([fe80::88f9:77fd:dfc:4d51%11]) with mapi; Sat, 14 Jan 2012 08:16:40 -0800
From: Jeff Haas <jhaas@juniper.net>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Date: Sat, 14 Jan 2012 08:16:39 -0800
Thread-Topic: [IETFMIBS] Extending InetAddress(Type) for BGP Multicast VPNs
Thread-Index: AczS1+WQapo71X+NQv6KaS0eTHol6Q==
Message-ID: <4DB4A319-8AA8-4510-B2A9-42A06513F1C0@juniper.net>
References: <CBFBAE7D-EFBC-4833-9DD5-C2659C00F419@juniper.net> <20120109234012.GA93650@elstar.local> <52539B15-9568-486D-9E04-5F753DA2BFAC@juniper.net> <20120110105431.GC94367@elstar.local> <4F0C35ED.8060705@innovationslab.net> <28D0A91D-4C9B-4562-9495-639A38394194@juniper.net> <20120110144109.GD95306@elstar.local>
In-Reply-To: <20120110144109.GD95306@elstar.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietfmibs@ietf.org" <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: Sat, 14 Jan 2012 16:17:20 -0000

Juergen,

On Jan 10, 2012, at 9:41 AM, Juergen Schoenwaelder wrote:
> If the reachability info BGP is carrying turns out to be BGP specific,
> then having a BGP specific TC to represent it seems quite OK. Is any
> non-BGP protocol using the formats and the encodings I looked at
> earlier this morning? If not, these formats seems to be rather BGP
> specific.

It seems that I will be authoring (and probably maintaining) another BGP TC MIB for this purpose.

Could the group share any experiences with MIB documents that note code points by reference?  The BGP protocol suite continues to evolve at a very steady pace and it would be nice if I could point to new code points at IANA rather than having a MIB document that could never be stable enough to really reach an RFC, except perhaps for a snapshot.

-- Jeff

v2.23.0 | Report a Bug | By Email