In message <[email protected]>, Came ron Byrne writes: > --00163630f77d957e25049c454dc0 > Content-Type: text/plain; charset=ISO-8859-1 > > On Feb 14, 2011 1:52 PM, "Mark Andrews" <[email protected]> wrote: > > > > > > In message <[email protected]>, Jack Bates writes: > > > > > > > > > On 2/14/2011 12:12 PM, Cameron Byrne wrote: > > > > Too bad the article pushes my mobile device to their mobile site > > > > mobile.nytimes.com and that references an ipv4 literal for the picture > to > > > > load .... so not only is nytimes not ipv6 it is also broken for ipv6 > only > > > > users behind nat64 .... > > > > > > That's almost as bad as the hundreds of subdomains used in webpages > > > which sometimes hit broken load balancers (reporting nxdomain for AAAA). > > > > Very few do that anymore. What they do however is return the wrong SOA > > record. > > > > > So you have to check each and every domain in the source to find which > > > ones are broken. > > > > Which one really shouldn't have to do. Add DS-Lite support to the > > phone and have the carriers advertise that they support DS-Lite and > > the IPv4 literal problem goes away. > > > > This has been done in a phone already so it is possible to do. > > > > Ds-lite has been dismissed by 3gpp. Nytimes needs to start using fqdns and > ideally ipv6. Until then, it's their content that's being mangled. It is > not reasonable for network operators to engineer for amateur web programming > mistakes
It still doesn't stop handest manufatures adding DS-Lite support and operators responding to the DHCP option so the handsets can find the AFTR box. NAT64/DNS64 may be the only operator side only solution but it has lots of limitation to it and it can't be made to work as well has DS-Lite even once the handset know the DNS64 prefix and BIH is added to translate IPv4 to IPv6 inside the handset using the DNS64 prefix. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [email protected]
