Re: [Idr] BGP KeepAlives

Requirements for Internet host (RFC 1122) mentions:

" 4.2.3.6  TCP Keep-Alives

            Implementors MAY include "keep-alives" in their TCP
            implementations, although this practice is not universally
            accepted.  If keep-alives are included, the application MUST
            be able to turn them on or off for each TCP connection, and
            they MUST default to off.

            Keep-alive packets MUST only be sent when no data or
            acknowledgement packets have been received for the
            connection within an interval.  This interval MUST be
            configurable and MUST default to no less than two hours."

Thus TCP keep-alive interval is a large value in general although it is
configurable. BGP keep-alive is specific to BGP protocol requirement and
thus it makes sense to have its own keep-alive interval without affecting
other TCP applications or TCP keep-alive frequency.

-Samita

>-----Original Message-----
>From: idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] On Behalf Of Jithu
>Arun Sreedhar
>Sent: Monday, March 31, 2008 2:45 AM
>To: idr@ietf.org
>Subject: [Idr] BGP KeepAlives
>
>Hi
>
>Why use keepalives while the liveliness of the TCP connection will by
>itself say if the peer is up or not. The TCP connections have its own
>keepalives now to check the liveliness.
>
>Jithu Arun Sreedhar
>_______________________________________________
>Idr mailing list
>Idr@ietf.org
>https://www.ietf.org/mailman/listinfo/idr

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr