Re: [sidr] adopt a mib

"t.petch" <ietfc@btconnect.com> Mon, 08 August 2011 09:14 UTC

Return-Path: <ietfc@btconnect.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 9F4ED21F84F8 for <sidr@ietfa.amsl.com>; Mon, 8 Aug 2011 02:14:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.07
X-Spam-Level:
X-Spam-Status: No, score=-2.07 tagged_above=-999 required=5 tests=[AWL=0.530, 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 yW4oNCUR2m4Q for <sidr@ietfa.amsl.com>; Mon, 8 Aug 2011 02:14:54 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr08.btconnect.com [213.123.26.186]) by ietfa.amsl.com (Postfix) with ESMTP id 8373221F85AA for <sidr@ietf.org>; Mon, 8 Aug 2011 02:14:52 -0700 (PDT)
Received: from host81-159-99-55.range81-159.btcentralplus.com (HELO pc6) ([81.159.99.55]) by c2beaomr08.btconnect.com with SMTP id DVR73876; Mon, 08 Aug 2011 10:15:11 +0100 (BST)
Message-ID: <018a01cc55a2$d54a9700$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: Arturo Servin <aservin@lacnic.net>, sidr wg list <sidr@ietf.org>
References: <m2d3gkepg8.wl%randy@psg.com><Pine.WNT.4.64.1108051639160.1356@mw-PC> <823D382E-CEEC-419B-B80C-3B09F957BA21@lacnic.net>
Date: Mon, 08 Aug 2011 10:11:47 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0302.4E3FA91F.0033, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.8.8.75715:17:7.586, ip=81.159.99.55, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __CP_URI_IN_BODY, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_2000_2999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2beaomr08.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0203.4E3FA921.0264, ss=1, fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=multiengine
X-Junkmail-IWF: false
Subject: Re: [sidr] adopt a mib
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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 09:14:55 -0000

----- Original Message -----
From: "Arturo Servin" <aservin@lacnic.net>
To: "sidr wg list" <sidr@ietf.org>
Sent: Saturday, August 06, 2011 5:42 PM
>
> Support.
>
> Some comments.
>
> Roque previously mentioned something similar, for me it's a bit confusing to
talk about ROAs validity in a router. In my mind ROAs are validated somewhere
else and in routers you search for the validity of a prefix which I think what
is referenced here.
>
> Also, as Robert Raszuk mentioned I am a bit concerned that in order to get the
validity of a prefix first I need to get a table with ~400k entries. I do not
normally get a full table BGP via SNMP so may be my concern is unjustified by my
lack of experience. May be is it just the way it is with SNMP and we need to
live with it.

The way with SNMPv1, long superseded, but still around, is to get table entries
one at a time, and if the table is dynamic, this process may never end - I once
set such a retrieval going (on statistics data rather than routing) and
cancelled it three days later, still incomplete (a good way of stress testing
router control planes:-)

SNMPv2 has a smarter way of bulk data retrieval but it depends on having the
right table structure, that is it can efficiently retrieve a slice through some
of the columns.  If you have thousands of rows, most with property X and a few
with property Y, then it should work well if X/Y is an index to a column and Y
collates after X, that is what you want is at the bottom of the column (since
the retrieval works down a column and  ends at the end of the column [RFC3416]).

But you can still be sabotaged by considerations of maximum PDU so for me,
accessing large tables remains troublesome:-(

Tom Petch
>
> Cheers,
> -as
>
>
> On 5 Aug 2011, at 11:39, Matthias Waehlisch wrote:
>
> >
> > On Fri, 5 Aug 2011, Randy Bush wrote:
> >
> >> i would request the wg adopt
> >>
> >>    draft-ymbk-bgp-origin-validation-mib
> >>    draft-ymbk-rpki-rtr-protocol-mib
> >>
> >
> > I support the adoption, as well.
> >
> >
> > Cheers
> >  matthias
> >
> > --
> > Matthias Waehlisch
> > .  Freie Universitaet Berlin, Inst. fuer Informatik, AG CST
> > .  Takustr. 9, D-14195 Berlin, Germany
> > .. mailto:waehlisch@ieee.org .. http://www.inf.fu-berlin.de/~waehl
> > :. Also: http://inet.cpt.haw-hamburg.de .. http://www.link-lab.net
> > _______________________________________________
> > sidr mailing list
> > sidr@ietf.org
> > https://www.ietf.org/mailman/listinfo/sidr
>
> _______________________________________________
> sidr mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr