All,
On Wed, 2005-02-02 at 13:32, Tony Hain wrote: > > That separation was a point in time implementation choice that is likely to > change in other versions of the OS. The split stack implementation by itself > does not preclude the right thing from happening through either a shim or > direct binding between the stacks, but by default there is no path. > > None of this or any other individual vendor's implementation choice affects > the value of the idea. The only thing those affect are the implementation > effort required for the app developer. Getting rid of a good idea does not > make the app developer's job any easier; it just ensures that everyone has > to go through the same level of pain. Taking it out is a bad idea. > I agree with Tony completely. The answer for dealing with buggy or expediently designed:-) implementations is not to throw capabilities out of the specifications until the bugs become features. The answer is to fix the the implementations. Tim Hartrick -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
