[v6ops] draft-pauly-v6ops-happy-eyeballs-update-01

[Ca By <[e-mail]>]

Just a comment following up on Jordi's Mic comment

Jordi said there was an issue with HE hiding IPv6 issues.

David's response was something along the lines of "deploy ipv6-only".  I
did not really understand this.

When folks deploy ipv6-only, they find they are all alone with a broken
ipv6 scenarios that work on all their competitors IPv4-only networks and HE
dual-stack networks.

Also, friendly reminder that Dan Wing catalogs a subset of the websites
that fail on ipv6-only http://www.employees.org/~dwing/aaaa-stats/

And, my customers still complain about www.fra.dot.gov ... this works for
everyone but me... because of HE...and I am already on IPv6-only ... and
nobody will fix it.  This issues has been known by the USG DOT for over 3
months, noted to NANOG, nobody cares to fix it.

So, perhaps there is room in the I-D for including NAT64 synthesized
address candidate set.  Meaning the HE algo on an IPv6-only host would
include the set of available native IPv6 answers as well as a 500ms timer
for attempting an A query with using whatever mechanism is available to the
host for relaying IPv4 packets across an IPv6 only network (RFC6877, Bump
in API, ...)

Without this, IPv6-only networks are at a painful disadvantage since IPv6
must be perfect while every other scenario has HE to mask brokenness.