Connected: An Internet Encyclopedia
RFC 1771 - 4.4 KEEPALIVE Message Format

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1771
Up: 4. Message Formats
Prev: 4.3 UPDATE Message Format
Next: 4.5 NOTIFICATION Message Format

### 4.4 KEEPALIVE Message Format

BGP does not use any transport protocol-based keep-alive mechanism to determine if peers are reachable. Instead, KEEPALIVE messages are exchanged between peers often enough as not to cause the Hold Timer to expire. A reasonable maximum time between KEEPALIVE messages would be one third of the Hold Time interval. KEEPALIVE messages MUST NOT be sent more frequently than one per second. An implementation MAY adjust the rate at which it sends KEEPALIVE messages as a function of the Hold Time interval.

If the negotiated Hold Time interval is zero, then periodic KEEPALIVE messages MUST NOT be sent.

KEEPALIVE message consists of only message header and has a length of 19 octets.

Next: 4.5 NOTIFICATION Message Format

Connected: An Internet Encyclopedia
RFC 1771 - 4.4 KEEPALIVE Message Format