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

Job Snijders <job@ntt.net> Fri, 02 August 2019 15:09 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 89E751203AA for <idr@ietfa.amsl.com>; Fri, 2 Aug 2019 08:09:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 2V7ONLc7QmEB for <idr@ietfa.amsl.com>; Fri, 2 Aug 2019 08:09:35 -0700 (PDT)
Received: from mail3.mlpsca01.us.to.gin.ntt.net (mail3.mlpsca01.us.to.gin.ntt.net [IPv6:2001:418:1401:17::242]) (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 6C4711203A9 for <idr@ietf.org>; Fri, 2 Aug 2019 08:09:35 -0700 (PDT)
Received: by mail3.mlpsca01.us.to.gin.ntt.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92) (envelope-from <job@ntt.net>) id 1htZBX-000Gck-2m (job@us.ntt.net) for idr@ietf.org; Fri, 02 Aug 2019 15:09:35 +0000
Received: by mail-ot1-f47.google.com with SMTP id z23so50112027ote.13 for <idr@ietf.org>; Fri, 02 Aug 2019 08:09:34 -0700 (PDT)
X-Gm-Message-State: APjAAAVJ+lW3nFtanL8+IPYu81hYaNbmQmnlDFkdetF0IE6EzmHCl0Z5 EeVlvvKnSh4prPzIsgRdhg6qC7p1ON8Rd/l6+sA=
X-Google-Smtp-Source: APXvYqwRR4wLCrpvjSpXlVDg5hB1bs4oup7wUnKIPP6q/3Kgvz7uf+3qhfuvUtgID0Y5p38vjRCXcd9KE73nOJMoRxo=
X-Received: by 2002:a9d:7d90:: with SMTP id j16mr30250096otn.95.1564758574502; Fri, 02 Aug 2019 08:09:34 -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>
In-Reply-To: <20190802150251.GA11217@pfrc.org>
From: Job Snijders <job@ntt.net>
Date: Sat, 3 Aug 2019 00:09:22 +0900
X-Gmail-Original-Message-ID: <CACWOCC_J6-wMWx7KL2dza5A77KFnoabMt7oAY-xhsGb8Vf3O5w@mail.gmail.com>
Message-ID: <CACWOCC_J6-wMWx7KL2dza5A77KFnoabMt7oAY-xhsGb8Vf3O5w@mail.gmail.com>
To: Jeffrey Haas <jhaas@pfrc.org>
Cc: Donatas Abraitis <donatas.abraitis@gmail.com>, "idr@ietf.org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000fe25c7058f23be13"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/rx4xR3uwpXTteA0fH7PmMZljhjY>
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:09:38 -0000

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