Thomas Narten [mailto:[EMAIL PROTECTED] wrote:
> Let's see. If an implementor got this wrong, and actually tested their > implementations with one of the bazillion IPv6 implemenations or test > suites (some productized and some nearly 10 years old -- and all of > them seeming to do the same thing w.r.t. network byte order), and > there was a subsequent dispute about who was right and needed to > change their implementation, would anyone care about what was (or was > not written) in an RFC on this point? Bazillion IPv6 implementations? What if a vendor writes the application and tests it with one other vendor's software. The application does not work. And the decision now has to be made as to which vendor needs to fix the problem? This is in a lab, before deployment, before many other vendors start writing their own code to make use of this message. Add to the mix that the decision makers, those who determine who gets to make the fix, are almost certainly clueless as to any conventions in IP that we're all supposed to take for granted. In IPv6, how does one convince the decision maker to do the right thing? This happens in real life. It's not just an improbable scenario. And keep in mind that the first vendor is being very defensive by now. Bert -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
