Tom,

Le 30/09/2017 à 18:42, Tom Herbert a écrit :
That said, I agree with you that that the technical basis is to allow encapsulate versions of IP in a same packet header.

This does not justify the statements that this protocol can be developed and deployed in a short time by technology companies. Deploying anything at Internet scale is hard,

I agree putting anything at Internet scale is hard.  Internet is a large
system.

People who try the migration from IPv4 to IPv6 are not dumb.  They try
very hard.  Yet, it takes decades.  That is explained by the fact that
Internet is already very large.  It is not as simple as the 1980
migration from NCP to TCP protocol, which happened in months.  The
Internet was much smaller at that time.

There is absolutely no expectation that some new IP-v-something can be
any more successful than what IPv6 already achieved at Internet scale.
Such expectation can be qualified as foolish.

[...]
End hosts need to change several ways, NIC HW needs to change to support protocol specific features, routers and switches need to be able to deal with new version [...]

I agree.

But I would like to understand whether the proposal (no name) may work
without modifying all the intermediary routers.  If all intermediary
routers must be modified to support it, then (proposal) can not work.

Also, some of the most widespread deployments of IPv6 do _not_ modify
the intermediary routers: they are tunnelled in IPv4.

So maybe this (proposal) could also be a tunnelled overlay network.

But we'd need running code to see it :-)

[...]
IETF is "rough consensus and running code". It's incumbent on the advocates of a proposed protocol to push for both of these. There's no concept that protocol experts bring their protocols to IETF and then throw over the wall to the protocol developers who happily go off and implement the spec. If you don't have the skills for implementation, then please find someone else to work with who can do
it for you.

I fully agree.

Alex


Tom

Alex


_______________________________________________ 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

Reply via email to