Re: [Idr] TCP & BGP: Some don't send terminate BGP when holdtimer expired, because TCP recv window is 0

[Robert Raszuk <[e-mail]>]

I went back and reread the thread:

   https://mailarchive.ietf.org/arch/msg/idr/q0Sx5d3zZjfOmOQ4lO2OZAHh9Lc/

Shouldn't it be better if we first ask implementations to provide show
command/api to list all peers and min-max durations of TCP Window being 0
without actually doing any automagic RST/NOTIFICATION/FIN ?

This could allow to better understand which peers are getting behind in
their control plane and perhaps also allow to set the RST timer under such
conditions by operator? If he chooses this to be equal to HOLD TIME so be
it but I am not sure this would be universally an optimal choice.

Along the same lines we should perhaps also list per BGP peer number of
DUPLICATE ACKS, RETRANSMISSIONS etc ...

Are there implementations already deployed in DFZ allowing such data to be
displayed per each BGP peer ?

Thx,
Robert.