IETF Logo Mail Archive

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

Jeffrey Haas <jhaas@pfrc.org> Thu, 29 March 2012 11:57 UTC

Return-Path: <jhaas@slice.pfrc.org>
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 63ED421F8604 for <sidr@ietfa.amsl.com>; Thu, 29 Mar 2012 04:57:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.17
X-Spam-Level:
X-Spam-Status: No, score=-102.17 tagged_above=-999 required=5 tests=[AWL=0.095, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, 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 zyDCpwUTvDsj for <sidr@ietfa.amsl.com>; Thu, 29 Mar 2012 04:57:15 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 78F6021F85CE for <sidr@ietf.org>; Thu, 29 Mar 2012 04:57:15 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id CC78717042B; Thu, 29 Mar 2012 07:57:14 -0400 (EDT)
Date: Thu, 29 Mar 2012 07:57:14 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Randy Bush <randy@psg.com>
Message-ID: <20120329115714.GA18393@slice>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <m262dnzlb0.wl%randy@psg.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
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: Thu, 29 Mar 2012 11:57:16 -0000

Randy,

On Thu, Mar 29, 2012 at 01:41:23PM +0200, Randy Bush wrote:
> > Just to be clear, this is not a route freshness mechanism I am
> > recommending.  What I am recommending is a signal that a repository
> > has newer data that may be needed for validation.
> 
> Serial Notify, sec 5.2 of draft-ietf-sidr-rpki-rtr-26.txt, provides such
> a mechanism

Not what I'm talking about.

What notifies a cache that it needs to fetch new objects from a RPKI
repository?  As best I understood, it's largely done on cron jobs now.

I could readily see a BGP signaled "This AS has a manifest with a newer
serial number" being passed back to rpki-rtr so that it could kick off
rsync (or whatever).

-- Jeff

v2.23.0 | Report a Bug | By Email