IETF Logo Mail Archive

Re: [sidr] adopt a mib

Robert Raszuk <raszuk@cisco.com> Fri, 05 August 2011 06:39 UTC

Return-Path: <raszuk@cisco.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5EBD21F863E for <sidr@ietfa.amsl.com>; Thu, 4 Aug 2011 23:39:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.339
X-Spam-Level:
X-Spam-Status: No, score=-3.339 tagged_above=-999 required=5 tests=[AWL=-0.740, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ekjW3LeImwpp for <sidr@ietfa.amsl.com>; Thu, 4 Aug 2011 23:39:03 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 0D7C221F84E1 for <sidr@ietf.org>; Thu, 4 Aug 2011 23:39:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=raszuk@cisco.com; l=1056; q=dns/txt; s=iport; t=1312526360; x=1313735960; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=stCSLt0sGTJo64omIPLhpQ5HqsJ1xOBQ4vR2yKyJkU4=; b=Nld4+rPr7DeCwk1CVB5sgl8oXNpzVrecm+PdVy3Kt+7qBHVZYEFAY/rk EQ0URqgOEWbXPdU4mnsKaNvpmD92iZCbxJWPygcWwS+IA/BYNLOSBTSCl DfMYPpwoVOY1IhjZwkMnlQG9U8oN808ZSG8IEwANxOpAGeCwOkbNhFGRT s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAOGPO06rRDoI/2dsb2JhbABDp3B3gUABAQEBAgESAQIBIkEFCwsYCSUPAkYGDQEHAQEeh0uiNAGDHA8Bm0SGRgSHW4skhQiLfw
X-IronPort-AV: E=Sophos;i="4.67,321,1309737600"; d="scan'208";a="9928618"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by rcdn-iport-5.cisco.com with ESMTP; 05 Aug 2011 06:39:19 +0000
Received: from [10.21.108.126] ([10.21.108.126]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p756dI3Q029347; Fri, 5 Aug 2011 06:39:19 GMT
Message-ID: <4E3B9018.80808@cisco.com>
Date: Thu, 04 Aug 2011 23:39:20 -0700
From: Robert Raszuk <raszuk@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: "Bert (IETF) Wijnen" <bertietf@bwijnen.net>
References: <m2d3gkepg8.wl%randy@psg.com> <4E3B8930.9090605@cisco.com> <4E3B8EB1.7030007@bwijnen.net>
In-Reply-To: <4E3B8EB1.7030007@bwijnen.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: sidr wg list <sidr@ietf.org>
Subject: Re: [sidr] adopt a mib
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: raszuk@cisco.com
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sidr>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2011 06:39:03 -0000

Hi Bert,

Many thx for your comment .. I was not able to stay at the IETF till the 
SIDR session.

If that is the case the draft-ymbk-bgp-origin-validation-mib is just 
completely not ready for adoption until it contains bare minimum which 
will allow operators to use it.

It would be insane to list 1 million of valid prefixes as opposed to 
little fraction of them being in question. Whoever authored that draft 
needs to develop a bit more real network operational experience :)

Best regards,
R.

> During the discussion at the SIDR WG session at IETF81 we
> found that the bgpVRTValid attribute in that table makes no
> sense, because we do not have that info. These are ALL
> validated ROAs (or better validated prefixes) as I understand
> it.
>
> Bert
> On 8/5/11 8:09 AM, Robert Raszuk wrote:
>> Hi,
>>
>> Just looking at draft-ymbk-bgp-origin-validation-mib may I ask what
>> would be the root OID string to start SNMP tree walk (or set the trap)
>> to list all INVALID or NOT_FOUND BGP entries ?
>>
>> Rgs,
>> R.

v2.23.0 | Report a Bug | By Email