IETF Logo Mail Archive

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

Randy Bush <randy@psg.com> Thu, 29 March 2012 12:01 UTC

Return-Path: <randy@psg.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 E67EF21F8A26 for <sidr@ietfa.amsl.com>; Thu, 29 Mar 2012 05:01:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.514
X-Spam-Level:
X-Spam-Status: No, score=-2.514 tagged_above=-999 required=5 tests=[AWL=0.085, 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 l0su1YKz-626 for <sidr@ietfa.amsl.com>; Thu, 29 Mar 2012 05:01:26 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 81C7421F8A23 for <sidr@ietf.org>; Thu, 29 Mar 2012 05:01:26 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SDE2f-000NRo-I5; Thu, 29 Mar 2012 12:01:25 +0000
Date: Thu, 29 Mar 2012 14:01:24 +0200
Message-ID: <m21uobzkdn.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Jeffrey Haas <jhaas@pfrc.org>
In-Reply-To: <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> <20120329115714.GA18393@slice>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset="US-ASCII"
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 12:01:27 -0000

>> 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.

ahh.  yes.  if we do a next-gen rpki flooding mechanism, that would be a
good addition.

> 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).

to a bgp hacker everything looks like a nail, eh?  how about a sip
notification?  :)

randy

v2.23.0 | Report a Bug | By Email