On May 31, 2014, at 11:03 AM, Gert Doering <[email protected]> wrote: > Hi, > > On Sat, May 31, 2014 at 06:33:45PM +0200, Mikael Abrahamsson wrote: >> On Sat, 31 May 2014, Gert Doering wrote: >> >>> So I'd keep the list of supported protocols as small as possible - and >>> stick to IP protocols. ISIS is great for ISP environments, but does not >>> nicely adapt to a unix environment where the kernel has no idea about >>> ISO/OSI protocols and you have to do everything via raw sockets. Which >>> would be a fairly typical environment for a CPE router. >> >> This is actually a feature, the fact that ISIS doesn't require IPv6 to be >> up and running before it can get itself started and you know the topology >> of the home. > > Uh, what? So the benefit of ISIS (over ISO/OSI transport) in the home would > be "you can have IPv4 in your homenet, without having IPv6"? I truly can't > see a reason why this would be useful in the time frame when this would be > ready - and it's also out of scope of what the homenet architecture concerns > itself with. Which, as far as I understand, is "make IPv6 work right, and > do not damage IPv4", while excluding IPv4-only scenarios.
Dear Gert, I could be wrong, but I don't think that was the point. There are also layer 2 protocols to consider. Expecting everything to be handled at IP transport layer 3 will confront extremely difficult security issues. Testing using a modern printer/scanner illustrated a major problem when devices were not restricted to link-local. Something like RBridge supporting PPP would provide a much safer foundation upon which to build. All networks must begin with layer 2 starting points. Selective routing between Rbridges would allow an ability to share data between HDCP enforced multi-media display devices using link-local addresses. There will be video cameras, baby monitors, HVAC/SCADA controls, printers and scanners offering media stick access, etc. These devices were never intended to directly interface with the Internet. These devices MUST NOT be assigned routable IPv4 or IPv6 addresses. Using mDNS proxy into DNS would be setting the stage for major security disasters. Regards, Douglas Otis _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
