NY Times on IPv4 depletion
http://www.nytimes.com/2011/02/15/technology/15internet.html “The problem was, the experiment never ended,” added Mr. Cerf, who is the
chairman of the Internet Corporation for Assigned Names and Numbers<http://topics.nytimes.com/top/reference/timestopics/organizations/i/internet_corp_for_assigned_names_and_numbers/index.html?inline=nyt-org>, or Icann <http://www.icann.org/>, a nonprofit corporation that coordinates the Internet naming system.
<http://www.nytimes.com/2011/02/15/technology/15internet.html>Surprising that that got past the NYT fact-checkers.. can see where they got it http://www.icann.org/en/biog/cerf.htm while they should have looked at http://www.icann.org/en/general/board.html or even http://en.wikipedia.org/wiki/Vint_Cerf let's see how long it takes to fix it. j -- --------------------------------------------------------------- Joly MacFie 218 565 9365 Skype:punkcast WWWhatsup NYC - http://wwwhatsup.com http://pinstand.com - http://punkcast.com VP (Admin) - ISOC-NY - http://isoc-ny.org ---------------------------------------------------------------
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 ....
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). So you have to check each and every domain in the source to find which ones are broken. Jack
In message <4D597216.1030400@brightok.net>, 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.
Jack -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org
On Feb 14, 2011 1:52 PM, "Mark Andrews" <marka@isc.org> wrote:
In message <4D597216.1030400@brightok.net>, 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 Cb
Jack -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org
In message <AANLkTikOS1H-2APnQqWqfsj7N-L=kuDYGNBpYWox-DiW@mail.gmail.com>, Came ron Byrne writes:
--00163630f77d957e25049c454dc0 Content-Type: text/plain; charset=ISO-8859-1
On Feb 14, 2011 1:52 PM, "Mark Andrews" <marka@isc.org> wrote:
In message <4D597216.1030400@brightok.net>, 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: marka@isc.org
Dear all, Actually I fully agree with Cameron.
From an operator point of view, it is quite difficult to rely on some specific functions in mobile, besides an IPv6 stack - that is already difficult to get if we have a look on IPv6-ready devices available on market. I do not know how we can mandate some DS-lite functions in devices, for example, as far as there is no document where 3GPP devices are "specified". So, it is not possible to set up some IPv6 introduction strategy based on some solutions integrated in devices. In mobile context, I think it is more adapted to encourage IPv6 native communications and to rely on NAT64 for IPv4-only appls access even if we all know that such translation solution has some drawbacks.
David
-----Message d'origine----- De : Mark Andrews [mailto:marka@isc.org] Envoyé : lundi 14 février 2011 23:53 À : Cameron Byrne Cc : North American Network Operators Group Objet : Re: NY Times on IPv4 depletion
--00163630f77d957e25049c454dc0 Content-Type: text/plain; charset=ISO-8859-1
On Feb 14, 2011 1:52 PM, "Mark Andrews" <marka@isc.org> wrote:
In message <4D597216.1030400@brightok.net>, 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
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
SOA record.
So you have to check each and every domain in the
In message <AANLkTikOS1H-2APnQqWqfsj7N-L=kuDYGNBpYWox-DiW@mail.gmail.com> , Came ron Byrne writes: literal for the the wrong 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: marka@isc.org
********************************* This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. Messages are susceptible to alteration. France Telecom Group shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. ********************************
+1 ========================================= John Jason Brzozowski Comcast Cable e) mailto:john_brzozowski@cable.comcast.com o) 609-377-6594 m) 484-962-0060 w) http://www.comcast6.net ========================================= On 2/14/11 5:09 PM, "Cameron Byrne" <cb.list6@gmail.com> wrote:
On Feb 14, 2011 1:52 PM, "Mark Andrews" <marka@isc.org> wrote:
In message <4D597216.1030400@brightok.net>, 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
Cb
Jack -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org
participants (6)
-
Brzozowski, John -
Cameron Byrne -
david.binet＠orange-ftgroup.com -
Jack Bates -
Joly MacFie -
Mark Andrews