On 28 Mar 2007, at 16:04, Eddie Kohler wrote:
Colin Perkins wrote:
On 28 Mar 2007, at 08:09, Gorry Fairhurst wrote:
...
Applications that want keepalives should define some
corresponding data format: a one-byte datagram would suffice.
Not sure I agree, I'd rather the apps called-down to the
transport using a control function and asked them to do this.
I'm inclined to agree with Gorry. Keeping NAT bindings alive would
seem to be part of connection establishment and maintenance, which
is squarely in the domain of the transport layer.
Sure, but keeping the NAT alive is transport/network functionality,
and I would therefore call it a transport/network keepalive, even
if the application requests it. I assume that "application keep-
alive" means that the sending APPLICATION wants to inform the
receiving APPLICATION that it is still alive. App-to-app
notification should use data, I believe. App-to-transport or app-
to-network can use zero-length datagrams.
Then we're in agreement.
--
Colin Perkins
http://csperkins.org/
