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

Job Snijders <job@ntt.net> Fri, 02 August 2019 14:30 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 ECA451202B4 for <idr@ietfa.amsl.com>; Fri, 2 Aug 2019 07:30:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 vw1CFuGdTyGE for <idr@ietfa.amsl.com>; Fri, 2 Aug 2019 07:30:33 -0700 (PDT)
Received: from mail3.dllstx09.us.to.gin.ntt.net (mail3.dllstx09.us.to.gin.ntt.net [IPv6:2001:418:3ff:5::26]) (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 3A9A71202AA for <idr@ietf.org>; Fri, 2 Aug 2019 07:30:33 -0700 (PDT)
Received: by mail3.dllstx09.us.to.gin.ntt.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92) (envelope-from <job@ntt.net>) id 1htYZk-0002yZ-BR (job@us.ntt.net) for idr@ietf.org; Fri, 02 Aug 2019 14:30:32 +0000
Received: by mail-oi1-f177.google.com with SMTP id a127so56908891oii.2 for <idr@ietf.org>; Fri, 02 Aug 2019 07:30:32 -0700 (PDT)
X-Gm-Message-State: APjAAAWd1frcRAwJ1By2ntLZ+WpyJzVHyLCsEOaB8oVnUBoIXt8dmQH1 kHW1iBYEhXBJ4m2v2/TD5mS/Exs8qT95nPSPEVhn9Q==
X-Google-Smtp-Source: APXvYqy6qbo2PRYOsKt5LQ2mHGx6bIOYy505d2OUoORjdDKt1lWi9s3HVOcFaYVNi+odWDxUJJRCD7qB8vfuAwhYYLU=
X-Received: by 2002:aca:1a0e:: with SMTP id a14mr2774876oia.51.1564756231985; Fri, 02 Aug 2019 07:30:31 -0700 (PDT)
MIME-Version: 1.0
References: <CAPF+HwV3EEUza3FyiXsd_oSkj80OwY-tE2DgFWnynq1FL2tLHg@mail.gmail.com> <CAOj+MMHB4BTZqo3YgdrBHCg88RdymS_Xs9Z=XM5pADqh6-uwzg@mail.gmail.com> <CAPF+HwXzMUOF0D-4VFuJ+vkQ+26+1UcEM=fWU=R82M30qra0SA@mail.gmail.com>
In-Reply-To: <CAPF+HwXzMUOF0D-4VFuJ+vkQ+26+1UcEM=fWU=R82M30qra0SA@mail.gmail.com>
From: Job Snijders <job@ntt.net>
Date: Fri, 2 Aug 2019 23:30:20 +0900
X-Gmail-Original-Message-ID: <CACWOCC-7q7F3pZxHjFURxyym4d7AJsC5RATb2cMPEgYj0oAD5w@mail.gmail.com>
Message-ID: <CACWOCC-7q7F3pZxHjFURxyym4d7AJsC5RATb2cMPEgYj0oAD5w@mail.gmail.com>
To: Donatas Abraitis <donatas.abraitis@gmail.com>
Cc: Robert Raszuk <robert@raszuk.net>, "idr@ietf. org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005e9906058f2333fd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/NNOQP_dRbB8SgXX1TsSK8NMJcS8>
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 14:30:35 -0000

On Fri, Aug 2, 2019 at 23:25 Donatas Abraitis <donatas.abraitis@gmail.com>
wrote:

> Hello guys,
>
> Job, I posted revision 01 with your replaced text.


Thanks!

It's not BGP protocol version, it's daemon/firmware version. So in
> IOS/EOS/JunOS/etc. it would be like "CISCO 15.0(1)M8" or "JunOS
> 19.1R1". Device model, we can exchange using LLDP/CDP, but not a
> specific version. Thus this would help in cases with lots of
> heterogeneous devices.


Yes, I can see value. However sometimes the BGP session is older than the
software release. There are implementations where the daemon is updated but
the BGP session stays up.

Perhaps exchanging the version - only - when the session is brought up
isn’t sufficient, and moving this into a message type of sorts may make
more sense.

Thoughts?

Kind regards,

Job