Rob Austein wrote:
At Thu, 12 Mar 2009 11:49:53 +1000, Terry Manderson wrote:
I don't remember seeing the a make-before-break issue raised in any
draft, can you point me to a reference?
May not have gotten into any draft, but keeping routing live has
certainly been an assumed requirement for some of us. :)
In mooted transfers of resources from one company on one side of the
world and under RIR 1 to a company on the other side of the world
under RIR 2 I really don't see that a make before break argument
applies. And really - we are talking about cert re-issuance times of
24 hours or less. I'd wager that business process would take longer
than the cert dance.
Think about corporate acquisitions for a moment. EngulfAndDevour,
headquartered in region A, buys MomAndPopISP, in region B.
MomAndPopISP is a going concern whose founders want to retire, grow
tomatoes, and deal with no unit of time shorter than a season.
EngulfAndDevour has paid heavily for good will of MomAndPopISP's
customer base and wants MomAndPopISP's routing to continue to work
during transfer of MomAndPopISP's resources from region B to region A.
Any downtime at all is unacceptable. Hence make-before-break.
Why would this acquisition result in an inter-RIR transfer of the
resource? Wouldn't EngulfAndDevour go to RIR in region B and say "Hi we
acquired MomAndPopISP, please update the company name on the record"
Isn't that how it is done today?
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr
