<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sat, Nov 8, 2014 at 11:48 PM, Jeroen Massar <span dir="ltr"><<a href="mailto:jeroen@massar.ch" target="_blank">jeroen@massar.ch</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">>> The issue with IPv6 access to Google should now be resolved. Please let<br>
>> us know if you're still having problems.<br>
<br>
</span>The fun question of course is: what/why/how the heck happened?<br></blockquote><div><br></div><div>Another fun question is why folks are relying on PMTUD instead of adjusting their MTU settings (e.g., via RAs). But relying on PMTUD still imposes a 1-RTT penalty on every TCP connection to an IPv6 address you haven't talked to in the last few minutes. Why would you do that to your connection?</div><div><br></div><div>As to what happened: what happened here is that some Google servers temporarily stopped doing MSS clamping. That was an outage, and AIUI it has since been fixed. (Some parts of) Google infrastructure do not do PMTUD for the latency reasons above and for reasons similar to those listed in <a href="https://tools.ietf.org/html/draft-v6ops-jaeggli-pmtud-ecmp-problem-00">https://tools.ietf.org/html/draft-v6ops-jaeggli-pmtud-ecmp-problem-00</a> .</div></div></div></div>