It looks to me as if these are developer and interoperability issues that are
not going to be addressed of their own accord through regular IETF meetings.
I think that the only way we could expect progress here would be to have a
series of interop events that involve representatives from all the interested
parties - ISPs, O/S, network infrastructure providers, core DNS.
And they are going to find a large number of such missing pieces that need to
be fed into the standards process.
In this type of situation I think that we have got to expect the standards
process to be descriptive rather than normative. Rather than having a group of
folk get together to propose what should work we have to have the interop folk
tell us what did work.
Some parts of this can take part in the regular IETF process but it really is
not the type of project that I think is going to be effectively completed
unless there is some fairly radical change in the approach.
Transition from IPv4 to IPv6 has to be effortless for the end user. We can
adopt a HDTV type approach where users are expected to deploy some sort of $50
'converter' box. What we cannot do is to propose an architecture that requires
end-users to think about the change.
My home network is IPv4. I have many devices that are not IPv6 aware and have
zero intention of changing them. The network is behind a NAT because I don't
see a business case to pay $10 per network device per month for unique IP
addresses. That would be $120 a month for me - if Comcast actually supported it
as an option which they do not, they allow up to 4 IPv4 addresses per
residential connection.
The core problem here is that the current Internet 'architecture' requires
applications to know rather too much about the internal workings of the network
that they are connected to. Everyone now accepts that IPv4 address space is
going to be quickly exhausted. What fewer people currently understand is that
16 bit port numbers are no longer a scalable means of protocol description. And
16 bit DNS RRs are no better in that respect either.
________________________________
From: ietf-bounces(_at_)ietf(_dot_)org on behalf of Harald Alvestrand
Sent: Wed 11/12/2008 5:06 AM
To: Pekka Savola
Cc: tytso(_at_)mit(_dot_)edu; ietf(_at_)ietf(_dot_)org
Subject: Re: IPv6 traffic stats
Pekka Savola wrote:
On Tue, 11 Nov 2008, Harald Alvestrand wrote:
The correct number from the presentation is 0.238% - only Russia,
Ukraine and France have more than 0.5% IPv6.
Presentation available from
http://rosie.ripe.net/presentations-detail/Thursday/Plenary%2014:00/index.html.
Depends on what you're looking for, but if you are interested in the
amount of users that have any kind of IPv6 connectivity, this
undercounts severely because address selection rules on recent OSs
typically select IPv4 if their connectivity is 6to4 or Teredo.
Pekka,
can you identify the OSes that prefer IPv4 when on 6to4, and pointers to
docs?
Steinar (the guy who did the Google experiment) has tried to dig through
the documentation on both Vista and Linux, and has drawn a blank (Vista
with Teredo doesn't even look up the AAAA record if it has IPv4
connectivity, according to the documentation, so it seems that it will
not use IPv6 to IPv6-only hosts; it will never find the address.)
Harald
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf