Le 01/09/2017 à 22:54, Lee Howard a écrit :
[...]
In summary:
This might be possible, with enough work, but I can’t see how it will
overtake the momentum of IPv6 deployment and existing transition
mechanisms. Here’s a possible timeline, being very generous to IPv10:
IPv6 IPv10
2018 50% of US WG discussion
2019 50% of world IETF nearing consensus (into 2020)
2021 75% of world first vendor code ships
2026 99% of world Old hardware that couldn’t support new code is
cyclin out
I am very happy to see the left column. Because it shows IPv6 adoption
is happening on a large scale. This is encouraging.
I would like, however, to express a risk, and at the same time, an
opportunity of further comparison.
The points of view are very different from country to country: 50%
penetration in US; I think Egypt is something like 0.2% penetration. 50
is significantly bigger than 0.2. This can be interpreted as too
overwhelming.
Listing US vs World may also be a risk of interpretation - sounds as if
US is not part of the world.
However, a common denominator could be: IPv6 is present (or not) in
country x vs country y.
Then one can discuss why, in a certain Country, the IPv6 presence is
posing problems of interconnectivity to IPv4 Internet.
Also, I agree it's hard to talk US, world, or even Country, in an
interconnected system like Internet.
My two cents worth.
Alex
You can prove me wrong:
1. Write an implementation. Show how an IPv4+IPv10 host can communicate
with an IPv6+IPv10 host over a dual-stack (or triple-stack) network. If
the router implementation is an open-source router, that’s fine at this
stage.
2. Have someone else write an implementation that interoperates with
yours. That will demonstrate that the document is detailed enough and
clear enough.
3. Do some performance testing. Show that it is easier to update to IPv10
than to dual-stack (including IPv6+transition), and that there is no
performance penalty for doing so.
4. Convince a router vendor to implement in test code, and run load
testing, to demonstrate that it works at Internet scale.
If you can get through Step 3, you may be able to get to Step 4, and if
you can do Step 4 you have a good shot at convincing other vendors to
implement. If you can get through at least Step 3, you’ll be in good shape
in looking for IETF consensus, because you’ll have running code.
While I am skeptical of this specific proposal, I wish you luck and hope
you will engage with other work in the IETF.
Lee
_______________________________________________
Int-area mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/int-area
_______________________________________________
Int-area mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/int-area
