Re: [Idr] draft-spaghetti-idr-bgp-sendholdtimer - Feedback requested

[Robert Raszuk <[e-mail]>]

> I think the default should be a long timer and to retain the routes
> when resetting the session. However, this choice should be configurable.


There could be potentially another option ...

Once we can not write to a peer over existing TCP session we could try to
OPEN a new TCP session to the same address:179 with the same
security strings. We could use same or different BGP_ID.

/* When we discussed eBGP peering between VRFs of the same PE it was
confirmed that most if not all implementations (at that time) do not check
for different BGP_ID when accepting an OPEN). */

If a new session succeeds and we sync routes we are good. Old session can
be terminated. No data plane disruption at all.

If not it would be indeed a sign that peer's BGP is not doing that well and
perhaps confirmation that in some deployment situations it would be good to
remove him from the picture after draining his routes from our peers.

Best,
R.