On 12/03/2009, at 3:23 PM, Terry Manderson wrote:
As stated, I would much prefer that the structure be as simple as
possible, and the co-ordination function be improved through some
inter-RIR brokerage/exhange/transfer protocol. I wonder (just
thinking aloud) if there would be dire consequences of a 24hr
overlap in information. Clearly a question about RP decision time if
the ROAs differ.. but other than that? (maybe a @beers discussion)
Could the following option be valid to maintain structural simplicity,
thinking that certificates have both a space function, and a time
function?
(and noting that this is not a ERX transfer)
EngulfAndDevour acquires MomAndPopISP.
EngulfAndDevour advises both RIRs of the purchase
EngulfAndDevour advises that at 0100hrs UTC on a future date all
resources (ROAs et al) are transferred to RIR 1.
RIR 1 advises RIR 2 to reissue all of MomAndPopISP resources (ROAs et
al) with a validity period that ends at 0059:59hrs UTC on that date
RIR 1 issues the old MomAndPopISP resources for EngulfAndDevour with a
validity period that begins at 0100hrs UTC on that future date.
Through all this, routing will still work, RPs don't have a confusing
decision to make (validity time takes care of that), no TAs are making
conflicting statements due to the time principle, and the structure of
the RPKI is simple such that RIRs aren't maintaining CAs of other
RIRs, further (and based on a brief email discussion with on RIR
policy staff) the resources transferred to an RIR under would stay at
that rir, until another transfer event (ERX included). But as randy
says, RIR policy are subject to change - best to design this to avoid
codifying that in a standard where possible.
Terry
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr
