[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

TCP and anycast (was Re: ECN)

Subject: TCP and anycast (was Re: ECN)
From: morrowc.lists at gmail.com (Christopher Morrow)
Date: Fri, 15 Nov 2019 09:31:49 +0800
In-reply-to: <[email protected]>
References: <[email protected]> <[email protected]> <CAHw9_i+uOvyv7yHu4DkLnYncTE6ttQQBzyiZOhVGS1299cMuiQ@mail.gmail.com> <CA+-tSzxY9CTLY7N5A+z=n8Mc_tU9QKOCeU1nhjJVdsG9Efj0OA@mail.gmail.com> <[email protected]>

On Fri, Nov 15, 2019 at 1:54 AM Randy Bush <randy at psg.com> wrote:
>
> > RFC 7094 (https://tools.ietf.org/html/rfc7094) describes the pitfalls
> > & risks of using TCP with an anycast address.
>
> and two decades of operational experience are that prudent deployments
> just work.

I agree with Bill/Randy here... this does just work if you understand
your local topology and manage change properly.

Follow-Ups:
- TCP and anycast (was Re: ECN)
  - From: randy at psg.com (Randy Bush)

References:
- ECN
  - From: toke at toke.dk (Toke Høiland-Jørgensen)
- ECN
  - From: nanog at as397444.net (Matt Corallo)
- ECN
  - From: warren at kumari.net (Warren Kumari)
- TCP and anycast (was Re: ECN)
  - From: anoop at alumni.duke.edu (Anoop Ghanwani)
- TCP and anycast (was Re: ECN)
  - From: randy at psg.com (Randy Bush)

Prev by Date: Puerto Rico IX (operational)
Next by Date: TCP and anycast (was Re: ECN)
Previous by thread: TCP and anycast (was Re: ECN)
Next by thread: TCP and anycast (was Re: ECN)
Index(es):
- Date
- Thread