[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RIPE our of IPv4
- Subject: RIPE our of IPv4
- From: lists.nanog at monmotha.net (Brandon Martin)
- Date: Sat, 30 Nov 2019 21:01:36 -0500
- In-reply-to: <94402.1575165336@turing-police>
- References: <CAPcE_LfoQ3pD5_+7EBsDkOiGq=1McZN90dOyTUwmO++RVX3J+Q@mail.gmail.com> <[email protected]> <CAPcE_Ld4LzoZg6d3xi=ubP3yJ4S5WFsZswYye8tD5BDbrZCZvw@mail.gmail.com> <94402.1575165336@turing-police>
On 11/30/19 8:55 PM, Valdis KlÄ?tnieks wrote:
>> User apps prefer IPv6, Netflix stops, users complain
> And fallback to IPv4 fails to happen, why, exactly?
Inability to signal application-level failure on IPv6 and that fallback to IPv4 would succeed.
Netflix definitely exhibits this. I've also noticed that a lot of Cloudflare-hosted apps/sites block AS6939 outright which mostly only affects IPv6 as they don't actually originate much end-user-facing IPv4 space. The result is an HTTP/403 which most browsers do not interpret as a response that could be remedied by "happy eyeballs" type behavior. Whether banning an entire ASN like that in precisely a situation where this kind of thing is likely to occur is a good practice or not is left as an exercise to the reader.
--
Brandon Martin