IETF Logo Mail Archive

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

"Susan Hares" <shares@ndzh.com> Wed, 07 August 2019 15:35 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50CD2120396 for <idr@ietfa.amsl.com>; Wed, 7 Aug 2019 08:35:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.949
X-Spam-Level:
X-Spam-Status: No, score=0.949 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YSqaU8rakcrd for <idr@ietfa.amsl.com>; Wed, 7 Aug 2019 08:35:04 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-100-static.hfc.comcastbusiness.net [50.245.122.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5506F120393 for <idr@ietf.org>; Wed, 7 Aug 2019 08:35:04 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=97.112.26.170;
From: Susan Hares <shares@ndzh.com>
To: 'Robert Raszuk' <robert@raszuk.net>, 'Job Snijders' <job@ntt.net>
Cc: 'Rob Shakir' <robjs@google.com>, idr@ietf.org, david.freedman@uk.clara.net
References: <CAPF+HwV3EEUza3FyiXsd_oSkj80OwY-tE2DgFWnynq1FL2tLHg@mail.gmail.com> <015d56c13d01436890da2b8a7179fac9@turkcell.com.tr> <CAPF+HwV2Df6qcRD+GrE_JFv8W5Yh3OACKZrdv1Bw4PXQbjtDyQ@mail.gmail.com> <20190802150251.GA11217@pfrc.org> <CACWOCC_J6-wMWx7KL2dza5A77KFnoabMt7oAY-xhsGb8Vf3O5w@mail.gmail.com> <CAOj+MMFL7FVciSx1NyCp9zCPXZeRtNn4J-O1vS8btg96ZbDRuA@mail.gmail.com> <CACWOCC_+X2bVWa3iFmb6eQ8FVvvn98h_B12HVVundcqCsd+-Lw@mail.gmail.com> <dc99fdf4-cb19-34d9-d34b-5ef18f559326@foobar.org> <CAOj+MMHEmQmPeYjWr-v3B1HXL3wYkku57e0SnZaT5dBpYrLAJw@mail.gmail.com> <CACWOCC939gEujomMLqiwA77EkTC7XGf_jSkCOOVhTaV6JKEGvA@mail.gmail.com> <CAOj+MMFhtM67UQfBrfYCf_UuRpC6HOFwU_NcRfrS=K8jyu4VMA@mail.gmail.com>
In-Reply-To: <CAOj+MMFhtM67UQfBrfYCf_UuRpC6HOFwU_NcRfrS=K8jyu4VMA@mail.gmail.com>
Date: Wed, 07 Aug 2019 11:34:52 -0400
Message-ID: <016c01d54d35$a8fce890$faf6b9b0$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_016D_01D54D14.21EDB990"
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AQGHHUFXsNXESvgLKN7qzs5kGLaZSAGTgg1eAY3ubK8B6SE7VQI8+owCAcKpOH4ByGAyAwIQKaHdA2la8toBr2WfQQH1/FuKpuyk0qA=
X-Antivirus: AVG (VPS 190807-0, 08/07/2019), Outbound message
X-Antivirus-Status: Not-Tested
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/zWkfQWkGEwV1yHYNeoynvud7EmM>
Subject: Re: [Idr] New BGP capability to advertise running daemon version
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Aug 2019 15:35:06 -0000

Robert:

 

The TLVs on an IDR message will need to be done in IDR. 

 

Sue 

 

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Robert Raszuk
Sent: Friday, August 2, 2019 11:50 AM
To: Job Snijders
Cc: Rob Shakir; idr@ietf.org; david.freedman@uk.clara.net
Subject: Re: [Idr] New BGP capability to advertise running daemon version

 

Dear Job,

 

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 ?

 

Thx,
R.

 

 

On Fri, Aug 2, 2019 at 11:36 AM Job Snijders <job@ntt.net> wrote:

Dear robert,

 

On Sat, Aug 3, 2019 at 00:29 Robert Raszuk <robert@raszuk.net> wrote:

Extremely happy to see your support here. 

 

Draft wise I think we still have sources :) But what really got this work stuck is implementations. 

 

Perhaps if we could make FRR and BIRD to implement it we could test it and ask for WGLC. 

 

Of course if there is seriou sinterest we should also ask for IANA allocations too. I think both Rob & David would be happy to see this moving forward too :) 

 

In order to move this forward, I think it would be good to split the draft out into the framework and then separately document the features. This allows the work to progress (in part), even when we encounter controversy.

 

Cutting this up in smaller chunks will increase the likelihood of reaching the finish line.

 

It also would make RFP / feature requesting + vendor management easier if we make sure all the documents in their entirety represent coherent building blocks.

 

I’m happy to work on such a proposal with you.  

 

Kind regards,

 

Job

v2.23.0 | Report a Bug | By Email