Re: [sidr] adopt a mib

Robert Raszuk <raszuk@cisco.com> Mon, 08 August 2011 19:59 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 866DF11E80A8 for <sidr@ietfa.amsl.com>; Mon, 8 Aug 2011 12:59:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.128
X-Spam-Level:
X-Spam-Status: No, score=-3.128 tagged_above=-999 required=5 tests=[AWL=-0.529, 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 xgD-c3TMJiQs for <sidr@ietfa.amsl.com>; Mon, 8 Aug 2011 12:59:09 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id A925C11E80A7 for <sidr@ietf.org>; Mon, 8 Aug 2011 12:59:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=raszuk@cisco.com; l=3265; q=dns/txt; s=iport; t=1312833576; x=1314043176; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=y5SsPhmJ90ndGHFQyn8+WloeRQg8XQDBm2fUWMsvvd0=; b=QcsGnSAWzF4AiQEVdgOW+hsYFMS9pz09qhlJnF+UCctvQnmZc4MaOYJ8 KHqei7b2/GWgB52CZ2co26oQP3R2Rt/dBlCTRU4kzmJGFSo6t8NuXN4OQ HaLm3Mivfx5LHjvoJzCwO/YNE3PkmQ39BfNlmZVXjHhvO61hTHsqjPKGr U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EACs/QE6rRDoI/2dsb2JhbABDpyd3gUABAQEBAwEBAQ8BAgEiNgoBEAsYCRYPCQMCAQIBFTAGDQEFAgEBHodPoAgBgxwPAZtAhkcEkwKFCIti
X-IronPort-AV: E=Sophos;i="4.67,338,1309737600"; d="scan'208";a="10957743"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by rcdn-iport-1.cisco.com with ESMTP; 08 Aug 2011 19:59:35 +0000
Received: from [192.168.1.68] (sjc-raszuk-87113.cisco.com [10.20.147.254]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p78JxWtg010755; Mon, 8 Aug 2011 19:59:33 GMT
Message-ID: <4E404043.7080004@cisco.com>
Date: Mon, 08 Aug 2011 22:00:03 +0200
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: Michael Baer <baerm@mikesoffice.com>
References: <m2d3gkepg8.wl%randy@psg.com> <4E3B8930.9090605@cisco.com> <4E3B8EB1.7030007@bwijnen.net> <4E3B9018.80808@cisco.com> <m3wrenhi0c.fsf@mikesoffice.com>
In-Reply-To: <m3wrenhi0c.fsf@mikesoffice.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: robert@raszuk.net, 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: Mon, 08 Aug 2011 19:59:10 -0000

Hello Michael,

By all means this MIB extension is useful and I do support it's adoption.

I was only suggesting to perhaps wait just a bit and adopt something 
which we do already know will be needed in this MIB to avoid next rev 
just few days after the adoption and save authors of this MIB another 
submission cycle :) But You, Bert and Randy are so ready and open to 
continue enhancing it I see no show-stopper.

Once I will see new rev (regardless if this is WG item already or not 
yet) I will take a look again and provide my comments (if any are needed 
then :).

Many thx,
R.


>>>>>> On Thu, 04 Aug 2011 23:39:20 -0700, Robert Raszuk<raszuk@cisco.com>  said:
>
>      Robert>  Hi Bert,
>      Robert>  Many thx for your comment .. I was not able to stay at the IETF till
>      Robert>  the SIDR session.
>
>      Robert>  If that is the case the draft-ymbk-bgp-origin-validation-mib is just
>      Robert>  completely not ready for adoption until it contains bare minimum which
>      Robert>  will allow operators to use it.
>
>      Robert>  It would be insane to list 1 million of valid prefixes as opposed to
>      Robert>  little fraction of them being in question. Whoever authored that draft
>      Robert>  needs to develop a bit more real network operational experience :)
>
> Hi Robert,
>
> I am co-editing the MIB and was the person that originally put most of
> the MIB into SMI form.  Major flaws in the original MIB design are going
> to be mostly due to me.  My SNMP background is much greater than my
> routing knowledge, and I'm sure it shows (not shockingly, no network
> operator experience).  I expected and hoped to get feedback on what was
> wrong with the MIB and how it could be improved.
>
> I do look at WG at adoption criteria differently.  I can see your point
> of view.  But I generally look on adoption as whether a document/MIB is
> useful, and appropriate for a particular WG and not whether the first
> version of the doc/MIB is ready, with just minor adjustment, to be coded
> and used.
>
> But regardless of WG adoption, I am curious whether you think these MIBs
> would be useful to have, not in the current state, but in a closer to
> ideal state?
>
> And please give as much feedback as you can,
>
> Thanks,
> Mike
>
>
>      Robert>  Best regards,
>      Robert>  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.
>
>
>      Robert>  _______________________________________________
>      Robert>  sidr mailing list
>      Robert>  sidr@ietf.org
>      Robert>  https://www.ietf.org/mailman/listinfo/sidr
>
>