> 1) a table which lists the options recommended and whether
> it needs to be implemented in the server or the client and
We have a table that is most of this... I suppose we could add a
column stating where the mechanism is needed (client or server).
> 2) a table which identifies which recommended options are
> currently available in commercial stacks with a comment section
> containing any additional information about stack implementor's
> plans to add them. (This might be better as an appendix since it
> will certainly be dated very quickly. But even a dated snapshot is
> better than pure hearsay.)
I don't think I agree with this... I think the big problem is that
the information is going to age too quickly. It seems to me that
this might give a company that produces a TCP with the extensions
helpful to satellites today an unfair advantage down the road. I'd
really rather not open this can of worms...
allman
--- http://gigahertz.lerc.nasa.gov/~mallman/
This archive was generated by hypermail 2b29 : Mon Feb 14 2000 - 16:14:31 EST