From mark@ellisonsoftware.com Thu Jul 15 09:55:06 2010 Return-Path: X-Original-To: ietfmibs@core3.amsl.com Delivered-To: ietfmibs@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E1F1E3A685C for ; Thu, 15 Jul 2010 09:55:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.976 X-Spam-Level: X-Spam-Status: No, score=-101.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id puDsWdiCfQcw for ; Thu, 15 Jul 2010 09:55:04 -0700 (PDT) Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 8CD673A6818 for ; Thu, 15 Jul 2010 09:55:04 -0700 (PDT) Received: by vws14 with SMTP id 14so1464029vws.31 for ; Thu, 15 Jul 2010 09:55:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.62.5 with SMTP id v5mr9797423vch.221.1279212912232; Thu, 15 Jul 2010 09:55:12 -0700 (PDT) Sender: mark@ellisonsoftware.com Received: by 10.220.201.12 with HTTP; Thu, 15 Jul 2010 09:55:12 -0700 (PDT) Date: Thu, 15 Jul 2010 12:55:12 -0400 X-Google-Sender-Auth: r_lamTYl7TyKDxiPq4xRx5enDfk Message-ID: From: Mark Ellison To: ietfmibs@ietf.org Content-Type: multipart/alternative; boundary=e0cb4e887ee939cb20048b6ff78d Cc: droasca@avaya.com, bwijnen@alcatel-lucent.com Subject: [IETFMIBS] Security Guidelines for IETF MIB modules X-BeenThere: ietfmibs@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF MIB Discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jul 2010 16:55:06 -0000 --e0cb4e887ee939cb20048b6ff78d Content-Type: text/plain; charset=ISO-8859-1 Hi, Today, in working with the boilerplate text for the security considerations (http://ops.ietf.org/mib-security.html) I found a minor spelling error that could be fixed. In the formatted text under "X. Security Considerations", the third '--' comment paragraph, last line: s/unathorized/unauthorized/ This spelling error also appears in the nroff source. Regards, Mark http://EllisonSoftware.com/ --e0cb4e887ee939cb20048b6ff78d Content-Type: text/html; charset=ISO-8859-1 Hi,

Today, in working with the boilerplate text for the security considerations (http://ops.ietf.org/mib-security.html) I found a minor spelling error that could be fixed.

In the formatted text under "X. Security Considerations", the third '--' comment paragraph, last line: s/unathorized/unauthorized/

This spelling error also appears in the nroff source.

Regards,

Mark
http://EllisonSoftware.com/
--e0cb4e887ee939cb20048b6ff78d-- From dromasca@avaya.com Sun Jul 18 09:45:49 2010 Return-Path: X-Original-To: ietfmibs@core3.amsl.com Delivered-To: ietfmibs@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DC5D63A693F for ; Sun, 18 Jul 2010 09:45:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.11 X-Spam-Level: X-Spam-Status: No, score=-2.11 tagged_above=-999 required=5 tests=[AWL=0.488, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Fs8LoGtGKBu for ; Sun, 18 Jul 2010 09:45:48 -0700 (PDT) Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (nj300815-nj-outbound.net.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id 6F3BD3A6926 for ; Sun, 18 Jul 2010 09:45:48 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.55,223,1278302400"; d="scan'208,217";a="25656464" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 18 Jul 2010 12:46:01 -0400 X-IronPort-AV: E=Sophos;i="4.55,223,1278302400"; d="scan'208,217";a="492657132" Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 18 Jul 2010 12:46:00 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB2698.B3D6A163" Date: Sun, 18 Jul 2010 18:45:59 +0200 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IETFMIBS] Security Guidelines for IETF MIB modules Thread-Index: AcskPoIW2PWZumR7RIeZr4ug/O1OyQCWgWhA References: From: "Romascanu, Dan (Dan)" To: "Mark Ellison" , Cc: droasca@avaya.com, bwijnen@alcatel-lucent.com Subject: Re: [IETFMIBS] Security Guidelines for IETF MIB modules X-BeenThere: ietfmibs@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF MIB Discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Jul 2010 16:45:50 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01CB2698.B3D6A163 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Thanks.=20 =20 As we are migrating this to a wiki I will make the correction in the wiki pages.=20 =20 Regards, =20 Dan =20 ________________________________ From: ietfmibs-bounces@ietf.org [mailto:ietfmibs-bounces@ietf.org] On Behalf Of Mark Ellison Sent: Thursday, July 15, 2010 7:55 PM To: ietfmibs@ietf.org Cc: droasca@avaya.com; bwijnen@alcatel-lucent.com Subject: [IETFMIBS] Security Guidelines for IETF MIB modules =09 =09 Hi, =09 Today, in working with the boilerplate text for the security considerations (http://ops.ietf.org/mib-security.html) I found a minor spelling error that could be fixed. =09 In the formatted text under "X. Security Considerations", the third '--' comment paragraph, last line: s/unathorized/unauthorized/ =09 This spelling error also appears in the nroff source. =09 Regards, =09 Mark http://EllisonSoftware.com/ =09 ------_=_NextPart_001_01CB2698.B3D6A163 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Thanks.
 
As we=20 are migrating this to a wiki I will make the correction in the wiki = pages.=20
 
Regards,
 
Dan
 


From: ietfmibs-bounces@ietf.org=20 [mailto:ietfmibs-bounces@ietf.org] On Behalf Of Mark=20 Ellison
Sent: Thursday, July 15, 2010 7:55 PM
To:=20 ietfmibs@ietf.org
Cc: droasca@avaya.com;=20 bwijnen@alcatel-lucent.com
Subject: [IETFMIBS] Security = Guidelines=20 for IETF MIB modules

Hi,

Today, in working with the boilerplate text for = the=20 security considerations (http://ops.ietf.org/mib-se= curity.html)=20 I found a minor spelling error that could be fixed.

In the = formatted=20 text under "X. Security Considerations", the third '--' comment = paragraph,=20 last line: s/unathorized/unauthorized/

This spelling error also = appears=20 in the nroff source.

Regards,

Mark
http://EllisonSoftware.com/
<= /BLOCKQUOTE> ------_=_NextPart_001_01CB2698.B3D6A163-- From rastrano@gmail.com Wed Jul 28 11:39:00 2010 Return-Path: X-Original-To: ietfmibs@core3.amsl.com Delivered-To: ietfmibs@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0D5163A681A; Wed, 28 Jul 2010 11:39:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.695 X-Spam-Level: X-Spam-Status: No, score=-1.695 tagged_above=-999 required=5 tests=[AWL=0.903, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y3r-nfTU1ipS; Wed, 28 Jul 2010 11:38:59 -0700 (PDT) Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 943A63A6974; Wed, 28 Jul 2010 11:38:58 -0700 (PDT) Received: by wyb40 with SMTP id 40so4689393wyb.31 for ; Wed, 28 Jul 2010 11:39:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type; bh=Nfvs/j3eCrf8CGLq50aGgLHwrAoFIkHW8kp8ZKFRdzE=; b=TIixaYjR++TzcKPV7ZGDYEHOLcwQC9air43HVpxbD6AMwRzGoUGvtlcwGj/P0V8Krx z9NXcG5Ca3Z4uzff8436taQxYHfDdXRonW+d95JxkD2Y4/Po+tTUwRExL1HUUW1/WZIt OvivvyCtBUtwzCQZCjyYS7WHkDjp2VMcjniLQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type; b=TZtpT3t6YtsNBk2BkcbkupbeqV/AfnrUdtJyUtJOMZXf8fIuF63AtRllPLgLdVPLpf bcBR16n2cha2rJ/TAgf8LYNg7BxhtntKhz8wKc+BfBJXZ7zBemt3cralyqGHa1p+zRg0 iyVcaBLG6T2qOVVnRFzdJ+bh06yCDQHzqZ9FQ= Received: by 10.227.69.10 with SMTP id x10mr10979785wbi.155.1280342361165; Wed, 28 Jul 2010 11:39:21 -0700 (PDT) Received: from [192.168.1.101] (dynamic-adsl-94-37-159-36.clienti.tiscali.it [94.37.159.36]) by mx.google.com with ESMTPS id e31sm5609935wbe.17.2010.07.28.11.39.20 (version=SSLv3 cipher=RC4-MD5); Wed, 28 Jul 2010 11:39:20 -0700 (PDT) Message-ID: <4C507959.10301@gmail.com> Date: Wed, 28 Jul 2010 20:39:21 +0200 From: Stefano Gargiulo User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; it; rv:1.9.1.11) Gecko/20100711 Lightning/1.0b1 Thunderbird/3.0.6 MIME-Version: 1.0 To: ietfmibs@ietf.org, idr@ietf.org Content-Type: multipart/alternative; boundary="------------060701080904080903020204" Subject: [IETFMIBS] SNMP bgpPeerTable IPV6 X-BeenThere: ietfmibs@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF MIB Discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jul 2010 18:43:31 -0000 This is a multi-part message in MIME format. --------------060701080904080903020204 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Hi, i'm sorry if this is not the right place to ask this, but i'm tring: Is there some proposal pending for implementing a *standard* bgp4 MIB with full support for Ipv6? Time is coming: in 2011/12 ipv4 will end all allocable space as you know. But my question is more pratical: How to monitoring ipv6 bgp peers? anyone does that now? how? I need to start from now, so i hope that a standard will come up soon... but for now i ask are there enterprise MIBs to do that on Juniper and Cisco routers? anyone knows the root OIDs? Thank you in advance, Best regards, Stefano. --------------060701080904080903020204 Content-Type: text/html; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Hi, i'm sorry if this is not the right place to ask this, but i'm tring:

Is there some proposal pending for implementing a standard bgp4 MIB with full support for Ipv6?

Time is coming: in 2011/12 ipv4 will end all allocable space as you know.

But my question is more pratical:
How to monitoring ipv6 bgp peers? anyone does that now? how?

I need to start from now, so i hope that a standard will come up soon... but for now i ask are there enterprise MIBs to do that on Juniper and Cisco routers? anyone knows the root OIDs?

Thank you in advance,
Best regards,
Stefano.

--------------060701080904080903020204-- From rastrano@gmail.com Thu Jul 29 07:24:52 2010 Return-Path: X-Original-To: ietfmibs@core3.amsl.com Delivered-To: ietfmibs@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2A6F13A67A4; Thu, 29 Jul 2010 07:24:52 -0700 (PDT) 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, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xnuLhH3z84+x; Thu, 29 Jul 2010 07:24:48 -0700 (PDT) Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id 91C573A680A; Thu, 29 Jul 2010 07:24:47 -0700 (PDT) Received: by eyb7 with SMTP id 7so138219eyb.31 for ; Thu, 29 Jul 2010 07:25:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type; bh=gYM1WGnBpJdVV9iYfmMTcBaxtLJEtit0ERLLNP4+7yo=; b=l+pH7jTwi061o2sG4rHtlgi4WT7xpXqw1ZbweXCdSLKYsgTofZV8VqwX3g4plG8p+R IlKxc5C0f6d09FQYA481nARGXPN68t1R+lbGXu/yRbrIgpgue/lzC6aieCGjdizkr1ix Auk8RnlzU/8VqrPFY+lpbZBQjTLCBA6NQrLXY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; b=e3OuyIfv2eiFOAX80wuXOwfQ+eUzEe6Ls3R0RCWP4hTNHxYIezM0e+r7u8UStu/u/D XXm9TyqTAosg3GCtVt88t6G2EQODLtj5+ymx6utIlFyxL5YTM3l7WNxaMkSWsII6Gygv IyfG2PhsrnJJFMjbxBmz7xKenmuiePLg68+SI= Received: by 10.227.146.4 with SMTP id f4mr233612wbv.14.1280413509233; Thu, 29 Jul 2010 07:25:09 -0700 (PDT) Received: from [193.206.158.194] (pcgarr66.dir.garr.it [193.206.158.194]) by mx.google.com with ESMTPS id i25sm781472wbi.22.2010.07.29.07.25.07 (version=SSLv3 cipher=RC4-MD5); Thu, 29 Jul 2010 07:25:08 -0700 (PDT) Message-ID: <4C518F28.8040007@gmail.com> Date: Thu, 29 Jul 2010 16:24:40 +0200 From: Stefano Gargiulo User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; it; rv:1.9.2.7) Gecko/20100713 Thunderbird/3.1.1 MIME-Version: 1.0 To: Kalpesh Zinjuwadia References: <4C507959.10301@gmail.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------050802030301010209010603" Cc: "idr@ietf.org" , "ietfmibs@ietf.org" Subject: Re: [IETFMIBS] [Idr] SNMP bgpPeerTable IPV6 X-BeenThere: ietfmibs@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF MIB Discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jul 2010 14:24:52 -0000 This is a multi-part message in MIME format. --------------050802030301010209010603 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Thank you so much Kalpesh. Best regards, Stefano. Il 28/07/2010 21:27, Kalpesh Zinjuwadia ha scritto: > > There is an ID for BGP4 MIBv2 which supports IPv6 AF (IPv6 peers, > NLRIs, etc). Not a public MIB yet. Check the vendor's MIB specs to > find out if it's supported and the enterprise-specific root OID. > > http://tools.ietf.org/html/draft-ietf-idr-bgp4-mibv2-10 > > Force10 supports it under FORCE10-BGP4-V2-MIB > > Thanks, > > Kalpesh > > *From:* idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] *On Behalf > Of *Stefano Gargiulo > *Sent:* Wednesday, July 28, 2010 11:39 AM > *To:* ietfmibs@ietf.org; idr@ietf.org > *Subject:* [Idr] SNMP bgpPeerTable IPV6 > > Hi, i'm sorry if this is not the right place to ask this, but i'm tring: > > Is there some proposal pending for implementing a *standard* bgp4 MIB > with full support for Ipv6? > > Time is coming: in 2011/12 ipv4 will end all allocable space as you know. > > But my question is more pratical: > How to monitoring ipv6 bgp peers? anyone does that now? how? > > I need to start from now, so i hope that a standard will come up > soon... but for now i ask are there enterprise MIBs to do that on > Juniper and Cisco routers? anyone knows the root OIDs? > > Thank you in advance, > Best regards, > Stefano. > --------------050802030301010209010603 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Thank you so much Kalpesh.

Best regards,
Stefano.


Il 28/07/2010 21:27, Kalpesh Zinjuwadia ha scritto:

There is an ID for BGP4 MIBv2 which supports IPv6 AF (IPv6 peers, NLRIs, etc). Not a public MIB yet. Check the vendor’s MIB specs to find out if it’s supported and the enterprise-specific root OID.

 

http://tools.ietf.org/html/draft-ietf-idr-bgp4-mibv2-10

 

Force10 supports it under FORCE10-BGP4-V2-MIB

 

Thanks,

Kalpesh

 

 

From: idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] On Behalf Of Stefano Gargiulo
Sent: Wednesday, July 28, 2010 11:39 AM
To: ietfmibs@ietf.org; idr@ietf.org
Subject: [Idr] SNMP bgpPeerTable IPV6

 

Hi, i'm sorry if this is not the right place to ask this, but i'm tring:

Is there some proposal pending for implementing a standard bgp4 MIB with full support for Ipv6?

Time is coming: in 2011/12 ipv4 will end all allocable space as you know.

But my question is more pratical:
How to monitoring ipv6 bgp peers? anyone does that now? how?

I need to start from now, so i hope that a standard will come up soon... but for now i ask are there enterprise MIBs to do that on Juniper and Cisco routers? anyone knows the root OIDs?

Thank you in advance,
Best regards,
Stefano.


--------------050802030301010209010603-- From kzinjuwadia@force10networks.com Wed Jul 28 12:27:02 2010 Return-Path: X-Original-To: ietfmibs@core3.amsl.com Delivered-To: ietfmibs@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5D65428B797; Wed, 28 Jul 2010 12:27:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.598 X-Spam-Level: X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rlah0KGDom4A; Wed, 28 Jul 2010 12:26:58 -0700 (PDT) Received: from mx.force10networks.com (corp.force10networks.com [64.186.164.204]) by core3.amsl.com (Postfix) with ESMTP id 709983A68D3; Wed, 28 Jul 2010 12:26:58 -0700 (PDT) Received: from EXCH-CLUSTER-09.force10networks.com ([10.11.10.113]) by exch7-sjc-fe.force10networks.com ([10.11.0.87]) with mapi; Wed, 28 Jul 2010 12:27:21 -0700 From: Kalpesh Zinjuwadia To: Stefano Gargiulo , "ietfmibs@ietf.org" , "idr@ietf.org" Date: Wed, 28 Jul 2010 12:27:18 -0700 Thread-Topic: [Idr] SNMP bgpPeerTable IPV6 Thread-Index: AcsuhNaJpE+wPdCHRr2wjddipaug1wABSm3w Message-ID: References: <4C507959.10301@gmail.com> In-Reply-To: <4C507959.10301@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_D5D07AB53D722442AB59544CFF470EA41B3DB5629BEXCHCLUSTER09_" MIME-Version: 1.0 X-Mailman-Approved-At: Thu, 29 Jul 2010 08:03:10 -0700 Subject: Re: [IETFMIBS] [Idr] SNMP bgpPeerTable IPV6 X-BeenThere: ietfmibs@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF MIB Discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jul 2010 19:27:02 -0000 --_000_D5D07AB53D722442AB59544CFF470EA41B3DB5629BEXCHCLUSTER09_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable There is an ID for BGP4 MIBv2 which supports IPv6 AF (IPv6 peers, NLRIs, et= c). Not a public MIB yet. Check the vendor's MIB specs to find out if it's = supported and the enterprise-specific root OID. http://tools.ietf.org/html/draft-ietf-idr-bgp4-mibv2-10 Force10 supports it under FORCE10-BGP4-V2-MIB Thanks, Kalpesh From: idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] On Behalf Of Stefa= no Gargiulo Sent: Wednesday, July 28, 2010 11:39 AM To: ietfmibs@ietf.org; idr@ietf.org Subject: [Idr] SNMP bgpPeerTable IPV6 Hi, i'm sorry if this is not the right place to ask this, but i'm tring: Is there some proposal pending for implementing a standard bgp4 MIB with fu= ll support for Ipv6? Time is coming: in 2011/12 ipv4 will end all allocable space as you know. But my question is more pratical: How to monitoring ipv6 bgp peers? anyone does that now? how? I need to start from now, so i hope that a standard will come up soon... bu= t for now i ask are there enterprise MIBs to do that on Juniper and Cisco r= outers? anyone knows the root OIDs? Thank you in advance, Best regards, Stefano. --_000_D5D07AB53D722442AB59544CFF470EA41B3DB5629BEXCHCLUSTER09_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

There is an ID for BGP4 MIBv2 which supports IPv6 AF (IPv6 peers, NLRIs, etc). Not a public MIB yet. Check the vendor’s MIB spec= s to find out if it’s supported and the enterprise-specific root OID.=

 

http://too= ls.ietf.org/html/draft-ietf-idr-bgp4-mibv2-10

 

Force10 supports it under FORCE10-BGP4-V2-MIB

 

Thanks,

Kalpesh

 

 

From: idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] On Behalf Of Stefano Gargiulo
Sent: Wednesday, July 28, 2010 11:39 AM
To: ietfmibs@ietf.org; idr@ietf.org
Subject: [Idr] SNMP bgpPeerTable IPV6

 

Hi, i'm sorry if this is not the right place to ask this, but i'm tring: In-Reply-To: <4C527775.3000007@ieca.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IETFMIBS] MIB Doctor Review: draft-ietf-isms-radius-vacm-09.txt Thread-Index: Acsv4XuRMAcK19CQTACQs/Iqt0tO3wAADjkQ References: <4C527775.3000007@ieca.com> From: "Romascanu, Dan (Dan)" To: "Sean Turner" , Subject: Re: [IETFMIBS] MIB Doctor Review: draft-ietf-isms-radius-vacm-09.txt X-BeenThere: ietfmibs@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF MIB Discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jul 2010 12:21:18 -0000 Any volunteers? Dan=20 > -----Original Message----- > From: ietfmibs-bounces@ietf.org=20 > [mailto:ietfmibs-bounces@ietf.org] On Behalf Of Sean Turner > Sent: Friday, July 30, 2010 9:56 AM > To: ietfmibs@ietf.org > Subject: [IETFMIBS] MIB Doctor Review:=20 > draft-ietf-isms-radius-vacm-09.txt >=20 > I would like a MIB Doctor review of the following ID (which=20 > is currently in AD review):=20 > draft-ietf-isms-radius-vacm-09.txt. Can I please note get=20 > Juergen, David H., and Randy as they were involved in the=20 > development of this I-D. >=20 > Thanks! >=20 > spt > _______________________________________________ > IETFMIBS mailing list > IETFMIBS@ietf.org > https://www.ietf.org/mailman/listinfo/ietfmibs >=20 From prvs=0827c1288d=simon.leinen@switch.ch Fri Jul 30 05:28:58 2010 Return-Path: X-Original-To: ietfmibs@core3.amsl.com Delivered-To: ietfmibs@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 757B03A693E; Fri, 30 Jul 2010 05:28:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 15L2rnxxTlry; Fri, 30 Jul 2010 05:28:57 -0700 (PDT) Received: from caval.switch.ch (caval.switch.ch [IPv6:2001:620:0:14::29]) by core3.amsl.com (Postfix) with ESMTP id 518B13A6967; Fri, 30 Jul 2010 05:28:57 -0700 (PDT) Received: from [2001:620:0:4:226:8ff:fe05:cfee] (helo=macsl.switch.ch) by caval.switch.ch with esmtp (Exim 4.69) (envelope-from ) id 1OeoiG-0005Jj-Dv; Fri, 30 Jul 2010 14:29:20 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <19538.50591.526381.713863@macsl.switch.ch> Date: Fri, 30 Jul 2010 14:29:19 +0200 From: Simon Leinen To: Kalpesh Zinjuwadia In-Reply-To: References: <4C507959.10301@gmail.com> X-Mailer: VM 8.1.0-devo-614 under 23.2.1 (x86_64-apple-darwin10.3.0) X-SWITCH-SCANNER: bypassed Cc: "idr@ietf.org" , "ietfmibs@ietf.org" Subject: Re: [IETFMIBS] [Idr] SNMP bgpPeerTable IPV6 X-BeenThere: ietfmibs@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF MIB Discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jul 2010 12:28:58 -0000 > There is an ID for BGP4 MIBv2 which supports IPv6 AF (IPv6 peers, > NLRIs, etc). Not a public MIB yet. Check the vendor's MIB specs to > find out if it's supported and the enterprise-specific root OID. > http://tools.ietf.org/html/draft-ietf-idr-bgp4-mibv2-10 This is an extremely important MIB to get standardized. As the original poster had said, how are we operators supposed to monitor IPv6 BGP peerings without something like this? The I-D has been active (growing and shrinking) over at least nine years: draft-ietf-idr-bgp4-mibv2-00 is from July 2001. Since I cannot currently follow the IDR WG, I don't know what's holding it up right now. Maybe just general loss of energy/shifting of priorities, which are unavoidable over such a long time. But pushing this towards RFC (at whatever standards level) would be a very honorable and worthwhile thing to do. > Force10 supports it under FORCE10-BGP4-V2-MIB Thanks, that's great to know. Force 10 just moved up two notches on my personal vendor sympathy scale. Of course your feedback (and that of users on the operator side, if any) would be very useful for advancing this in IDR. -- Simon.