[c-nsp] BGP KEEPALIVE maximum frequency

[Keegan Holley]

On Dec 4, 2010, at 6:23 PM, Pete Templin <petelists at templin.org> wrote:

> On 12/4/10 9:38 AM, M. V. wrote:
> 
>> as i said, RFC4271 says: router should send first KEEPALIVE when goes from
>> "OpenSent" to "OpenConfirm". then when first KEEPALIVE of its peer is recieved,
>> it goes to "Established" state, and starts its KeepAlive-Timer(default=60s).  so
>> the next (2nd so far) KEEPALIVE message has to be sent after 60 seconds.
>> but what i see is: routers send first KEEPALIVE when they go from "OpenSent" to
>> "OpenConfirm". and then send 1 or 2 (usually 2) KEEPALIVEs immediately after
>> they go to Established state.
>> plus,  RFC4271 says: "KEEPALIVE messages MUST NOT be sent more frequently than
>> one per second" which happens here. so, i wanted to know, why they behave like
>> this.
> 
> I see that you're "bored to death", but is it really essential to be the RFC police on an operations list?
> 
> Is it breaking anything for you?
> 
> pt

This may be relevant if it causes issues with interoperability.       At least for those who purchase routers from more than one vendor.  

> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>