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

Danny McPherson <danny@tcb.net> Fri, 30 March 2012 15:27 UTC

Return-Path: <danny@tcb.net>
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 C209F21F84D2 for <sidr@ietfa.amsl.com>; Fri, 30 Mar 2012 08:27:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 qHb4dMkwyII4 for <sidr@ietfa.amsl.com>; Fri, 30 Mar 2012 08:27:12 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by ietfa.amsl.com (Postfix) with ESMTP id E97A821F84D1 for <sidr@ietf.org>; Fri, 30 Mar 2012 08:27:11 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0) id 8F7A4268063; Fri, 30 Mar 2012 09:27:11 -0600 (MDT)
Received: from [192.168.1.7] (134.sub-166-248-35.myvzw.com [166.248.35.134]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; for sidr@ietf.org; Fri, 30 Mar 2012 09:27:11 -0600 (MDT) (envelope-from danny@tcb.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=166.248.35.134; client-port=10720; syn-fingerprint=65535:44:1:64:M1460,N,W3,N,N,T,S MacOS 10.4.8; data-bytes=0
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1257)
From: Danny McPherson <danny@tcb.net>
In-Reply-To: <20120329081625.GA9609@slice>
Date: Fri, 30 Mar 2012 11:26:47 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <7B939BBC-D24A-4A18-BF29-A9515A45C178@tcb.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>
To: sidr wg list <sidr@ietf.org>
X-Mailer: Apple Mail (2.1257)
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 15:27:12 -0000

On Mar 29, 2012, at 4:16 AM, Jeffrey Haas 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.
> 
> Given such a mechanism, we may be able to reduce the work upon the
> repository mirroring system (distributed or not) by not having to regularly
> poll for new objects frequently unless the repository indicates there is new
> data present.

And again, why would this not be done in the repository system (RPKI)?  It does NOT belong in the routing system.

-danny