News for hackers. Stuff that matters.
Re:IPv6 privacy addresses crashed the MIT CSAIL network by MichaelGG on Saturday September 06, 2014 @03:31PM (#8279236)
What's the reasoning for dropping ARP? It seemed like a simple architecture. The post seems to indicate IPv6 requires a ton more hardware resources. And if Juniper doesn't have a basic feature like MLD snooping after all this time, uh? Shouldn't practically designing a high-volume switch be part of creating such a fundamental protocol? (I know designing 2 elegant implementations of other protocols would have fixed a ton of things in nasty protocols like HTTP - dumbass things like line folding and comments-in-headers.)

Is this a case of idiocy seeping through the IETF because they can? It's pretty easy to write something down on paper if you don't have to implement engineering and product management on the result. Or because you're out of touch with reality, like the source routing feature which was kept in IPv6 despite it only ever being a problem in IPv4? Or is this a case of the protocol being superior and vendors just being very lazy?

Re:IPv6 privacy addresses crashed the MIT CSAIL network by dfox on Saturday September 06, 2014 @08:51PM (#8280003)
ICMPv6 ND and ARP are essentially same protocol. Main difference is that ARP runs directly over some L2 protocol, while ICMPv6 ND uses IPv6 multicast as underlying protocol regardless of underlying L2 transport. Practical motivation to do neighbor discovery using multicast instead of broadcast is to limit overall volume of ARP/ND packets that have to be processed by host's L3 stack (and enable reasonable intelligent switch to just drop them), when this mechanism was designed, excessive ARP traffic was real problem for many kinds of ethernet or ethernet-derived (eg. DOCSIS) access networks.
Re:IPv6 privacy addresses crashed the MIT CSAIL network by akira2501 on Saturday September 06, 2014 @03:50PM (#8279281)
It seems like they really wanted to push multicast as a "first-class" mode of the protocol, and by weaving it into the core of IPv6 they've forced everyone to have a somewhat exercised implementation of it in their stack.
Re:IPv6 privacy addresses crashed the MIT CSAIL network by cesarb on Saturday September 06, 2014 @07:32PM (#8279863)
I believe their thinking process was more like:

-> Broadcast is just a special case of multicast, where every host listens to an "all hosts" multicast group;

-> Since this is a new protocol, there is no need to keep broadcast; just mandate that every host join the "all hosts" multicast group (notice that the numerically first two IPv6 multicast groups are "all hosts" and "all routers", implying they were the first ones thought of);

-> Since we will always have multicast, instead of flooding ARP-like requests to everyone, let's create many "buckets" so each ARP-like request will go only to the hosts to which it's relevant, saving traffic and processing power.

IPv6 is old. It's possible that when it was designed, global multicast was just around the corner. Designing the protocol to use multicast would have seemed natural back then.

Re:IPv6 privacy addresses crashed the MIT CSAIL network by ChuckMcM on Saturday September 06, 2014 @03:53PM (#8279287)
This was my take on it as well. Multicast was a very under deployed system, one way to fix that is to make it mandatory :-)
Re:IPv6 privacy addresses crashed the MIT CSAIL network by MichaelGG on Saturday September 06, 2014 @04:45PM (#8279413)
So pushing something no one uses, and has significantly narrow uses, and still isn't deployed publicly, into the core... How is that anything but self-serving protocol designers? How do they get away with that?
Re:IPv6 privacy addresses crashed the MIT CSAIL network by teach on Saturday September 06, 2014 @05:41PM (#8279577)
Multicast has much more than "significantly narrow uses". When we were studying IPv6 in my network protocols course 20 years ago(!) I remember thinking how useful that would be if widely deployed.
Re:IPv6 privacy addresses crashed the MIT CSAIL network by FeepingCreature on Saturday September 06, 2014 @07:23PM (#8279837)
I'm a private customer, and I use IPv4 Multicast. My ISP uses it to distribute IPTV streams.

Don't generalize from "I don't know anybody who uses" to "nobody uses".

Re:IPv6 privacy addresses crashed the MIT CSAIL network by jewel on Saturday September 06, 2014 @10:12PM (#8280122)
A good portion of the bandwidth being used on the Internet could be done over multicast if it were widely supported.

For example, popular content on Hulu could be multicast. You'd download the beginning of the video over HTTP but simultaneously tune into the multicast that started the most recently. Once the two streams meet you drop the HTTP connection. If widely deployed this would reduce costs for both Hulu and ISPs, and for places where multicast doesn't work it can fall back to HTTP.

Re:IPv6 privacy addresses crashed the MIT CSAIL network by xorcist on Sunday September 07, 2014 @04:07AM (#8280578)
It decreases network load (when implemented correctly). Broadcast floods used to be a real problem.