IETF Logo Mail Archive

Re: [sidr] Injecting idea of "freshness of repository data" into BGP

Christopher Morrow <morrowc.lists@gmail.com> Fri, 30 March 2012 09:44 UTC

Return-Path: <christopher.morrow@gmail.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 C287421F8878 for <sidr@ietfa.amsl.com>; Fri, 30 Mar 2012 02:44:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.564
X-Spam-Level:
X-Spam-Status: No, score=-103.564 tagged_above=-999 required=5 tests=[AWL=0.035, 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 EN1LeRp39kqa for <sidr@ietfa.amsl.com>; Fri, 30 Mar 2012 02:44:22 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3D5F321F888C for <sidr@ietf.org>; Fri, 30 Mar 2012 02:44:22 -0700 (PDT)
Received: by obbta17 with SMTP id ta17so870163obb.31 for <sidr@ietf.org>; Fri, 30 Mar 2012 02:44:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=SB1nFFOemG44F07hl+UCctS98j5D2nESZYA3Bc0BbOw=; b=rokbsqoSn12Kkfqz6k0CYxM7jsEv7Rho3N21z/4O6XqPBkiECn6h0ZiFjtYA3kf87Y zBTkbBlUL3mfPDXorvxRt7LWkLFgWg0C2kSj3V6DhcK6t8usA4gmEJbMwptJqLHUC1n2 AxtHSXxRxi+kcpR+8/uvaobHzK1gscAePtGpz/O9+t2UTEDSZ1D0L7pkaEeTLaZ/gxB1 /memMsHn3GYHcUbGWpA4rwEx5Vc23JzeXHbdRI2p8xgwXeMMEZPI5OsJEAH7wafzJYof 6WVz48C33wWY16fiTmeIq0vykllrdhFRUaCwx8pi58hcAzcVVidwOW/1wM6xRyCIbHV8 T2Lg==
MIME-Version: 1.0
Received: by 10.60.1.7 with SMTP id 7mr1686301oei.71.1333100661866; Fri, 30 Mar 2012 02:44:21 -0700 (PDT)
Sender: christopher.morrow@gmail.com
Received: by 10.182.80.137 with HTTP; Fri, 30 Mar 2012 02:44:21 -0700 (PDT)
In-Reply-To: <2C74399F-D505-4FF3-BD0D-57527E87784D@arin.net>
References: <20120328081939.GA19843@slice> <CA796250-4EA9-468D-BB4A-4C1187D2148F@tcb.net> <20120329072236.GA7311@slice> <61C7DEFD-B03F-42B2-B0FC-878E84C32629@ericsson.com> <20120329081625.GA9609@slice> <m262dnzlb0.wl%randy@psg.com> <20120329115714.GA18393@slice> <m21uobzkdn.wl%randy@psg.com> <20120329121824.GB18393@slice> <m2aa2zzelr.wl%randy@psg.com> <2C74399F-D505-4FF3-BD0D-57527E87784D@arin.net>
Date: Fri, 30 Mar 2012 05:44:21 -0400
X-Google-Sender-Auth: _3Yb-HwmMTniQrbGGQgVAw8aUGM
Message-ID: <CAL9jLaYYJ3GMZHiRi5-U=UCHhTD_sPsHRG8yx85=diC4W20JeA@mail.gmail.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Andy Newton <andy@arin.net>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: sidr wg list <sidr@ietf.org>
Subject: Re: [sidr] Injecting idea of "freshness of repository data" into BGP
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: Fri, 30 Mar 2012 09:44:23 -0000

On Fri, Mar 30, 2012 at 4:53 AM, Andy Newton <andy@arin.net> wrote:
>
> Also, the presentation given at SIDR and IEPG indicated the study was done with only one RPKI validator. We have all three running in our lab and have noticed differences in speed over a local network with the same repository. Before declaring the problem a universal issue with rsync, wouldn't a test with the other validators provide helpful data points?
>

is there a way to run all three from many points on the network and
gather useful stats to graph/history/etc? (is this sort of thing a
good idea? watching/storing/analyzing performance over history I mean)

v2.23.0 | Report a Bug | By Email