IETF Logo Mail Archive

[Idr] New BGP capability to advertise running daemon version

Donatas Abraitis <donatas.abraitis@gmail.com> Fri, 02 August 2019 06:07 UTC

Return-Path: <donatas.abraitis@gmail.com>
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 58F3E120135 for <idr@ietfa.amsl.com>; Thu, 1 Aug 2019 23:07:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 pEQIW6JVMCzX for <idr@ietfa.amsl.com>; Thu, 1 Aug 2019 23:07:56 -0700 (PDT)
Received: from mail-qt1-x82c.google.com (mail-qt1-x82c.google.com [IPv6:2607:f8b0:4864:20::82c]) (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 C730C12003E for <idr@ietf.org>; Thu, 1 Aug 2019 23:07:56 -0700 (PDT)
Received: by mail-qt1-x82c.google.com with SMTP id h18so72821578qtm.9 for <idr@ietf.org>; Thu, 01 Aug 2019 23:07:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=DyhEsux/MME8bRi1BrM5hvRXKt+VR4tQA+hGMX2IrIA=; b=Sd3fThoM+xe/shDGHO+OktIvlF7Svx4bZpNFRo9vcyKllV0qMxUnJNdwS2PoO+lrM4 98D3aOP4URsAcPVxhafuZjJG35xglbKlDNWycaoABZZ/dBQWEhEU5PJsfzlKghABMrHL 1HVUV+eZljOHH6Hgun0PEp5T3739CMpGYG5qlQ4LnXl6TC4BOPToKOnJlwPfYIDb8fV0 JP+ZgzE4pJABG4ABNgeKz5FSe7vOKQ0FeWk8bwQSIFBQMLxJBC0XHeJGwm1Kh9LqLlt4 gisArkWeDuZ5KTLdUCXSo1qkDiWE/FmtPlkYQj083nYtmrfOqFNuWt2A4Ya+flycXOpy Uq8g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=DyhEsux/MME8bRi1BrM5hvRXKt+VR4tQA+hGMX2IrIA=; b=Xc4cxM2HFzZPjsHZOraoMtpAu7Ifoc++HjmIAZYVFYC8HcMAvcmvj6h+c0R6lvIZQH Jm6swsaBl80BnUhakiIiEBr/iDn9jkaN0o4xV6hN6j181I2VFy7mO44lPhJAyptck7CM p1nIHDOTH83ofIT+iYmFn1q2emAr09AXS7p6y4AQ0g2sTTFbRTvWYqbehVnieUD+v+eB UEnT4rPOKD0JWN4G0m2qOrZuuZZvioHkyRCrr87Uga0HKm2dPGHfdcyLNshR5mc3bFi5 NNgsUVJnLbbluO2EE2BwBWEWzII3O6Dcjr46YAM8FE5Y0bCK4Li4QbCOYD/VoJyVpfJ2 Nn7w==
X-Gm-Message-State: APjAAAUORkIBnfbojzpDmbwvseesovp/58ioFb9tH7mFDYzJWhTDJWds hiVErqL4VH1Gj++v1cuV/n/BmWZ5Z0PGVL2SvlfIxD4A
X-Google-Smtp-Source: APXvYqy9bzuhWnsI6lJga0iWM3TFPprCgsZR8y4osJ7WKBBeWMoZKqPe6jsdIAtEM9GxAKNBaUm2c5pCnzTIWxA3tCQ=
X-Received: by 2002:ac8:359a:: with SMTP id k26mr91143056qtb.87.1564726074549; Thu, 01 Aug 2019 23:07:54 -0700 (PDT)
MIME-Version: 1.0
From: Donatas Abraitis <donatas.abraitis@gmail.com>
Date: Fri, 02 Aug 2019 09:07:43 +0300
Message-ID: <CAPF+HwV3EEUza3FyiXsd_oSkj80OwY-tE2DgFWnynq1FL2tLHg@mail.gmail.com>
To: idr@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/zHNioWl24mdTthQA0O4OatZ2uy4>
Subject: [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 06:09:13 -0000

Hi there!

I would like to propose a new idea of how to simplify the debugging
process when dealing with lots of different BGP speakers and even more
with different versions.

Basically, the implementation is very trivial, but it would be handy
in cases when you should debug why some functionality does not work
between two or more BGP speakers. Having this in place would speedup
troubleshooting time. Even better if that comes to automation to
gather information around all infrastructure you have.

The implementation and details are posted in this draft:
https://www.ietf.org/id/draft-abraitis-bgp-version-capability-00.txt

Waiting for comments.

Thank you!

-- 
Donatas

v2.23.0 | Report a Bug | By Email