On Thu, Aug 30, 2012 at 10:59 AM, Eric Osterweil <[email protected]> wrote: > > On Aug 28, 2012, at 2:55 PM, Stephen Kent wrote: > >> Eric, >> >> Perhaps what you are looking for is some text in an operations doc, >> suggesting what >> an RP can expect, depending on how it elects to interact with the repository >> system, >> maintain its local cache, etc. > > Actually, I was looking for some intuition/guidance for people in a position > to take a systematic look at how to implement the design. I'm not sure which > draft, or which section, etc. Basically, I'm trying to get things worked > out, but I keep having issues w/ ensuring that ingestion of data by a process > at (say) one router has something/anything to do with the ingestion of the > same thing at (say) another router. Consistency models tell me what > properties I can rely on at time t_0 at location r_0 vs time t_1 at r_1, etc. > Right now, I'm having a lot of trouble ensuring that anything agrees with > anything else in the Interwebz and I don't know if I should just let that be > the case, or there is some sort of consistency I need to adhere to... >
right, for the whole system you want to know: 'how long between ROA create and ROA-foo on router' I think what you really want (because across the whole of the realm it's a 'simple' model, where inside islands there is potentially lots more fudgery) is: 1) 'how long from roa-create -> roa-at-all-ASNs' 2) 'what model of timing makes sense for 'once a ROA is at a remote ASN, how long before that data is available on 1 routing-device, then all routing-devices in that realm' 3) should this set of numbers apply to ALL objects in the RPKI equally? or should some object types have different timing requirements? -chris (using ROA as the unit, you could use CRL update, EE-cert, etc... 'one item in the RPKI') > Eric > _______________________________________________ > sidr mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/sidr _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
