Re: [Idr] New BGP capability to advertise running daemon version

[Job Snijders <[e-mail]>]

On Sat, Aug 3, 2019 at 00:50 Robert Raszuk <[e-mail]> wrote:

> The current version of the document is already a very limited subset of
> functionality mainly focusing on defining new BGP message after we took two
> documents (BGP Advisory and BGP Diagnostics Messages) and merged them into
> one document.
>
> Quote from section 10:
>
>    This memo is based on existing works [I-D.ietf-idr-advisory] and
>    [I-D.raszuk-bgp-diagnostic-message] which describe a number of
>    operational message types documented here.
>
> If one would define just new BGP Operational Message alone then the
> question will come up to provide the use cases. So here we are defining the
> former with few optional use cases which was operationally found to be of
> some use.
>
> Of course this is no longer individual draft but belongs to WG so what WG
> decides to do with it (if anything) is fine. Is core of your suggestion
> that it is much easier to push N TLVs each in separate draft via IDR or
> GROW rather then keep them in one consistent document - assuming that some
> of them are just optional TLVs?
>


Yes, that is the essence of my suggestion. I suspect it’ll be much easier
to get implementations, show interopability, and facilitate discussing
requirements with vendors if the document is chopped up.

As you pointed out the draft in its current form didn’t manage to advance
due lack of implementations, and I agree with your assessment. The current
draft is a tall order to ask from any implementer.

We can make a proposal and see if we can succeed this time around.

Kind regards,

Job

>