[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: I-D ACTION:draft-ietf-ipsec-udp-encaps-00.txt

To: "jshukla" <jshukla@earthlink.net>
Subject: Re: I-D ACTION:draft-ietf-ipsec-udp-encaps-00.txt
From: Bill Sommerfeld <sommerfeld@East.Sun.COM>
Date: Thu, 12 Jul 2001 18:23:28 -0400
cc: "Mason, David" <David_Mason@nai.com>, "Derek Atkins" <warlord@mit.edu>, "'sommerfeld@east.sun.com'" <sommerfeld@East.Sun.COM>, "'Brian Swander'" <briansw@windows.microsoft.com>, ipsec@lists.tislabs.com
In-reply-to: Your message of "Thu, 12 Jul 2001 15:19:04 PDT." <000c01c10b20$aa3d7d20$03b02304@ffb5b>
Reply-to: sommerfeld@East.Sun.COM
Sender: owner-ipsec@lists.tislabs.com

> Most TCP implementations have a built-in keep
> alive. Default is supposed to be 2 hrs, but it is
> not uncommon to see messages sent every
> 10-15min.

RFC1122 (Host Requirements, part 1) specifies that TCP keep-alives
MUST default to OFF and the default idle timeout MUST be greater than
2 hours.

Individual applications may turn on keepalives, but it would be
incorrect for any other part of the system to assume that they're
always (or even usually) on.

						- Bill

References:

Re: I-D ACTION:draft-ietf-ipsec-udp-encaps-00.txt

From: "jshukla" <jshukla@earthlink.net>

Prev by Date: Re: I-D ACTION:draft-ietf-ipsec-udp-encaps-00.txt
Next by Date: Prefered minimum Phase2 lifetime
Prev by thread: Re: I-D ACTION:draft-ietf-ipsec-udp-encaps-00.txt
Next by thread: Re: I-D ACTION:draft-ietf-ipsec-udp-encaps-00.txt
Index(es):
- Main
- Thread