North American Network Operators Group|
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical
Re: IP failover/migration question.
RB> Date: Sun, 11 Jun 2006 17:02:14 -1000 RB> From: Randy Bush RB> persistent tcp connections from clients would not fare well unless RB> you actually did the hacks to migrate the sessions, i.e. tcp serial RB> numbers and all the rest of the tcp state. hard to do. Actually, the TCP goo isn't too terribly difficult [when one has kernel source]. What's tricky is (1) handling splits, and (2) ensuring that the app is consistent and deterministic. One transit provider handling multiple locations shouldn't present a problem. Of course many things that should be, aren't. == below respsonses are general, not re Randy's post == Note also that redundancy/propagation is at odds with RTT latency. The proof of this is left as an exercise for the reader. Finally, an internal network between locations is a good thing. (Hint: compare internal convergence times with global ones.) Eddy -- Everquick Internet - http://www.everquick.net/ A division of Brotsman & Dreger, Inc. - http://www.brotsman.com/ Bandwidth, consulting, e-commerce, hosting, and network building Phone: +1 785 865 5885 Lawrence and [inter]national Phone: +1 316 794 8922 Wichita ________________________________________________________________________ DO NOT send mail to the following addresses: [email protected] -*- [email protected] -*- [email protected] Sending mail to spambait addresses is a great way to get blocked. Ditto for broken OOO autoresponders and foolish AV software backscatter.