
From jhaas@juniper.net  Mon Jan  9 12:42:44 2012
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 1BA6D21F87B3 for <ietfmibs@ietfa.amsl.com>; Mon,  9 Jan 2012 12:42:44 -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 QWAIRPekfvf4 for <ietfmibs@ietfa.amsl.com>; Mon,  9 Jan 2012 12:42:43 -0800 (PST)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id 4BE4621F8796 for <ietfmibs@ietf.org>; Mon,  9 Jan 2012 12:42:43 -0800 (PST)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKTwtRQWeLQjEgxQUMBJry7l5cxhwiZ95r@postini.com; Mon, 09 Jan 2012 12:42:43 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; Mon, 9 Jan 2012 12:40:16 -0800
From: Jeff Haas <jhaas@juniper.net>
To: "ietfmibs@ietf.org" <ietfmibs@ietf.org>
Date: Mon, 9 Jan 2012 12:40:19 -0800
Thread-Topic: Extending InetAddress(Type) for BGP Multicast VPNs
Thread-Index: AczPDuURcDTe3KtYRfqCnYepi/MhVA==
Message-ID: <CBFBAE7D-EFBC-4833-9DD5-C2659C00F419@juniper.net>
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
Subject: [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: Mon, 09 Jan 2012 20:42:44 -0000

I am the current editor for the BGP MIB (draft-ietf-idr-bgp4-mibv2).  I've =
been approached recently about MIB representation of BGP Multicast VPNs (dr=
aft-ietf-l3vpn-2547bis-mcast-bgp).  After having spent some time discussing=
 this with some people internally at Juniper, it seems like the BGP MIBv2 w=
ould handle a significant portion of representing MVPNs.  This is great, be=
cause much of the purpose of the structure of the new BGP MIB was to make i=
t re-usable for other address families.

The one sticking point is the representation of MVPN reachability (prefixes=
, effectively).  The BGP MIB does the following:


    bgp4V2NlriPrefixType OBJECT-TYPE
        SYNTAX     InetAddressType
        MAX-ACCESS not-accessible


        STATUS     current
        DESCRIPTION
            "The type of the IP address prefix in the
             Network Layer Reachability Information field.
             The value of this object is derived from the
             appropriate value from the bgp4V2NlriAfi field.
             Where an appropriate InetAddressType is not
             available, the value of the object must be
             unknown(0)."
        ::=3D { bgp4V2NlriEntry 4 }

    bgp4V2NlriPrefix OBJECT-TYPE
        SYNTAX     InetAddress
        MAX-ACCESS not-accessible
        STATUS     current
        DESCRIPTION
            "An IP address prefix in the Network Layer
             Reachability Information field. This object
             is an IP address containing the prefix with
             length specified by bgp4V2NlriPrefixLen.
             Any bits beyond the length specified by
             bgp4V2NlriPrefixLen are zeroed."
        REFERENCE
            "RFC 4271, Section 4.3<http://tools.ietf.org/html/rfc4271#secti=
on-4.3>."
        ::=3D { bgp4V2NlriEntry 5 }

    bgp4V2NlriPrefixLen OBJECT-TYPE
        SYNTAX     InetAddressPrefixLength
        MAX-ACCESS not-accessible
        STATUS     current
        DESCRIPTION
            "Length in bits of the address prefix in
             the Network Layer Reachability Information field."
        ::=3D { bgp4V2NlriEntry 6 }


It would seem that the "relatively simple" method to extend this to MVPN wo=
uld be to update the InetAddress(Type) textual conventions.

I am aware that by making that statement I have stepped into the dragon's m=
aw.  Please be gentle. :-)

But more seriously, this seems to be a good fit for what this TC was intend=
ed to accomplish: Make MIB structure more generic and reusable.  How could =
we go about accomplishing the goal of re-using the BGP MIB for MVPN?

-- Jeff

From j.schoenwaelder@jacobs-university.de  Mon Jan  9 15:40:59 2012
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 0C89711E80D6 for <ietfmibs@ietfa.amsl.com>; Mon,  9 Jan 2012 15:40:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.249
X-Spam-Level: 
X-Spam-Status: No, score=-103.249 tagged_above=-999 required=5 tests=[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 fjISDclynuPn for <ietfmibs@ietfa.amsl.com>; Mon,  9 Jan 2012 15:40:58 -0800 (PST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 92DC911E80DC for <ietfmibs@ietf.org>; Mon,  9 Jan 2012 15:40:31 -0800 (PST)
Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id 8866120BD7; Tue, 10 Jan 2012 00:40:30 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius4.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id yoZ9NRXCwL6r; Tue, 10 Jan 2012 00:40:30 +0100 (CET)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 1FDFB20BD6; Tue, 10 Jan 2012 00:40:30 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id E4CE91C5FF1D; Tue, 10 Jan 2012 00:40:12 +0100 (CET)
Date: Tue, 10 Jan 2012 00:40:12 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Jeff Haas <jhaas@juniper.net>
Message-ID: <20120109234012.GA93650@elstar.local>
References: <CBFBAE7D-EFBC-4833-9DD5-C2659C00F419@juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CBFBAE7D-EFBC-4833-9DD5-C2659C00F419@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: Mon, 09 Jan 2012 23:40:59 -0000

On Mon, Jan 09, 2012 at 12:40:19PM -0800, Jeff Haas wrote:
> I am the current editor for the BGP MIB (draft-ietf-idr-bgp4-mibv2).  I've been approached recently about MIB representation of BGP Multicast VPNs (draft-ietf-l3vpn-2547bis-mcast-bgp).  After having spent some time discussing this with some people internally at Juniper, it seems like the BGP MIBv2 would handle a significant portion of representing MVPNs.  This is great, because much of the purpose of the structure of the new BGP MIB was to make it re-usable for other address families.
> 
> The one sticking point is the representation of MVPN reachability (prefixes, effectively).  The BGP MIB does the following:
> 
> 
>     bgp4V2NlriPrefixType OBJECT-TYPE
>         SYNTAX     InetAddressType
>         MAX-ACCESS not-accessible
> 
> 
>         STATUS     current
>         DESCRIPTION
>             "The type of the IP address prefix in the
>              Network Layer Reachability Information field.
>              The value of this object is derived from the
>              appropriate value from the bgp4V2NlriAfi field.
>              Where an appropriate InetAddressType is not
>              available, the value of the object must be
>              unknown(0)."
>         ::= { bgp4V2NlriEntry 4 }
> 
>     bgp4V2NlriPrefix OBJECT-TYPE
>         SYNTAX     InetAddress
>         MAX-ACCESS not-accessible
>         STATUS     current
>         DESCRIPTION
>             "An IP address prefix in the Network Layer
>              Reachability Information field. This object
>              is an IP address containing the prefix with
>              length specified by bgp4V2NlriPrefixLen.
>              Any bits beyond the length specified by
>              bgp4V2NlriPrefixLen are zeroed."
>         REFERENCE
>             "RFC 4271, Section 4.3<http://tools.ietf.org/html/rfc4271#section-4.3>."
>         ::= { bgp4V2NlriEntry 5 }
> 
>     bgp4V2NlriPrefixLen OBJECT-TYPE
>         SYNTAX     InetAddressPrefixLength
>         MAX-ACCESS not-accessible
>         STATUS     current
>         DESCRIPTION
>             "Length in bits of the address prefix in
>              the Network Layer Reachability Information field."
>         ::= { bgp4V2NlriEntry 6 }
> 
> 
> It would seem that the "relatively simple" method to extend this to MVPN would be to update the InetAddress(Type) textual conventions.
> 
> I am aware that by making that statement I have stepped into the dragon's maw.  Please be gentle. :-)
> 
> But more seriously, this seems to be a good fit for what this TC was intended to accomplish: Make MIB structure more generic and reusable.  How could we go about accomplishing the goal of re-using the BGP MIB for MVPN?

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.

/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/>

From jhaas@juniper.net  Mon Jan  9 16:09:23 2012
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 CCABC11E80B4 for <ietfmibs@ietfa.amsl.com>; Mon,  9 Jan 2012 16:09:23 -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 3-WTOyF17fr0 for <ietfmibs@ietfa.amsl.com>; Mon,  9 Jan 2012 16:09:23 -0800 (PST)
Received: from exprod7og102.obsmtp.com (exprod7og102.obsmtp.com [64.18.2.157]) by ietfa.amsl.com (Postfix) with ESMTP id 18F7E11E80B1 for <ietfmibs@ietf.org>; Mon,  9 Jan 2012 16:09:23 -0800 (PST)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob102.postini.com ([64.18.6.12]) with SMTP ID DSNKTwuBpHC9icJhhHIplwfrv8D08XDGSnfd@postini.com; Mon, 09 Jan 2012 16:09:23 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; Mon, 9 Jan 2012 16:05:52 -0800
From: Jeff Haas <jhaas@juniper.net>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Date: Mon, 9 Jan 2012 16:05:55 -0800
Thread-Topic: [IETFMIBS] Extending InetAddress(Type) for BGP Multicast VPNs
Thread-Index: AczPK52shvkES1LgSrqnUhhEQ5RUUg==
Message-ID: <52539B15-9568-486D-9E04-5F753DA2BFAC@juniper.net>
References: <CBFBAE7D-EFBC-4833-9DD5-C2659C00F419@juniper.net> <20120109234012.GA93650@elstar.local>
In-Reply-To: <20120109234012.GA93650@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: Tue, 10 Jan 2012 00:09:23 -0000

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 th=
at's a minor detail.  Please refer to section 4 for the different route for=
mats to avoid significant copy and paste.

My proposal is that 7 code points are allocated for MVPN routes for InetAdd=
ressType for these 7 types of information.  Textual conventions would be de=
fined to cover each of the appropriate types.

One small annoyance is that the DISPLAY-HINT syntax isn't quite flexible en=
ough 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, w=
e'll submit some text for the MIB.

-- Jeff


From dromasca@avaya.com  Tue Jan 10 02:52:45 2012
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.=20

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
>=20
> Juergen,
>=20
> 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.
>=20
> Reference:
> http://tools.ietf.org/html/draft-ietf-l3vpn-2547bis-mcast-bgp-08
>=20
> 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.
>=20
> 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.
>=20
> 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.
>=20
> If this proposal seems to have merit and would be likely to get
> traction, we'll submit some text for the MIB.
>=20
> -- Jeff
>=20
> _______________________________________________
> IETFMIBS mailing list
> IETFMIBS@ietf.org
> https://www.ietf.org/mailman/listinfo/ietfmibs

From j.schoenwaelder@jacobs-university.de  Tue Jan 10 02:55:01 2012
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 AA8DB21F861F for <ietfmibs@ietfa.amsl.com>; Tue, 10 Jan 2012 02:55:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.249
X-Spam-Level: 
X-Spam-Status: No, score=-103.249 tagged_above=-999 required=5 tests=[AWL=0.000, 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 g40HDJk-dJLs for <ietfmibs@ietfa.amsl.com>; Tue, 10 Jan 2012 02:55:01 -0800 (PST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id DAAFA21F84D7 for <ietfmibs@ietf.org>; Tue, 10 Jan 2012 02:54:54 -0800 (PST)
Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id D31E320BDE; Tue, 10 Jan 2012 11:54:53 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id vFW7R4eo0U9f; Tue, 10 Jan 2012 11:54:53 +0100 (CET)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 696B720AFE; Tue, 10 Jan 2012 11:54:53 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id EDAF71C606B8; Tue, 10 Jan 2012 11:54:34 +0100 (CET)
Date: Tue, 10 Jan 2012 11:54:33 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Jeff Haas <jhaas@juniper.net>
Message-ID: <20120110105431.GC94367@elstar.local>
References: <CBFBAE7D-EFBC-4833-9DD5-C2659C00F419@juniper.net> <20120109234012.GA93650@elstar.local> <52539B15-9568-486D-9E04-5F753DA2BFAC@juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <52539B15-9568-486D-9E04-5F753DA2BFAC@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: Tue, 10 Jan 2012 10:55:01 -0000

On Mon, Jan 09, 2012 at 04:05:55PM -0800, Jeff Haas wrote:
> 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.

What I see in section 4 of draft-ietf-l3vpn-2547bis-mcast-bgp-08 does
not seem to be Internet addresses. There are quite a number of MIB
modules using InetAddressType and InetAddress and pretty much for all
of them these additions likely do not make sense. So either I do not
understand the proposal yet or if I understand it correctly, I tend to
not like it.

/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/>

From brian@innovationslab.net  Tue Jan 10 04:58:23 2012
Return-Path: <brian@innovationslab.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 83A9421F8649 for <ietfmibs@ietfa.amsl.com>; Tue, 10 Jan 2012 04:58:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 RuE7Ug9Aamtc for <ietfmibs@ietfa.amsl.com>; Tue, 10 Jan 2012 04:58:22 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id BD61221F8644 for <ietfmibs@ietf.org>; Tue, 10 Jan 2012 04:58:22 -0800 (PST)
Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 896F78809B for <ietfmibs@ietf.org>; Tue, 10 Jan 2012 04:58:22 -0800 (PST)
Received: from clemson.jhuapl.edu (unknown [128.244.243.28]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 3D06D130002 for <ietfmibs@ietf.org>; Tue, 10 Jan 2012 04:58:22 -0800 (PST)
Message-ID: <4F0C35ED.8060705@innovationslab.net>
Date: Tue, 10 Jan 2012 07:58:21 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: ietfmibs@ietf.org
References: <CBFBAE7D-EFBC-4833-9DD5-C2659C00F419@juniper.net> <20120109234012.GA93650@elstar.local> <52539B15-9568-486D-9E04-5F753DA2BFAC@juniper.net> <20120110105431.GC94367@elstar.local>
In-Reply-To: <20120110105431.GC94367@elstar.local>
X-Enigmail-Version: 1.3.4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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 12:58:23 -0000

Hi Juergen,

On 1/10/12 5:54 AM, Juergen Schoenwaelder wrote:
> On Mon, Jan 09, 2012 at 04:05:55PM -0800, Jeff Haas wrote:
>> 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.
> 
> What I see in section 4 of draft-ietf-l3vpn-2547bis-mcast-bgp-08 does
> not seem to be Internet addresses. There are quite a number of MIB
> modules using InetAddressType and InetAddress and pretty much for all
> of them these additions likely do not make sense. So either I do not
> understand the proposal yet or if I understand it correctly, I tend to
> not like it.

I suspect that Jeff wants to introduce 7 new values for InetAddressType
that allows him to represent these seven types of routes:

     + 1 - Intra-AS I-PMSI A-D route;
     + 2 - Inter-AS I-PMSI A-D route;
     + 3 - S-PMSI A-D route;
     + 4 - Leaf A-D route;
     + 5 - Source Active A-D route.
     + 6 - Shared Tree Join route;
     + 7 - Source Tree Join route;

I would have to see a more concrete proposal, but it seems a unwieldy
given that each of the above types could occur for both IPv4 and IPv6
addresses.  So that would require more than seven new values for
InetAddressType.  Unless I am not understanding the referenced draft
correctly...

Regards,
Brian

From jhaas@juniper.net  Tue Jan 10 06:30:44 2012
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 B436821F85FD for <ietfmibs@ietfa.amsl.com>; Tue, 10 Jan 2012 06:30:44 -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 A49bbUv6fo6c for <ietfmibs@ietfa.amsl.com>; Tue, 10 Jan 2012 06:30:44 -0800 (PST)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by ietfa.amsl.com (Postfix) with ESMTP id E76D021F85F8 for <ietfmibs@ietf.org>; Tue, 10 Jan 2012 06:30:43 -0800 (PST)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKTwxLhkhMtIVQhCA8nNsDYezMzQG7WBRY@postini.com; Tue, 10 Jan 2012 06:30:44 PST
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB01-HQ.jnpr.net ([fe80::fc92:eb1:759:2c72%11]) with mapi; Tue, 10 Jan 2012 06:28:06 -0800
From: Jeff Haas <jhaas@juniper.net>
To: Brian Haberman <brian@innovationslab.net>
Date: Tue, 10 Jan 2012 06:28:09 -0800
Thread-Topic: [IETFMIBS] Extending InetAddress(Type) for BGP Multicast VPNs
Thread-Index: AczPpBFEW207VPGpRKe7zK6wBjawqA==
Message-ID: <28D0A91D-4C9B-4562-9495-639A38394194@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>
In-Reply-To: <4F0C35ED.8060705@innovationslab.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="Windows-1252"
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: Tue, 10 Jan 2012 14:30:44 -0000

Brian,

Since your response is closest to my intentions, I'll answer here:

On Jan 10, 2012, at 7:58 AM, Brian Haberman wrote:
> I suspect that Jeff wants to introduce 7 new values for InetAddressType
> that allows him to represent these seven types of routes:
>=20
>     + 1 - Intra-AS I-PMSI A-D route;
>     + 2 - Inter-AS I-PMSI A-D route;
>     + 3 - S-PMSI A-D route;
>     + 4 - Leaf A-D route;
>     + 5 - Source Active A-D route.
>     + 6 - Shared Tree Join route;
>     + 7 - Source Tree Join route;
>=20
> I would have to see a more concrete proposal, but it seems a unwieldy
> given that each of the above types could occur for both IPv4 and IPv6
> addresses.  So that would require more than seven new values for
> InetAddressType.  Unless I am not understanding the referenced draft
> correctly=85

You and Juergen are understanding this perfectly fine.

Also, as I expected, you're all not very fond of the idea (using differing =
wording in the various responses, but it's clear).  That saved having the d=
iscussion complicated by providing sample SMI.

What this means is, as the editor of the BGP MIB, I now have to ask and ans=
wer a slightly different problem.  I made use of the InetAddress MIB so tha=
t we could take advantage of the flexibility to cover both IPv4 and IPv6 re=
achability for our peering sessions as well as our prefixes.  However, BGP =
is capable of carrying more reachability than simply IPv4 or IPv6; in the e=
xample case, it's MVPN.  We also support things like VPLS.

This seems to suggest that BGP needs to copy and fork InetAddressType/InetA=
ddress (and perhaps the prefix length TC as well) for a BGP specific MIB th=
at can accommodate non-IP prefixes.

I would love an alternate suggestion to doing this since I do not relish th=
e idea of maintaining such a TC MIB indefinitely. :-)

(I also understood that was exactly what I was asking the owners of INET-AD=
DRESS-MIB to do.)

One property such a BGP-specific MIB should have is to use the same code po=
ints as the INET-ADDRESS-MIB where possible.  This would enable code re-use=
.

Is my logic correct?

-- Jeff=

From j.schoenwaelder@jacobs-university.de  Tue Jan 10 06:41:28 2012
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 6EB4421F86EC for <ietfmibs@ietfa.amsl.com>; Tue, 10 Jan 2012 06:41:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.249
X-Spam-Level: 
X-Spam-Status: No, score=-103.249 tagged_above=-999 required=5 tests=[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 J28+0c6UFV2i for <ietfmibs@ietfa.amsl.com>; Tue, 10 Jan 2012 06:41:27 -0800 (PST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 4CA6221F86EB for <ietfmibs@ietf.org>; Tue, 10 Jan 2012 06:41:27 -0800 (PST)
Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id A050F20BE9; Tue, 10 Jan 2012 15:41:26 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id IQC7S7dUR5-g; Tue, 10 Jan 2012 15:41:26 +0100 (CET)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 4183920BDC; Tue, 10 Jan 2012 15:41:26 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id A5F5B1C61BC9; Tue, 10 Jan 2012 15:41:09 +0100 (CET)
Date: Tue, 10 Jan 2012 15:41:09 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Jeff Haas <jhaas@juniper.net>
Message-ID: <20120110144109.GD95306@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>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <28D0A91D-4C9B-4562-9495-639A38394194@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: Tue, 10 Jan 2012 14:41:28 -0000

On Tue, Jan 10, 2012 at 06:28:09AM -0800, Jeff Haas wrote:
> Brian,
> 
> Since your response is closest to my intentions, I'll answer here:
> 
> On Jan 10, 2012, at 7:58 AM, Brian Haberman wrote:
> > I suspect that Jeff wants to introduce 7 new values for InetAddressType
> > that allows him to represent these seven types of routes:
> > 
> >     + 1 - Intra-AS I-PMSI A-D route;
> >     + 2 - Inter-AS I-PMSI A-D route;
> >     + 3 - S-PMSI A-D route;
> >     + 4 - Leaf A-D route;
> >     + 5 - Source Active A-D route.
> >     + 6 - Shared Tree Join route;
> >     + 7 - Source Tree Join route;
> > 
> > I would have to see a more concrete proposal, but it seems a unwieldy
> > given that each of the above types could occur for both IPv4 and IPv6
> > addresses.  So that would require more than seven new values for
> > InetAddressType.  Unless I am not understanding the referenced draft
> > correctly…
> 
> You and Juergen are understanding this perfectly fine.
> 
> Also, as I expected, you're all not very fond of the idea (using differing wording in the various responses, but it's clear).  That saved having the discussion complicated by providing sample SMI.
> 
> What this means is, as the editor of the BGP MIB, I now have to ask and answer a slightly different problem.  I made use of the InetAddress MIB so that we could take advantage of the flexibility to cover both IPv4 and IPv6 reachability for our peering sessions as well as our prefixes.  However, BGP is capable of carrying more reachability than simply IPv4 or IPv6; in the example case, it's MVPN.  We also support things like VPLS.
> 
> This seems to suggest that BGP needs to copy and fork InetAddressType/InetAddress (and perhaps the prefix length TC as well) for a BGP specific MIB that can accommodate non-IP prefixes.
> 
> I would love an alternate suggestion to doing this since I do not relish the idea of maintaining such a TC MIB indefinitely. :-)
> 
> (I also understood that was exactly what I was asking the owners of INET-ADDRESS-MIB to do.)
> 
> One property such a BGP-specific MIB should have is to use the same code points as the INET-ADDRESS-MIB where possible.  This would enable code re-use.
> 
> Is my logic correct?

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.

/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/>

From jhaas@juniper.net  Sat Jan 14 08:17:20 2012
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 poi=
nts by reference?  The BGP protocol suite continues to evolve at a very ste=
ady pace and it would be nice if I could point to new code points at IANA r=
ather than having a MIB document that could never be stable enough to reall=
y reach an RFC, except perhaps for a snapshot.

-- Jeff


From jcucchiara@mindspring.com  Sat Jan 14 10:06:20 2012
Return-Path: <jcucchiara@mindspring.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 E810921F84FE for <ietfmibs@ietfa.amsl.com>; Sat, 14 Jan 2012 10:06:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
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 WvUSagPXquF9 for <ietfmibs@ietfa.amsl.com>; Sat, 14 Jan 2012 10:06:20 -0800 (PST)
Received: from elasmtp-spurfowl.atl.sa.earthlink.net (elasmtp-spurfowl.atl.sa.earthlink.net [209.86.89.66]) by ietfa.amsl.com (Postfix) with ESMTP id 3250C21F84B2 for <ietfmibs@ietf.org>; Sat, 14 Jan 2012 10:06:19 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=ti3udF8q6lw28msFrUnYIdZa9RDMHMTz9GK8Tvhm7ff6GoWBz7TkinqrJlqB7LFN; h=Received:Message-ID:From:To:Cc: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 [24.41.31.146] (helo=JoanPC) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <jcucchiara@mindspring.com>) id 1Rm7zb-0008Hi-H6; Sat, 14 Jan 2012 13:06:15 -0500
Message-ID: <75a101ccd2e7$3506d3e0$6601a8c0@JoanPC>
From: "Joan Cucchiara" <jcucchiara@mindspring.com>
To: "Jeff Haas" <jhaas@juniper.net>, "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de>
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>
Date: Sat, 14 Jan 2012 13:06:14 -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: 4d68bbe9cb71969ea344cf2d1a8e60840a9da525759e2654577745b4542a1dcdccd48f696c8d99c6c4f26bf0bb8d15d7350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 24.41.31.146
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: Sat, 14 Jan 2012 18:06:21 -0000

Hi Jeff,

If you are asking how to go about asking IANA to create a name space, the 
MIB Guidelines
doc discusses this.

http://www.rfc-editor.org/rfc/rfc4181.txt

MIB guidelines also discusses how MIB docs can add new values to these IANA 
maintained TCs.

I don't see the  point in having IANA maintain a TC-MIB, which is never used 
in an
actual RFC MIB.  While this might be easier for you, there is still work by 
someone.
Typically, the IANA considerations section that requests creating a new name 
space,
is included in a MIB document that is advancing to RFC status.   I don't 
know of  acceptions, but
maybe someone else does?

Thanks,
  -Joan





----- Original Message ----- 
From: "Jeff Haas" <jhaas@juniper.net>
To: "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de>
Cc: <ietfmibs@ietf.org>
Sent: Saturday, January 14, 2012 11:16 AM
Subject: Re: [IETFMIBS] Extending InetAddress(Type) for BGP Multicast VPNs


> 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
>
> _______________________________________________
> IETFMIBS mailing list
> IETFMIBS@ietf.org
> https://www.ietf.org/mailman/listinfo/ietfmibs 


From j.schoenwaelder@jacobs-university.de  Sun Jan 15 02:49:44 2012
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/>

From dromasca@avaya.com  Sun Jan 15 06:02:31 2012
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 87CEE21F846F for <ietfmibs@ietfa.amsl.com>; Sun, 15 Jan 2012 06:02:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.276
X-Spam-Level: 
X-Spam-Status: No, score=-103.276 tagged_above=-999 required=5 tests=[AWL=0.323, 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 Qz2kFV18ZzNM for <ietfmibs@ietfa.amsl.com>; Sun, 15 Jan 2012 06:02:31 -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 F088421F8469 for <ietfmibs@ietf.org>; Sun, 15 Jan 2012 06:02:30 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAC/cEk+HCzI1/2dsb2JhbABErTaBBYFyAQEBAQMSHgoxDgwEAgEIDQEDBAEBAQoGDAsBBgFFCQgBAQQBEggBGaF1mmGLNGMEmwSFC4dE
X-IronPort-AV: E=Sophos;i="4.71,513,1320642000"; d="scan'208";a="324543521"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 15 Jan 2012 09:02:27 -0500
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 15 Jan 2012 08:49:06 -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: Sun, 15 Jan 2012 15:02:23 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A0406F498A6@307622ANEX5.global.avaya.com>
In-Reply-To: <4DB4A319-8AA8-4510-B2A9-42A06513F1C0@juniper.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [IETFMIBS] Extending InetAddress(Type) for BGP Multicast VPNs
Thread-Index: AczS1+WQapo71X+NQv6KaS0eTHol6QAtTe/Q
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>
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: Sun, 15 Jan 2012 14:02:31 -0000

> -----Original Message-----
> From: ietfmibs-bounces@ietf.org [mailto:ietfmibs-bounces@ietf.org] On
> Behalf Of Jeff Haas
> Sent: Saturday, January 14, 2012 6:17 PM
> To: Juergen Schoenwaelder
> Cc: ietfmibs@ietf.org
> Subject: Re: [IETFMIBS] Extending InetAddress(Type) for BGP Multicast
> VPNs
>=20
> Juergen,
>=20
> 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.
>=20
> It seems that I will be authoring (and probably maintaining) another
> BGP TC MIB for this purpose.
>=20
> 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.
>=20
> -- Jeff
>=20

Hi Jeff,

Do you refer to the IANA maintained MIB modules listed at
http://www.iana.org/protocols? The policy for extending each of the
modules is defined typically in the RFC where the TC is defined. If for
example 'Expert Review' (as the policy is for many of these) IANA passes
the requests to the expert designated by the IESG, who is evaluating and
advising IANA. I think that the process is well known and works pretty
well, but other people are invited to share their experiences.=20

Dan



From jhaas@juniper.net  Tue Jan 17 06:35:58 2012
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 C4EF021F85AE for <ietfmibs@ietfa.amsl.com>; Tue, 17 Jan 2012 06:35:58 -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 uxIAvn7sFnDF for <ietfmibs@ietfa.amsl.com>; Tue, 17 Jan 2012 06:35:58 -0800 (PST)
Received: from exprod7og127.obsmtp.com (exprod7og127.obsmtp.com [64.18.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id DD17C21F85A0 for <ietfmibs@ietf.org>; Tue, 17 Jan 2012 06:35:57 -0800 (PST)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob127.postini.com ([64.18.6.12]) with SMTP ID DSNKTxWHPhuYZoCApYf245i8syCsjh2fx4Aj@postini.com; Tue, 17 Jan 2012 06:35:57 PST
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB01-HQ.jnpr.net ([fe80::fc92:eb1:759:2c72%11]) with mapi; Tue, 17 Jan 2012 06:34:07 -0800
From: Jeff Haas <jhaas@juniper.net>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Date: Tue, 17 Jan 2012 06:34:04 -0800
Thread-Topic: [IETFMIBS] Extending InetAddress(Type) for BGP Multicast VPNs
Thread-Index: AczVJRFZNjqpI9mzSPab9MjCGsgI9Q==
Message-ID: <03D47A26-2966-40BB-A372-B560DAE2A57C@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> <4DB4A319-8AA8-4510-B2A9-42A06513F1C0@juniper.net> <EDC652A26FB23C4EB6384A4584434A0406F498A6@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0406F498A6@307622ANEX5.global.avaya.com>
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: Tue, 17 Jan 2012 14:35:58 -0000

Dan, Juergen, Joan,

Thanks for your kind responses.

On Jan 15, 2012, at 9:02 AM, Romascanu, Dan (Dan) wrote:
Do you refer to the IANA maintained MIB modules listed at
http://www.iana.org/protocols? The policy for extending each of the
modules is defined typically in the RFC where the TC is defined. If for
example 'Expert Review' (as the policy is for many of these) IANA passes
the requests to the expert designated by the IESG, who is evaluating and
advising IANA. I think that the process is well known and works pretty
well, but other people are invited to share their experiences.

This was exactly the sort of thing I was looking for.  It avoids my problem=
 of a never-really-published MIB that is constantly being updated for the B=
GP MIBv2.

Joan had written earlier:
I don't see the  point in having IANA maintain a TC-MIB, which is never use=
d
in an
actual RFC MIB.  While this might be easier for you, there is still work by
someone.
Typically, the IANA considerations section that requests creating a new nam=
e
space,
is included in a MIB document that is advancing to RFC status.   I don't
know of  acceptions, but
maybe someone else does?

Please recall that the purpose of this is to help make the BGP MIBv2 (which=
 is standards track) be more generally useful for BGP address families.

If your point was that an initial MIB document is required to bootstrap the=
 request for IANA to maintain a TC MIB per RFC 4181, that's understandable.

-- Jeff


From jcucchiara@mindspring.com  Tue Jan 17 07:04:24 2012
Return-Path: <jcucchiara@mindspring.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 275DC21F86F8 for <ietfmibs@ietfa.amsl.com>; Tue, 17 Jan 2012 07:04:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
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 b-kB0edyJzpj for <ietfmibs@ietfa.amsl.com>; Tue, 17 Jan 2012 07:04:23 -0800 (PST)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by ietfa.amsl.com (Postfix) with ESMTP id 53C1821F86CE for <ietfmibs@ietf.org>; Tue, 17 Jan 2012 07:04:23 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=Hb8ShvlafJ1q9+MHcWmTS+V3jKHm7JyNHzialOc2aMZENVZUXq2aeugAIOUM6Hr2; h=Received:Message-ID:From:To:Cc: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 [24.41.31.146] (helo=JoanPC) by elasmtp-mealy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <jcucchiara@mindspring.com>) id 1RnAaB-0007YV-Tr; Tue, 17 Jan 2012 10:04:19 -0500
Message-ID: <39eb01ccd529$0062c470$6601a8c0@JoanPC>
From: "Joan Cucchiara" <jcucchiara@mindspring.com>
To: "Jeff Haas" <jhaas@juniper.net>, "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
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><EDC652A26FB23C4EB6384A4584434A0406F498A6@307622ANEX5.global.avaya.com> <03D47A26-2966-40BB-A372-B560DAE2A57C@juniper.net>
Date: Tue, 17 Jan 2012 10:02:15 -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: 4d68bbe9cb71969ea344cf2d1a8e60840a9da525759e2654ea830ce65b1e232620b3672795f7bd6692764449e275203c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 24.41.31.146
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, 17 Jan 2012 15:04:24 -0000

Jeff,

Could you remind me again what the requirements are by the the IDR WG to 
have
a document advance to RFC status?   As I recall, this is more involved than 
what is required by
other WGs.

Could you also tell us what the status is of the BGPv2 MIBs with respect to 
the
IDR WG requirements?

Thank you,
  -Joan


----- Original Message ----- 
From: "Jeff Haas" <jhaas@juniper.net>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Cc: <ietfmibs@ietf.org>
Sent: Tuesday, January 17, 2012 9:34 AM
Subject: Re: [IETFMIBS] Extending InetAddress(Type) for BGP Multicast VPNs


> Dan, Juergen, Joan,
>
> Thanks for your kind responses.
>
> On Jan 15, 2012, at 9:02 AM, Romascanu, Dan (Dan) wrote:
> Do you refer to the IANA maintained MIB modules listed at
> http://www.iana.org/protocols? The policy for extending each of the
> modules is defined typically in the RFC where the TC is defined. If for
> example 'Expert Review' (as the policy is for many of these) IANA passes
> the requests to the expert designated by the IESG, who is evaluating and
> advising IANA. I think that the process is well known and works pretty
> well, but other people are invited to share their experiences.
>
> This was exactly the sort of thing I was looking for.  It avoids my 
> problem of a never-really-published MIB that is constantly being updated 
> for the BGP MIBv2.
>
> Joan had written earlier:
> I don't see the  point in having IANA maintain a TC-MIB, which is never 
> used
> in an
> actual RFC MIB.  While this might be easier for you, there is still work 
> by
> someone.
> Typically, the IANA considerations section that requests creating a new 
> name
> space,
> is included in a MIB document that is advancing to RFC status.   I don't
> know of  acceptions, but
> maybe someone else does?
>
> Please recall that the purpose of this is to help make the BGP MIBv2 
> (which is standards track) be more generally useful for BGP address 
> families.
>
> If your point was that an initial MIB document is required to bootstrap 
> the request for IANA to maintain a TC MIB per RFC 4181, that's 
> understandable.
>
> -- Jeff
>
> _______________________________________________
> IETFMIBS mailing list
> IETFMIBS@ietf.org
> https://www.ietf.org/mailman/listinfo/ietfmibs 


From jhaas@juniper.net  Tue Jan 17 07:47:15 2012
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 5C72221F8572 for <ietfmibs@ietfa.amsl.com>; Tue, 17 Jan 2012 07:47:15 -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=[AWL=0.000,  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 P9b4SA2rwF9I for <ietfmibs@ietfa.amsl.com>; Tue, 17 Jan 2012 07:47:15 -0800 (PST)
Received: from exprod7og118.obsmtp.com (exprod7og118.obsmtp.com [64.18.2.8]) by ietfa.amsl.com (Postfix) with ESMTP id B043921F856C for <ietfmibs@ietf.org>; Tue, 17 Jan 2012 07:47:14 -0800 (PST)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob118.postini.com ([64.18.6.12]) with SMTP ID DSNKTxWYAGBWMLWS1vcRGk4nnBCzYvdOyZmq@postini.com; Tue, 17 Jan 2012 07:47:14 PST
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB01-HQ.jnpr.net ([fe80::fc92:eb1:759:2c72%11]) with mapi; Tue, 17 Jan 2012 07:45:58 -0800
From: Jeff Haas <jhaas@juniper.net>
To: Joan Cucchiara <jcucchiara@mindspring.com>
Date: Tue, 17 Jan 2012 07:45:57 -0800
Thread-Topic: [IETFMIBS] Extending InetAddress(Type) for BGP Multicast VPNs
Thread-Index: AczVLxsjtsUJjT2rQYKo60kP4klyBg==
Message-ID: <4B6C3A87-D555-4E6F-B0A2-BA2E2BC13083@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><4DB4A319-8AA8-4510-B2A9-42A06513F1C0@juniper.net><EDC652A26FB23C4EB6384A4584434A0406F498A6@307622ANEX5.global.avaya.com> <03D47A26-2966-40BB-A372-B560DAE2A57C@juniper.net> <39eb01ccd529$0062c470$6601a8c0@JoanPC>
In-Reply-To: <39eb01ccd529$0062c470$6601a8c0@JoanPC>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
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: Tue, 17 Jan 2012 15:47:15 -0000

On Jan 17, 2012, at 10:02 AM, Joan Cucchiara wrote:
> Could you remind me again what the requirements are by the the IDR WG to=
=20
> have
> a document advance to RFC status?   As I recall, this is more involved th=
an=20
> what is required by
> other WGs.

Two independent implementations.

> Could you also tell us what the status is of the BGPv2 MIBs with respect =
to=20
> the
> IDR WG requirements?

Stable, but lacking implementation of the latest draft.  Juniper has an ent=
erprise MIB implementation of the older draft but I haven't had the opportu=
nity to update the implementation since joining.  (MIBs get poor attention =
from product managers in general.)  Another large vendor is rumored to have=
 an implementation in progress.

I also had most of an implementation in Quagga that I have yet to complete.=
  The majority of my problem was net-snmp issues with notifications, partic=
ularly with sysUpTime timestamps.
I probably should complete that just to push the standard.

-- Jeff


From adrian@olddog.co.uk  Tue Jan 17 10:48:58 2012
Return-Path: <adrian@olddog.co.uk>
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 017E421F8597 for <ietfmibs@ietfa.amsl.com>; Tue, 17 Jan 2012 10:48:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 JyUE-g4SHZgC for <ietfmibs@ietfa.amsl.com>; Tue, 17 Jan 2012 10:48:53 -0800 (PST)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 18C3A21F855D for <ietfmibs@ietf.org>; Tue, 17 Jan 2012 10:48:52 -0800 (PST)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id q0HImoGE008638;  Tue, 17 Jan 2012 18:48:51 GMT
Received: from 950129200 (86-83.77-83.cust.bluewin.ch [83.77.83.86]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id q0HImncr008608 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 17 Jan 2012 18:48:50 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Jeff Haas'" <jhaas@juniper.net>, "'Joan Cucchiara'" <jcucchiara@mindspring.com>
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><EDC652A26FB23C4EB6384A4584434A0406F498A6@307622ANEX5.global.avaya.com>	<03D47A26-2966-40BB-A372-B560DAE2A57C@juniper.net>	<39eb01ccd529$0062c470$6601a8c0@JoanPC> <4B6C3A87-D555-4E6F-B0A2-BA2E2BC13083@juniper.net>
In-Reply-To: <4B6C3A87-D555-4E6F-B0A2-BA2E2BC13083@juniper.net>
Date: Tue, 17 Jan 2012 18:48:49 -0000
Message-ID: <018101ccd548$a7a10110$f6e30330$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
thread-index: AQGmo3JKdJR0MREEvSbSF1xLQ9WMKQD2v+OyARrYa/8BgKlECgG7KNukAgg97WkChTDVdwGj6zjXAnT7vXoCYikDSwHToJjLAV7as8iVwQZ5IA==
Content-Language: en-gb
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
Reply-To: adrian@olddog.co.uk
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, 17 Jan 2012 18:48:58 -0000

Hi,

The "two implementations" rule is imposed on a case-by-case basis by the IDR WG
chairs. It is usual for protocol modifications to BFD.  I am not aware of it
being enforced for MIB modules (indeed, I am not sure what would be meant by
"two interoperating independent implementations" of a MIB module).

Let's allow the WG chairs to decide what is needed in this case.

Cheers,
Adrian

> -----Original Message-----
> From: ietfmibs-bounces@ietf.org [mailto:ietfmibs-bounces@ietf.org] On Behalf
> Of Jeff Haas
> Sent: 17 January 2012 15:46
> To: Joan Cucchiara
> Cc: ietfmibs@ietf.org
> Subject: Re: [IETFMIBS] Extending InetAddress(Type) for BGP Multicast VPNs
> 
> 
> On Jan 17, 2012, at 10:02 AM, Joan Cucchiara wrote:
> > Could you remind me again what the requirements are by the the IDR WG to
> > have
> > a document advance to RFC status?   As I recall, this is more involved than
> > what is required by
> > other WGs.
> 
> Two independent implementations.
> 
> > Could you also tell us what the status is of the BGPv2 MIBs with respect to
> > the IDR WG requirements?
> 
> Stable, but lacking implementation of the latest draft.  Juniper has an
enterprise
> MIB implementation of the older draft but I haven't had the opportunity to
> update the implementation since joining.  (MIBs get poor attention from
product
> managers in general.)  Another large vendor is rumored to have an
> implementation in progress.
> 
> I also had most of an implementation in Quagga that I have yet to complete.
The
> majority of my problem was net-snmp issues with notifications, particularly
with
> sysUpTime timestamps.
> I probably should complete that just to push the standard.
> 
> -- Jeff
> 
> _______________________________________________
> IETFMIBS mailing list
> IETFMIBS@ietf.org
> https://www.ietf.org/mailman/listinfo/ietfmibs


From dromasca@avaya.com  Wed Jan 18 03:33:01 2012
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 7E3C721F87BF for <ietfmibs@ietfa.amsl.com>; Wed, 18 Jan 2012 03:33:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.31
X-Spam-Level: 
X-Spam-Status: No, score=-103.31 tagged_above=-999 required=5 tests=[AWL=0.289, 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 j7LVgLZmzCbF for <ietfmibs@ietfa.amsl.com>; Wed, 18 Jan 2012 03:33:00 -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 ABFA921F8794 for <ietfmibs@ietf.org>; Wed, 18 Jan 2012 03:33:00 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAFKtFk+HCzI1/2dsb2JhbABErD6BAYEFgXIBAQEBAgEBAQEPHgo0CwUHBAIBCA0EBAEBAQoGDAsBBgEmHwkIAgQBEggah1gInHebdgSJMTYBBVYIAgcBAQIBAQgBAQEBAigOHAk3BQGBbTkeFgEBAQKCR2MEmwmMUA
X-IronPort-AV: E=Sophos;i="4.71,529,1320642000"; d="scan'208";a="325106316"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 18 Jan 2012 06:33:00 -0500
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 18 Jan 2012 06:19:34 -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: Wed, 18 Jan 2012 12:32:58 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A0407023C2B@307622ANEX5.global.avaya.com>
In-Reply-To: <018101ccd548$a7a10110$f6e30330$@olddog.co.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [IETFMIBS] Extending InetAddress(Type) for BGP Multicast VPNs
Thread-Index: AQGmo3JKdJR0MREEvSbSF1xLQ9WMKQD2v+OyARrYa/8BgKlECgG7KNukAgg97WkChTDVdwGj6zjXAnT7vXoCYikDSwHToJjLAV7as8iVwQZ5IIABGIMA
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><EDC652A26FB23C4EB6384A4584434A0406F498A6@307622ANEX5.global.avaya.com>	<03D47A26-2966-40BB-A372-B560DAE2A57C@juniper.net>	<39eb01ccd529$0062c470$6601a8c0@JoanPC><4B6C3A87-D555-4E6F-B0A2-BA2E2BC13083@juniper.net> <018101ccd548$a7a10110$f6e30330$@olddog.co.uk>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <adrian@olddog.co.uk>, "Jeff Haas" <jhaas@juniper.net>, "Joan Cucchiara" <jcucchiara@mindspring.com>
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: Wed, 18 Jan 2012 11:33:01 -0000

> I am not sure what would be
> meant by
> "two interoperating independent implementations" of a MIB module).

Roughly - the method used by the WGs developing MIB modules was to test
(at least) two independent implementations of agents and two
implementations of manager applications, run (at least) a complete MIB
walk on the respective MIB module and make sure that the results
obtained by the two applications from the two agents are consistent.=20

Regards,

Dan




> -----Original Message-----
> From: ietfmibs-bounces@ietf.org [mailto:ietfmibs-bounces@ietf.org] On
> Behalf Of Adrian Farrel
> Sent: Tuesday, January 17, 2012 8:49 PM
> To: 'Jeff Haas'; 'Joan Cucchiara'
> Cc: ietfmibs@ietf.org
> Subject: Re: [IETFMIBS] Extending InetAddress(Type) for BGP Multicast
> VPNs
>=20
> Hi,
>=20
> The "two implementations" rule is imposed on a case-by-case basis by
> the IDR WG
> chairs. It is usual for protocol modifications to BFD.  I am not aware
> of it
> being enforced for MIB modules (indeed, I am not sure what would be
> meant by
> "two interoperating independent implementations" of a MIB module).
>=20
> Let's allow the WG chairs to decide what is needed in this case.
>=20
> Cheers,
> Adrian
>=20
> > -----Original Message-----
> > From: ietfmibs-bounces@ietf.org [mailto:ietfmibs-bounces@ietf.org]
On
> Behalf
> > Of Jeff Haas
> > Sent: 17 January 2012 15:46
> > To: Joan Cucchiara
> > Cc: ietfmibs@ietf.org
> > Subject: Re: [IETFMIBS] Extending InetAddress(Type) for BGP
Multicast
> VPNs
> >
> >
> > On Jan 17, 2012, at 10:02 AM, Joan Cucchiara wrote:
> > > Could you remind me again what the requirements are by the the IDR
> WG to
> > > have
> > > a document advance to RFC status?   As I recall, this is more
> involved than
> > > what is required by
> > > other WGs.
> >
> > Two independent implementations.
> >
> > > Could you also tell us what the status is of the BGPv2 MIBs with
> respect to
> > > the IDR WG requirements?
> >
> > Stable, but lacking implementation of the latest draft.  Juniper has
> an
> enterprise
> > MIB implementation of the older draft but I haven't had the
> opportunity to
> > update the implementation since joining.  (MIBs get poor attention
> from
> product
> > managers in general.)  Another large vendor is rumored to have an
> > implementation in progress.
> >
> > I also had most of an implementation in Quagga that I have yet to
> complete.
> The
> > majority of my problem was net-snmp issues with notifications,
> particularly
> with
> > sysUpTime timestamps.
> > I probably should complete that just to push the standard.
> >
> > -- Jeff
> >
> > _______________________________________________
> > IETFMIBS mailing list
> > IETFMIBS@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietfmibs
>=20
> _______________________________________________
> IETFMIBS mailing list
> IETFMIBS@ietf.org
> https://www.ietf.org/mailman/listinfo/ietfmibs
