IETF Logo Mail Archive

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

Sandy Breeze <sandy.breeze@eu.clara.net> Fri, 02 August 2019 14:44 UTC

Return-Path: <sandy.breeze@eu.clara.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 BE8C6120370 for <idr@ietfa.amsl.com>; Fri, 2 Aug 2019 07:44:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eu.clara.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 IypDTjYF5j90 for <idr@ietfa.amsl.com>; Fri, 2 Aug 2019 07:44:10 -0700 (PDT)
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (mail-eopbgr30081.outbound.protection.outlook.com [40.107.3.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F62B120362 for <idr@ietf.org>; Fri, 2 Aug 2019 07:44:10 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Ds8JL4WAFKLgXfWQoLEoGybn4dLyzfVbza1YYrIuaPr9lXUtzDQAi+dPboY2a9FRm5fcSf9cGMEniMSUiu5CS8WI2BhHk5BTRP3dsecHqSdVleaCqrohZYb/Hwg0CSc1yvEZbAZ/Bwb23x4keMOcGI9XDYQX1FCoLw4q0e8kkOgTpwbk9z/f2nGqsJCcqvehYg9r+IBGT8DSQ87Mli9iDzPGtFJmtqI/vAwxk5Fz7Vj8MzAMSwV96gP7NdA036QTfbSls+GBxIVidsDFa/chq3/o4p8qzhR9nL8ZYwAvCt/jHHRUzRs7G0FsDhXwOKrxE/9sGQAYb8iwjClh6W+vgg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=AlB1BYa3s0QjV3YhvPNgplvSxTi2kMl0yIuis13qCn0=; b=D+x8gOojl6vbpNbaZm+iWAtsPnnGPXYYx+BZw3naNv801QQbwUhsYqAASHOHG3eFveKruxLe5RvqvxWDON1DJORmru+srCsj4dLVjI+ko1QHAe71nFBNHBXLyO5ZhdJ9JuGN1CUqpuJhT7yGgwfJqErwfjFXNREfxzrdzXbTgotMwt8+Ib9MJOOoDD1a99nJwKGaGhe9lqQMY0iGeJ6g32BEl+ZLKw69iDX/W9IjO+gPWhiz4jzZDLlTdBE1Y4FAEwSCDgJHTmqKL4NOpDOwseVwBwpSDVQP3LJtDVOv6AN7KKN36Yc/YwvFVhTE/9IpxvmzjPvvAUqPJO/xdvbKeA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=eu.clara.net;dmarc=pass action=none header.from=eu.clara.net;dkim=pass header.d=eu.clara.net;arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eu.clara.net; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=AlB1BYa3s0QjV3YhvPNgplvSxTi2kMl0yIuis13qCn0=; b=6UL+mPey1imJmlQ9hGn9zy0CaeFO7545bFSh8UcpdKOZdMjjNp5FB8Rg26Jw2fVzpOC+3OuFWRe8v0s4msuFY0Ah5xKnSKaDk/mqhWJeJL0DH8h4RLpCKtVMZBW4ISQTHSgzjjaYOGABDtxfRYZY3eaD3y/VT6hCryvIJtZCOlA=
Received: from AM5PR0202MB2692.eurprd02.prod.outlook.com (10.173.93.23) by AM5PR0202MB2628.eurprd02.prod.outlook.com (10.173.89.11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2115.14; Fri, 2 Aug 2019 14:44:07 +0000
Received: from AM5PR0202MB2692.eurprd02.prod.outlook.com ([fe80::31ba:679e:11ad:b7ba]) by AM5PR0202MB2692.eurprd02.prod.outlook.com ([fe80::31ba:679e:11ad:b7ba%9]) with mapi id 15.20.2136.010; Fri, 2 Aug 2019 14:44:07 +0000
From: Sandy Breeze <sandy.breeze@eu.clara.net>
To: Donatas Abraitis <donatas.abraitis@gmail.com>, Robert Raszuk <robert@raszuk.net>
CC: "idr@ietf. org" <idr@ietf.org>
Thread-Topic: [Idr] New BGP capability to advertise running daemon version
Thread-Index: AQHVSPjUeRcxkbRXAUi/JWw94zB7BabnsiOAgAA4BgCAABYigA==
Date: Fri, 02 Aug 2019 14:44:07 +0000
Message-ID: <DDF61F35-1512-463F-98BC-17F5E6D49110@eu.clara.net>
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>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1c.0.190710
authentication-results: spf=none (sender IP is ) smtp.mailfrom=sandy.breeze@eu.clara.net;
x-originating-ip: [2001:a88:0:fffc:9cae:10c3:bfe7:57e4]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 98f33aee-3ebb-4eb1-bcbd-08d71757dfa9
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:AM5PR0202MB2628;
x-ms-traffictypediagnostic: AM5PR0202MB2628:
x-microsoft-antispam-prvs: <AM5PR0202MB262867882F3264C10B0165F4A8D90@AM5PR0202MB2628.eurprd02.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7691;
x-forefront-prvs: 011787B9DD
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(346002)(366004)(396003)(136003)(39860400002)(189003)(199004)(81156014)(14454004)(81166006)(110136005)(66946007)(478600001)(58126008)(256004)(6116002)(8676002)(5660300002)(14444005)(4744005)(66556008)(76116006)(6436002)(76176011)(91956017)(6512007)(7736002)(68736007)(71200400001)(71190400001)(66446008)(64756008)(66476007)(99286004)(186003)(11346002)(316002)(8936002)(33656002)(6486002)(44832011)(86362001)(53936002)(305945005)(25786009)(486006)(446003)(229853002)(2906002)(2616005)(46003)(6246003)(476003)(4326008)(6506007)(102836004); DIR:OUT; SFP:1101; SCL:1; SRVR:AM5PR0202MB2628; H:AM5PR0202MB2692.eurprd02.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:0;
received-spf: None (protection.outlook.com: eu.clara.net does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: NrCZYA4ry+EWgWWktEwgSzfovtGfv8e3qRDhJoztdoevv3mjUraeiG/6Ye7IVqoIwy7mGFBW/UBajth11NcGozSgGpaXrIyxVx9KM2BMdFyUdkWqtvJpA9S7yrP9qZ85v9yTkK8n4jaW/CYJfXxICtUuwWtNRp9jRdRKtB7zdqagXbjzs6P9Fn5lXY2oPRNN4vSdOcFJW3lqC7LQE00kkS2XAepV0gj9FFNg3jDyuempCsyXQevaYgpkCUTASaQzDQ+WroyXjzAofL/PMNiat24FFt6Q1ZVjL/gPhuW8AlV7y2uQmBDKT/1RkE/69kz+Fu10XQZ+wK9iazMgrb/4Ovezkk1E89VcMVlRZp1uSFdDZbwBOoROT/iK3d4nIFmZutzMT8sNOaJrKe3KjSfiyIj1Y24SD08vwil4G22Vqqw=
Content-Type: text/plain; charset="utf-8"
Content-ID: <D5DB60097AB83644ADB3AC86D1D86BE1@eurprd02.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: eu.clara.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 98f33aee-3ebb-4eb1-bcbd-08d71757dfa9
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Aug 2019 14:44:07.6901 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f87a7640-3b94-4bbd-b5fa-b4c15947cf56
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: sandy.breeze@eu.clara.net
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5PR0202MB2628
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/J04J7jvwcd8iAuxXacnjRVSZhS4>
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:44:16 -0000

Hi Donastas,

>    One simple example is a single ToR device with 300 or 400 VMs under.
>    Each runs different versions BGP daemons. I noticed that few of 400
>    peers are down, how would you quickly identify which version or why
>    they are down? By having version in place it's easy to notice such
>    things and no need to log into those all 400 hosts in advance.

How would you identify versions on those sessions which are down?  Are you assuming the ToR might cache the information after the lifetime of the session?  That’s probably quite implementation specific assumption and I probably wouldn’t bank on it being there.

I can see value though.

Sandy

v2.23.0 | Report a Bug | By Email