Re: Connection Establishment

[Henk Langeveld - NL <[e-mail]>]

> Jeremy Harris - Network Service Providers Division wrote:
>>I believe that an HTTP GET which hits an in-kernel cache satisfies the
>>above constraints; the transaction can then be reduced to a minimum of
>>three packets.


David Nicol wrote:
> fascinating -- you're suggesting HTTP over datagrams.  Or at least
> acting like datagrams when all you really want is a datagram.  You
> can dispense with the connection when all you want is a datagram.

This is beginning to look like the DNS approach:  Just use udp
on the first attempt, and revert to tcp when the result would be
too large?

Frankly, given that one of the conditions given was sufficient
resistance/defence against DoS attacks,  I doubt this will ever
escape the lab.  A proper defence against DoS attacks is miserly
conduct with your resources, until you've established at least
some validity in the request - this will require a round trip from
server to client.

If you're going to allow initial datagrams carrying data, you'll
have to limit the size of that data, possibly using the same
constraints as the DNS udp/tcp switch referred to above.  You might
be thinking of a specific application for this web-service, where
you'd control the network stack of both client and server *and*
the network in between.  Then you've got your value-add network,
with your own application protocol - why use http?

Henk