Le 2014-04-16 04:44, Lorenzo Colitti a écrit : > I'm sorry, but I have no sympathy for your protestations about > DHCPv4 clients in embedded applications. If it's an RPi, you can > run a full-featured DHCPv4/DHCPv6 implementation that works, so > there's no excuse for running one that doesn't. > > > Ted, I think you'll have to accept that Philip's assessment of how much > work has to be done on his platform is accurate, since he's the one > writing that code.
On his platform, sure. On all the platforms I know, it would be trivial. > We've had this discussion many times on many different drafts, and every > time the conclusions from the implementers (and of course, not from the > standards writers) was that tying together the state machines from > different protocol provisioning mechanisms was brittle and a lot of work. They are already tied together on many platforms. NetworkManager, systemd, Android, Mac, Windows, etc. /etc/rc.d/dhclient is dead. And that's a good thing. Simon -- DTN made easy, lean, and smart --> http://postellation.viagenie.ca NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca STUN/TURN server --> http://numb.viagenie.ca _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
