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

[Jeffrey Haas <[e-mail]>]

Robert,

On Mon, Jan 16, 2023 at 08:28:27PM +0100, Robert Raszuk wrote:
> I am afraid you are talking about BGP version while Linda is asking about
> the subject draft bgp version ... Both are completely unrelated "versions".

I'm answering Linda's literal question.  In the cited text, she is not
asking about the new version capability.  If her intent was to ask about
that, her text wasn't stating what she wanted to ask.

> While we are here I did reread RFC4271 and I am not sure either if there is
> text to mandate closing the session when new BGP OPEN Optional Parameter is
> not recognized. Neither does FSM. Generating NOTIFICATION and continue
> should be allowed by the spec unless I missed some embedded mandate to
> close it.

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.
: 
:    If one of the Optional Parameters in the OPEN message is recognized,
:    but is malformed, then the Error Subcode MUST be set to 0
:    (Unspecific).

-- Jeff