At Tue, 6 Sep 2016 22:48:07 -0400, Christopher Morrow wrote: > > (note, I do not care for this message about politics)
Understood, with the caveat that since it's the politics which are pushing the wrong technical solution here, any technical discussion will loop back to politics as soon as one asks "why?" > we're here because, I think, from the top down to the RIR there isn't a > hierarchy being created, right? the RIR folk are saying: "Ok, you all want > this thing, but upstairs hasn't created the root, so we're going to do the > best we can with making a root each that allows us to xfer between RIRs. > This is how it's being done, so you have some docs about the mechanics > involved and can build/guide from there" > > is that not the case? (again, I don't care about the politics) I'm ignoring "upstairs", because that is also political. Stripped of the politics, we're having this conversation because the RIRs are proposing to operate five roots instead of one, with each root allowed to claim ownership over the known universe, because actually coordinating with each other is Too Hard. Or maybe it's more than five, some of the RIRs have extra roots just for fun, but let's take it as given for now that they'll collapse back down to five. The problem with multiple global RPKI roots, as KC Claffy put it rather neatly many years ago, is that it pushes responsibility for fixing RIR coordination mistakes (which the RIRs apparently believe are a serious issue, as evidenced by the draft under discussion) onto the relying parties rather than forcing the RIRs to fix those issues on the CA side. This is technically broken. Generating a single RPKI root is not hard. It can be done by a cron job. I ran one for years, for experimental purposes, entirely from data already available to the RIRs. The only real issue is which database to believe when they disagree -- which is exactly the problem the RIRs are trying to push onto the RPs with this document. Which brings us back to bad technical decisions and political reasons. Sorry. _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
