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

Robert Raszuk <robert@raszuk.net> Wed, 09 September 2020 18:19 UTC

Return-Path: <robert@raszuk.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 B9B5A3A0C11 for <idr@ietfa.amsl.com>; Wed, 9 Sep 2020 11:19:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=raszuk.net
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 NDti25qnxPZK for <idr@ietfa.amsl.com>; Wed, 9 Sep 2020 11:19:19 -0700 (PDT)
Received: from mail-ed1-x52e.google.com (mail-ed1-x52e.google.com [IPv6:2a00:1450:4864:20::52e]) (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 A12E33A0B4B for <idr@ietf.org>; Wed, 9 Sep 2020 11:19:19 -0700 (PDT)
Received: by mail-ed1-x52e.google.com with SMTP id w1so3667441edr.3 for <idr@ietf.org>; Wed, 09 Sep 2020 11:19:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=B14H13lxlt8McCO7coJQKA22+qLq2jtHsoSj4PiWgjU=; b=Lm2sJnc3ONF0S4p7iHt4irpclx84ft/KJlwyjJX0cBhoLq2NTrPMAlEuTISxEk4Llq vbO/I5OeHbRbBzDM2qGh/bwkpDYy1UECSDI+sQOCY4v/CEI7dWSEMv/K0FybaPcCUf59 20pKD5ky3RnJGtyJLS4QW13c4Lu2+OuATdEuJMShdRXhI81XwJIciTO0I/KCmSPl2m6x pKm/QlVFWa9jqVZApc6bv7Q6W4WnNTjNLth4qlHwd6ruoB5rHwIGmwpX+V0CJzGXZfAH CuENrBZTf/6PbGyurg0Vkid7sc4is8ZNHTu7OZhjBqxyF3bjULCkook1DGD/gyaKz/Ar b7Eg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=B14H13lxlt8McCO7coJQKA22+qLq2jtHsoSj4PiWgjU=; b=UQh31ehqO2H571OchcCdQFDN4AmJFf63i2a4VoARnQDtJrq5LP46pn3u76djHEXjX9 DfSdBdXaINm8qI5DxbPvzTtExsTUEJ7vcR0g/S6+tGVhs20DGjRKRuf4PqBJFK1pMIG4 ykvVfx9v9/GuQ2zrZHxOHLi/Afa8fIpKpC+CTJuGwQrZZAZeypbPGTUqb2kVgz5n83u1 j3IZzNeFAZrJQxXj66X+/CdGYIIrWrRqlwJZsdLld/XKKam9mJOvAQjHUpCf6v26C4Fb IuuGPmZDVRSYuSfPt8JdOCaNyN/RBLx/0dpdXvJ/ChiKg8PtoxBNGWUwe0M/v4/W6HRM 5zIg==
X-Gm-Message-State: AOAM530AgoIK1s2oLM4wa+vCiMw4KwwOHAdwmjc27lxptkI2TtvyOCbP o/rV7ygMr85BN4QTnVzUD4Hj/2MiSaqoPI1orPz9oA==
X-Google-Smtp-Source: ABdhPJzjKU4Iry7M6hQ4kfEgHDQNTdhz9PQwshutmpBW8x86eo7bodgAvHWQ3QpSpWd1+MUkf05LwnOOXpbwFonkZBs=
X-Received: by 2002:a50:9f6f:: with SMTP id b102mr5347251edf.272.1599675558093; Wed, 09 Sep 2020 11:19:18 -0700 (PDT)
MIME-Version: 1.0
References: <CAOj+MMGvoghDMLax5oFoqEK6PO0gvew_dN3OyRz8k8c3wyYeUA@mail.gmail.com> <E3EC0E6B-4848-4FA4-B7D7-399B6831C346@hostinger.com>
In-Reply-To: <E3EC0E6B-4848-4FA4-B7D7-399B6831C346@hostinger.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Wed, 9 Sep 2020 20:19:08 +0200
Message-ID: <CAOj+MMGXDGb-_5U0q+839qfQYyf5Yq_7Q9YzG8zqoQ4qb4E6Og@mail.gmail.com>
To: Donatas Abraitis <donatas.abraitis@hostinger.com>
Cc: "Jakob Heitz (jheitz)" <jheitz=40cisco.com@dmarc.ietf.org>, IDR List <idr@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000065812505aee57d65"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Dokgxg2IKYrRGdh5-kHMuzMlqIA>
Subject: Re: [Idr] WG adoption call for draft-abraitis-bgp-version-capability-08, to end September 25
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, 09 Sep 2020 18:19:22 -0000

> these times BGP is used not in telcos mainly.

Great ! Thanks for this valuable insight.

Well last time I checked BGP is rather needed for the Internet. And this is
major focus here to keep The Internet running.

If we start throwing one off stones into it - it can still hold ... till
the time when it no longer can. And then what ? Do we have backoff plan ?
What if someone takes 128 bytes of capabilities tomorrow ?

I proposed splitting BGP into telco/Internet BGP and all other use cases
many year ago. All you enumerated fit perfectly into the latter.

- - -

Donatas,

Said all of the above - I do like your suggestion to augment BGP with this
extra information. It may be useful. I would actually still like to know
who is behind an RR as far as BGP implementation is concerned though.

What if we define new message (we can call it operational message) and for
now just have one TLV there carrying OS version of BGP between connected
peers ?

What do you think ? Would you add this to FRR ?

Many thx,
Robert.







On Wed, Sep 9, 2020 at 7:28 PM Donatas Abraitis <
donatas.abraitis@hostinger.com> wrote:

> Robert, I fully understand you, but these times BGP is used not in telcos
> mainly.
>
>  It's happening in services. Even MySQL HA can be achieved with help of
> BGP protocol.
>
> Kubernetes, Openshift, containers, etc., changed a shape how processes are
> running these days actually. But that's not about that.
>
> Imagine a cluster of 1000 containers each running a specific version of
> BGP daemon. With such setup I would need another 1000 containers running
> lldpd and exposing information about the versions. Even this won't work
> because of network namespaces.
>
> Implementing huge rfcs take time, and this is very trivial to implement
> for any existing daemons. I'm not referring big vendors here, but more
> about software vendors.
>
>
> Sent from my iPhone
>
> On 2020-09-09, at 20:16, Robert Raszuk <robert@raszuk.net> wrote:
>
> 
> Jakob,
>
> I know you love simple features easy to implement. We all to pick like low
> hanging fruits.
>
> But I support Randy in his opinion expressed on this thread that we should
> look at the bigger picture here instead of troughing ASCII or UTF strings
> at random places into current BGP protocol just because this is "easy to
> do".
>
> Thx,
> R.
>
>
>
>
>
>
>
>
> On Wed, Sep 9, 2020 at 5:32 PM Jakob Heitz (jheitz) <jheitz=
> 40cisco.com@dmarc.ietf.org> wrote:
>
>> No.
>>
>> This is a simple feature to allow an operator to get a quick idea
>> with "show bgp neighbors" what he is looking at.
>> Let's not boil this too much.
>>
>> Regards,
>> Jakob.
>>
>> -----Original Message-----
>> From: Nick Hilliard <nick@foobar.org>
>> Sent: Wednesday, September 9, 2020 1:23 AM
>> To: Jakob Heitz (jheitz) <jheitz@cisco.com>
>> Cc: John Scudder <jgs@juniper.net>et>; IDR List <idr@ietf.org>rg>; Donatas
>> Abraitis <donatas.abraitis@hostinger.com>
>> Subject: Re: [Idr] WG adoption call for
>> draft-abraitis-bgp-version-capability-08, to end September 25
>>
>> Jakob Heitz (jheitz) wrote on 09/09/2020 02:39:
>> > Nevertheless, even with all these possible issues, I think it would
>> > be super handy to run "show bgp neighbors" and see the software vendor
>> > and version for each neighbor.
>>
>> yeah, this would be useful.  Would there be value in splitting the host
>> stack name from the version name?
>>
>> Nick
>> _______________________________________________
>> Idr mailing list
>> Idr@ietf.org
>> https://www.ietf.org/mailman/listinfo/idr
>>
>