IETF Logo Mail Archive

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

Donatas Abraitis <donatas.abraitis@gmail.com> Fri, 02 August 2019 15:27 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 B90E9120431 for <idr@ietfa.amsl.com>; Fri, 2 Aug 2019 08:27:51 -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 vZd5vPQbF-17 for <idr@ietfa.amsl.com>; Fri, 2 Aug 2019 08:27:49 -0700 (PDT)
Received: from mail-qk1-x744.google.com (mail-qk1-x744.google.com [IPv6:2607:f8b0:4864:20::744]) (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 B891B120427 for <idr@ietf.org>; Fri, 2 Aug 2019 08:27:40 -0700 (PDT)
Received: by mail-qk1-x744.google.com with SMTP id w190so55067197qkc.6 for <idr@ietf.org>; Fri, 02 Aug 2019 08:27:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=55pHm70mrnYTG9OCofRBC9Q6nzQ6pYQ+8/5x8l9OOeA=; b=hiY7cSppp3qB7mpgBbYBbCv4+TIjqSRRXfuF87WRdc9WGEsI5OHKXpzH6LKNrUPDK/ 6Xtx+8YNSnsoE1Z5X9nDEWNkq7vC8IIBYl1ZPbNIXike4BT/6QZ3L9S3RuFFn4j3zfc1 xlPDuY/aEREdetHf6rkX/sWScBYEJYYm6A0v7g0+83Kp128RrKAWvNFp5GmjG2fq0C1c yk65UXL4fuYIoJ0uzemFWidtEiyrfbCkgSROUMtrRzQjoMzmWmuYul0w7/aL66VcXS5q 5cTae4YRCIPYdEtplQBh9fMvkj158fK2bKAyjtAJXjjCLYOAbFuVotysWsj7DtnKraFm XUwQ==
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:content-transfer-encoding; bh=55pHm70mrnYTG9OCofRBC9Q6nzQ6pYQ+8/5x8l9OOeA=; b=UqyTOuminH+aQsX1IVRSo/yrt1pcPAL7Xcdu21DvwU7DZl27JY3iBXVPwF1MzcBnuu ytXe1LmcqrlXGHSQq7ZFRGL9771pJTDwYdnf0IZ0EfJy6QlcZYi5IO89Qt7TOlvZdale 4AFc82U2qJahkaSonjFuhdO7XYzmOrFdWNLLKCgzibNiLtkK4nyGaE9cwlcVpxKeDwaM udl0oapEEWiPqvkEMv9gqpi9sZoX3F33ZaZEqb1/efXyq+ByeR9a2SFm/BnxaYVCP4bp L7FlPDvkUclzMot/ns/yaNaJS9XtAwz+AM8jYp7yh+8Q/cEwIAeJAMoye6u/zbooCoLq UjYw==
X-Gm-Message-State: APjAAAX9iAJAEmDYcfXu22bIEHSZ+I8mb2slR94W/D2LVNEvtL1VCc84 YNhnoPjBiOibak7jN/qOl6MtCpHIzyEJ2v4cXnc=
X-Google-Smtp-Source: APXvYqwX8AOHJIEEFWTMZRpnZVBBDdCVJTk0sDOJEn6gVMvLzTFEo/5lF6p6zZDolMFv8kcQWLw/cd8Qfdz3KsyUMnc=
X-Received: by 2002:a37:795:: with SMTP id 143mr475100qkh.140.1564759659915; Fri, 02 Aug 2019 08:27:39 -0700 (PDT)
MIME-Version: 1.0
References: <CAPF+HwV3EEUza3FyiXsd_oSkj80OwY-tE2DgFWnynq1FL2tLHg@mail.gmail.com> <015d56c13d01436890da2b8a7179fac9@turkcell.com.tr> <CAPF+HwV2Df6qcRD+GrE_JFv8W5Yh3OACKZrdv1Bw4PXQbjtDyQ@mail.gmail.com> <20190802150251.GA11217@pfrc.org> <CACWOCC_J6-wMWx7KL2dza5A77KFnoabMt7oAY-xhsGb8Vf3O5w@mail.gmail.com> <CAOj+MMFL7FVciSx1NyCp9zCPXZeRtNn4J-O1vS8btg96ZbDRuA@mail.gmail.com> <CACWOCC_+X2bVWa3iFmb6eQ8FVvvn98h_B12HVVundcqCsd+-Lw@mail.gmail.com> <dc99fdf4-cb19-34d9-d34b-5ef18f559326@foobar.org>
In-Reply-To: <dc99fdf4-cb19-34d9-d34b-5ef18f559326@foobar.org>
From: Donatas Abraitis <donatas.abraitis@gmail.com>
Date: Fri, 02 Aug 2019 18:27:28 +0300
Message-ID: <CAPF+HwVkEM5QZE1zPMYvyocjY=Xx=yds72utmBNsvQm3FRbzeA@mail.gmail.com>
To: Nick Hilliard <nick@foobar.org>
Cc: Job Snijders <job@ntt.net>, "idr@ietf.org" <idr@ietf.org>, Robert Raszuk <robert@raszuk.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/lNXdSntpZX_W7Xt1Ks0WE9RcJxY>
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 15:27:52 -0000

https://tools.ietf.org/html/draft-ietf-idr-operational-message-00
sounds interesting to me as well. It can be used to implement IRC over
BGP :)

On Fri, Aug 2, 2019 at 6:22 PM Nick Hilliard <nick@foobar.org> wrote:
>
> I'd be very much in favour of seeing draft-ietf-idr-operational-message
> being pushed towards publication.
>
> Nick
>
> Job Snijders wrote on 02/08/2019 16:21:
> > Perhaps this work should be picked up again.
> >
> > On Sat, Aug 3, 2019 at 00:19 Robert Raszuk <robert@raszuk.net
> > <mailto:robert@raszuk.net>> wrote:
> >
> >     Hi,
> >
> >     Just to refresh memory there is an active WG document precisely
> >     describing how to carry such information between BGP peers. It is
> >     called BGP Operational Message
> >
> >     https://tools.ietf.org/html/draft-ietf-idr-operational-message-00
> >
> >     The ADVISE TLV there section 3.4.1 and 4 are proposed with the very
> >     same intention as this discussion is targeting.
> >
> >     Due to no customer push vendors have not implemented it yet. So the
> >     draft is just hanging waiting for implementations.
> >
> >     I think if there is some new interest please consider to review the
> >     linked WG doc and possibly augment it with missing elements.
> >
> >     Use of BGP capabilities in current state of implementation of bgp
> >     dynamic capabilities is really not the right messaging vehicle here.
> >
> >     Thx,
> >     R.
> >
> >     On Fri, Aug 2, 2019 at 11:09 AM Job Snijders <job@ntt.net
> >     <mailto:job@ntt.net>> wrote:
> >
> >         Right now operators use the peer’s MAC address and certain TCP
> >         behaviorism (nmap -O) to attempt to conclude what the remote
> >         side might be in case of issues.
> >
> >         I see value in having this on by default. Security through
> >         obscurity isn’t the best defense anyway. I’m assuming a degree
> >         of trust exists anyway, why else set up a BGP session in the
> >         first place?
> >
> >         I think there are valid use cases, i think it is worthwhile
> >         exploring how to implement this concept.
> >
> >         Kind regards,
> >
> >         Job
> >         _______________________________________________
> >         Idr mailing list
> >         Idr@ietf.org <mailto:Idr@ietf.org>
> >         https://www.ietf.org/mailman/listinfo/idr
> >
> >
> >
> > _______________________________________________
> > Idr mailing list
> > Idr@ietf.org
> > https://www.ietf.org/mailman/listinfo/idr
> >
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr



-- 
Donatas

v2.23.0 | Report a Bug | By Email