Saku Ytti wrote:
It works and has worked 2 decades in real IXP.
If you're referring to Netnod, this started out as a fddi platform with a native max frame size of 4470. Maintaining something which already exists is not nearly as difficult as starting something from scratch and trying to reach a critical mass. In the case of INEX and several other IXPs, it failed because of (in no particular order): - hardware problems - lack of interest among ixp participants outside individual pushers - lack of consensus about what MTU should be chosen - operational problems causing people to "temporarily disable connectivity until someone can take a look at it", i.e. permanently. - additional expense in some situations - the main peering lan worked fine, ie no overriding value proposition - pmtu problems - fragile and troublesome to debug when things went wrong
++ytti, boy who didn't cry wolf
Many IXPs have either looked at or attempted to build jumbo peering lans. You can see how well they worked out by looking at the number of successful deployments. The reason for this tiny number isn't due to lack of effort on the part of the ixp operators. Nick, boy who did the jumbo vlan thing and got the t shirt