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

Robert Raszuk <> Thu, 29 October 2020 08:22 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8A4453A0AA4 for <>; Thu, 29 Oct 2020 01:22:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.098
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=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id rioZtIlsc_ln for <>; Thu, 29 Oct 2020 01:22:41 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 755F33A0A16 for <>; Thu, 29 Oct 2020 01:22:41 -0700 (PDT)
Received: by with SMTP id 141so2185523lfn.5 for <>; Thu, 29 Oct 2020 01:22:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=v4DLfgBcIXkkhEsDLagX4FohaZRgRIm4b5Z2FAmZ7hw=; b=SHNI9RC0NKya7CBfBzyTmM0zcubIqILpgAWUC3wh4GNkl55yd6RQijktynCC0a1Bvo gRphhZJFR2mT1xkhOUJXrF79TWpUwlZo+l8KuwwZrATtL8N0MWjznFsQFkunTtnIWOBe pk33JQd3kRO37ROVaeSPnoHAxfWABu2jvKT1lazbVC9JUSYcMl9RL6YFMExC5Har5Pko X1bmpgeLj8YRxEDxogUbYD/9J+WRjG1wxo9/0zhrt3fz1y8d62W/i58DzIYj6EKWKp5G EPNNEdYtMSUUml+zc22TIhPnb5lXVEhksb5l+s4CM0YxyYFoLqZT48ECjdaIaljZB3Zr uUJQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=v4DLfgBcIXkkhEsDLagX4FohaZRgRIm4b5Z2FAmZ7hw=; b=qd8u1ivbCG9FbDSwRBhlPoihQdRWJXRjI9ehlBzfj0lYGX4LtP7y/NZpub1kiSO4uE ojyUZybYSZ8bnFWz8FKzpo3CPcTsa7Fmdf+12Jald3D76k6ETMuxAb9XLdMjA42AYpFk +Ky26V/kfYOHiszncykhqeQcId78OwX81nq/FIyvldrJ6BkXFIoD5qasHCpJ1+gAWOyW goOFEnKO4620PWYU030z0vlpq+CMJkVTOrnGe8HR9/FfyrfFOS74iV1A7Qojq+exHPV6 1bouMhzrEIjQB10q7CoWUJbHt2Rpk99j7Glnc/AT+SNluQu0cwcHYXFzHSEEHoEM0wFO n2dA==
X-Gm-Message-State: AOAM5308irut/Nhz+mfFaMHeE1HlBai11APZAfAiJVjFJinJBcmvf//7 mryYvehsXDBdEo2kVq6YNVckqDB+QfVOBxtNRSBCbw==
X-Google-Smtp-Source: ABdhPJw/Gc6oTDvozwnQkheTqUlK31xcv6QdnzKK9xEW9j95LQZqybfctvWDUspgpiWH7x1sMiaT+xHhJmfqQidfBQs=
X-Received: by 2002:a19:83c9:: with SMTP id f192mr1053663lfd.148.1603959759476; Thu, 29 Oct 2020 01:22:39 -0700 (PDT)
MIME-Version: 1.0
References: <> <> <>
In-Reply-To: <>
From: Robert Raszuk <>
Date: Thu, 29 Oct 2020 09:22:29 +0100
Message-ID: <>
To: Jeffrey Haas <>
Cc: John Scudder <>, IDR List <>, Donatas Abraitis <>
Content-Type: multipart/alternative; boundary="000000000000b2a8a805b2cafba6"
Archived-At: <>
Subject: Re: [Idr] WG adoption call for draft-abraitis-bgp-version-capability-08, to end September 25
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 29 Oct 2020 08:22:44 -0000

> - I think requiring extended optional params is a good idea for this.  It
>   mitigates the necessity for having to do do the math to squeeze stuff in
>   or not.

How about we would just carry a fixed size URL reference to this
effectively static and opaque to the bgp protocol information instead of
actual text string ?

IMO anything which is static and is not needed for protocol operations,
best path selection etc ... should be passed as a pointer.

Fetching such string could be done in spare CPU times well before need to
locally present it or at the run time when someone executes a show cmd or
other form of query api.

Note that till one day dynamic capabilities are in place - the above would
also cover ISSU/NSR where one would like to do software upgrade without BGP
session reset.


On Wed, Oct 28, 2020 at 10:38 PM Jeffrey Haas <> wrote:

> Adding in a comment as I clear my backlog:
> On Mon, Sep 28, 2020 at 06:18:21PM +0000, John Scudder wrote:
> > It seems to me that the discussion hasn’t concluded and we are still
> having productive discussion. Hence, I would like to extend the period for
> discussion by another week, now to conclude on October 2.
> I have general concerns about this feature.  But let me offer related
> observations why my opinion is "not a fan, but of potential use":
> - This capability is advertised prior to session establishment.
>   RFC 8203 got a bit of jutification for putting in text during a
>   NOTIFICATION where the session is going down anyway.  Having this at
>   session start means less chance for damange than if we're exchanging
> stuff a
>   bit more interactively in something like the operational message.
> - I think requiring extended optional params is a good idea for this.  It
>   mitigates the necessity for having to do do the math to squeeze stuff in
>   or not.
> I would qualify the feature as "mostly harmless" and "useful in some
> circumstancs".  Use in BGP fabrics is one I find a compelling use case.
> I'm strongly supportive of the concerns with using this feature for general
> ISP eBGP use cases.  I will, however, offer the related observation that an
> ISP may like knowing what version of software their customers are running.
> It may ease situations where service providers may want to signal a
> customer
> to upgrade a vulnerable stack.
> Consider me weakly supportive of adoption and fast WGLC.
> -- Jeff
> _______________________________________________
> Idr mailing list