Re: [tcpm] Is this a problem?

[[e-mail](speakeasy)]

On Nov 2, 2007, at 12:00 AM, MURALI BASHYAM wrote:

>
> Clearly there seems to be no consensus on where the problem lies.   
> I've heard that it's not a transport problem, and that the
> responsibility for mitigating the problem lies with a) sockets API,  
> b) OS, and
> c) the application. That's as varied a response as one can get...
>

There is no need for TCPM to decide which of the three is the best  
solution, since all
three solutions can interoperate on the wire.

The fact that this behavior is not specified by TCP is actually a  
strength. It allows different
hosts to use very different stack strategies. Even for web servers one  
size does not fit all.
What makes sense for a high volume site supporting a large number of  
virtual sites does
not make sense for an embedded web server in a home router that  
supports configuration.

And once you vary the ULP the variations get even greater.

You need to find a more narrowly focused forum that can judge whether  
the proposed
solutions are proper for Web servers (or whatever). But these are all  
issues that the
transport layer needs to avoid.



_______________________________________________
tcpm mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/tcpm