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

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Sun, 15 January 2012 10:49 UTC

Return-Path: <j.schoenwaelder@jacobs-university.de>
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 9076721F84AE for <ietfmibs@ietfa.amsl.com>; Sun, 15 Jan 2012 02:49:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.223
X-Spam-Level:
X-Spam-Status: No, score=-103.223 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 UhYTDqP85Onn for <ietfmibs@ietfa.amsl.com>; Sun, 15 Jan 2012 02:49:44 -0800 (PST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id CE75521F8462 for <ietfmibs@ietf.org>; Sun, 15 Jan 2012 02:49:43 -0800 (PST)
Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id EE04220BDB; Sun, 15 Jan 2012 11:49:42 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius2.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id qpHg8ALfMpZE; Sun, 15 Jan 2012 11:49:42 +0100 (CET)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 5EF1120B6C; Sun, 15 Jan 2012 11:49:42 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id C2E981C85456; Sun, 15 Jan 2012 11:49:23 +0100 (CET)
Date: Sun, 15 Jan 2012 11:49:22 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Jeff Haas <jhaas@juniper.net>
Message-ID: <20120115104922.GA261@elstar.local>
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> <4DB4A319-8AA8-4510-B2A9-42A06513F1C0@juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4DB4A319-8AA8-4510-B2A9-42A06513F1C0@juniper.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
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
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
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: Sun, 15 Jan 2012 10:49:44 -0000

On Sat, Jan 14, 2012 at 08:16:39AM -0800, Jeff Haas wrote:
> 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.
> 

I do not know what "note code points by reference" means. You can
place a whole TC MIB module under IANA control if extensions are
needed and a WG process is to heavy weight.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>