In your letter dated Tue, 15 Apr 2014 13:20:19 -0500 you wrote: >Right, but you haven't given a technical argument to support that. >You've just said that it's convenient in a particular existing >implementation, which is not in wide use, and which is already >undergoing changes that will coincidentally make addressing this less >inconvenient. So this isn't a good argument.
Please describe how in OSX, OpenWRT, FreeBSD, Android, IOS, the various Windows version gracefully starting and stopping IPv4 from an RA works? Oh, maybe give one example of a documented clean architecture that can handle this including every possible boundary condition. In contrast, having a DHCPv4 client stop sending DISCOVERs upon reception of a particular reply packet is almost a no brainer. I guess you don't see this as a technical argument, so be it. If you think that introducing network protocol changes that can only be handled by a widely used OS by rewriting their network config is a good idea when there is an alternative the can be implemented cleanly today, then there is no point further arguing. _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
