Re: [Idr] WG adoption call for draft-abraitis-bgp-version-capability-08, to end September 25

[Jeffrey Haas <[e-mail]>]

On Mon, Jan 16, 2023 at 08:49:46PM +0100, Robert Raszuk wrote:
> >
> > RFC 4271, §6.2:
> >
> > :    If one of the Optional Parameters in the OPEN message is not
> > :    recognized, then the Error Subcode MUST be set to Unsupported
> > :    Optional Parameters.
> 
> 
> Yes I have see it. But what I was nto able to find was a statement that
> ALL Errors MUST result in dropping the TCP session.
> 
> Note that I am all for it and not questioning it. Just was curious
> where is this explicitly written in the base spec.

I'll do this bit of your homework for you, but I'm not going to dig deeply
here through all of the edge cases.  There are bugs in the FSM text.  I have
already lost too much of my life previously finding and reporting them.
Unfortunately my notes are two jobs ago gone and it'll be up to someone else
to spend their time finding the nits.  Mostly because the earlier text from
RFC 1771 was good enough for most cases and it's usually obvious what you
should do.

(Thanks, Alex...)

:       If BGP message header checking (Event 21) or OPEN message checking
:       detects an error (Event 22) (see Section 6.2), the local system:
: 
:         - (optionally) If the SendNOTIFICATIONwithoutOPEN attribute is
:           set to TRUE, then the local system first sends a NOTIFICATION
:           message with the appropriate error code, and then
: 
:         - stops the ConnectRetryTimer (if running) and sets the
:           ConnectRetryTimer to zero,
: 
:         - releases all BGP resources,
: 
:         - drops the TCP connection,
: 
:         - increments the ConnectRetryCounter by 1,
: 
:         - (optionally) performs peer oscillation damping if the
:           DampPeerOscillations attribute is set to TRUE, and
: 
:         - changes its state to Idle.

-- Jeff