Jeroen Massar wrote:
That indeed matches most of the corporate world quite well. That they
are heavily misinformed does not make it the correct answer though.
Either you are correct and they are all wrong, or they have a
perspective that you dont or wont see.
Either way I dont see them changing their mind anytime soon.
So how about we both accept that they exist and start designing the
network to welcome rather than ostracize them, unless that is your intent.
And the good thing is that if you can support jumbo frames, just turn it
on and let pMTU do it's work. Happy 9000's ;)
pMTU has been broken in IPv4 since the early days.
It is still broken. It is also broken in IPv6. It will likely still be
broken for the forseeable future. This is
a) a problem that should not be ignored
b) a failure in imagination when designing the protocol
c) a missed opportunity to correct a systemic issue with IPv4
Or better said: mis-configuring systems break things.
Why do switches auto-mdix these days?
Because insisting that things will work properly if you just configure
them correctly turns out to be inferior to designing a system that
requires less configuration to achieve the same goal.
Automate.
This whole thread is all about how IPv6 has not improved any of the
issues that are well known with IPv4 and in many cases makes them worse.
You cannot unteach stupid people to do stupid things.
Protocol changes will not suddenly make people understand that what they
want to do is wrong and breaks said protocol.
Greets,
Jeroen
You also cannot teach protocol people that there is protocol and then
there is reality.
Relying on ICMP exception messages was always wrong for normal network
operation.
Best,
Joe
