[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: randy at psg.com (Randy Bush)
Date: Thu, 14 Nov 2019 09:53:18 -0800
In-reply-to: <CA+-tSzxY9CTLY7N5A+z=n8Mc_tU9QKOCeU1nhjJVdsG9Efj0OA@mail.gmail.com>
References: <[email protected]> <[email protected]> <CAHw9_i+uOvyv7yHu4DkLnYncTE6ttQQBzyiZOhVGS1299cMuiQ@mail.gmail.com> <CA+-tSzxY9CTLY7N5A+z=n8Mc_tU9QKOCeU1nhjJVdsG9Efj0OA@mail.gmail.com>

> 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.

randy

Follow-Ups:
- TCP and anycast (was Re: ECN)
  - From: morrowc.lists at gmail.com (Christopher Morrow)

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)

Prev by Date: Disney+ Geolocation issues
Next by Date: someone, probably someone who scraped your group, sent me a virus as a .doc file
Previous by thread: TCP and anycast (was Re: ECN)
Next by thread: TCP and anycast (was Re: ECN)
Index(es):
- Date
- Thread