On Wed, Aug 29, 2012 at 1:25 AM, Stephen Kent <[email protected]> wrote: > Brian, > > As I mentioned in my rely to Eric, I think this is a topic to be addressed > in an RPKI > operational considerations doc. We have draft-ietf-sidr-origin-ops-19 in > progress now, > so I suggest you discuss this with the author of that doc. Nonetheless, > I'll offer my > views on a few of the topics you mentioned: > > ... >> >> What model for the processes of maintaining sync between INR and RPKI >> should be followed? A high-level finite state machine (FSM) model should be >> an eventual goal, so that implementors have a crystal clear model to follow. >> > I rarely see FSMs in RFCs these days, although I agree that they are > valuable in many contexts. Do > we have an FSM for IRR data use by RPs?
I don't know about FSM _diagram, but the RIPE database (which includes not only IRR data but also authoritative INR data and RPKI data), is fully documented here: http://www.ripe.net/data-tools/support/documentation And in particular the manual, including how a request turns into an "inetnum" (and RPKI object, now) is here: http://www.ripe.net/lir-services/training/material/LIR-Training-Course/LIR-Handbook.pdf The language used in the objects, RPSL, is memorialized here: http://tools.ietf.org/html/rfc2622 (Published in 1999, updated by: http://tools.ietf.org/html/rfc4012) The history of the IRRs, language, and tools, is well documented here: http://tools.ietf.org/html/rfc4277#page-15 And it might be well noted, that the RADB dates back to the Routing Arbiter project, and to its predecessor-in-interest (PRDB) which predates BGP version 4. RIPE-81 -> RIPE-181 -> RPSL. But, as author or co-author of several SIDR docs, I'm presuming you're already familiar with the above? You wouldn't really try implementing a system for (securely) registering internet routing information, without being completely familiar with prior art in the field, would you? Brian
_______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
