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

Speaking as regular ol' member.

Too bad you couldn't make the meeting, Danny.

This is in bgpsec path validation and the signalling would go no further than the bgpsec path validation would go.

A method of "signalling" that was mentioned was the validity periods on the router keys so all RPKI info needed would already be available.  Other means were also discussed, no decision made.

--Sandy, regular ol' member

________________________________________
From: sidr-bounces@ietf.org [sidr-bounces@ietf.org] on behalf of Danny McPherson [danny@tcb.net]
Sent: Wednesday, March 28, 2012 9:02 PM
To: sidr wg list
Subject: Re: [sidr] Injecting idea of "freshness of repository data" into BGP

On Mar 28, 2012, at 4:19 AM, Jeffrey Haas wrote:

> Per my mic comment at IETF 83:
> During the San Diego interim session we had discussed potentially signaling
> in BGP the idea that a given AS may have fresher data available in its
> repository.

Shouldn't this problem be solved in the resource certification infrastructure (i.e., RPKI) - signaling RPKI freshness in BGP and distributing to literally millions of routers seems like a REALLY bad idea to me.

-danny

_______________________________________________
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr