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

Job Snijders <job@ntt.net> Fri, 02 August 2019 16:02 UTC

Return-Path: <job@ntt.net>
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 8E9BC12066C for <idr@ietfa.amsl.com>; Fri, 2 Aug 2019 09:02:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 WMSXAzOLmwm7 for <idr@ietfa.amsl.com>; Fri, 2 Aug 2019 09:02:46 -0700 (PDT)
Received: from mail3.mlpsca01.us.to.gin.ntt.net (mail3.mlpsca01.us.to.gin.ntt.net [IPv6:2001:418:1401:17::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0723B120659 for <idr@ietf.org>; Fri, 2 Aug 2019 09:02:46 -0700 (PDT)
Received: by mail3.mlpsca01.us.to.gin.ntt.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92) (envelope-from <job@ntt.net>) id 1hta0z-0005Zb-R2 (job@us.ntt.net) for idr@ietf.org; Fri, 02 Aug 2019 16:02:45 +0000
Received: by mail-ot1-f42.google.com with SMTP id x21so13142306otq.12 for <idr@ietf.org>; Fri, 02 Aug 2019 09:02:45 -0700 (PDT)
X-Gm-Message-State: APjAAAX55temg1rR6UWvkEvWi/CdCAMjjd0zgtAJuCKs5vAbs92e6nmZ C6qRvekM/jNhvlocedpQSM8Rn0EkgM77LZ7WJj8=
X-Google-Smtp-Source: APXvYqwuLDR2FnUAgTIy0BwtBUBboyujvjbVymD0IS2fBqq6yvuepp9/ZUoykvG2HioXrhAqAua0ChnF9ufHnK5JQE4=
X-Received: by 2002:a9d:7d90:: with SMTP id j16mr30446580otn.95.1564761765110; Fri, 02 Aug 2019 09:02:45 -0700 (PDT)
MIME-Version: 1.0
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>
From: Job Snijders <job@ntt.net>
Date: Sat, 3 Aug 2019 01:02:34 +0900
X-Gmail-Original-Message-ID: <CACWOCC9xAbyEQCtFWWqvMFDdY2JqoXR_XQUFAPywEY8WOKG6sw@mail.gmail.com>
Message-ID: <CACWOCC9xAbyEQCtFWWqvMFDdY2JqoXR_XQUFAPywEY8WOKG6sw@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
Cc: Job Snijders <job@ntt.net>, Nick Hilliard <nick@foobar.org>, Rob Shakir <robjs@google.com>, david.freedman@uk.clara.net, "idr@ietf.org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002b002c058f247d59"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/K_hbe9lfTu02ZQcbFugQgooKm-c>
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: Fri, 02 Aug 2019 16:02:50 -0000

On Sat, Aug 3, 2019 at 00:50 Robert Raszuk <robert@raszuk.net> 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

>