North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical Re: Multi-6 [WAS: OT - Vint Cerf joins Google]
On Sep 13, 2005, at 3:19 PM, Iljitsch van Beijnum wrote: So, move to IPv6 and watch your initial connect times according to keynote et al. increase?On 13-sep-2005, at 0:22, Igor Gashinsky wrote::: I must be missing something, but there's a good chance that the requester isThis aspect isn't nailed down yet, but basically there are two options: depend on the application do try all addresses (which apps should do anyway, but I for one wouldn't want to wait for all these timeouts), or have the shim detect that the first address doesn't work and repair the failure. This adds additional complexity, though, and there is still a timeout, although it isn't a full TCP SYN timeout. Mmmm, DNS load balancing. As a shareholder in my current employer, I am happy to see that market increase. As a network engineer, I keep getting the feeling I'm missing out on some great drugs.Or, on top of that, how traffic engineering can be performed with shim6..For outgoing traffic there is no difference with the current situation (as long as there are nog ingress filtering issues). For incoming traffic, it basically starts with DNS load balancing, and the shim itself will have priority mechanisms to choose between different address pairs but this will generally not come into play because the idea is that the shim doesn't do anything unless there is an outage. So where were you the past years in multi6 and months in shim6? Please be part of the solution and not part of the problem. (That goes for John Payne and Daniel Senie too.)I was in denial that multihoming would get this broken. I've joined the mailing list... I'll note that the mailing list archive is not linked anywhere useful, so to save others the guesswork: <http://psg.com/lists/shim6/>
|