IETF Logo Mail Archive

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

John Scudder <jgs@juniper.net> Fri, 02 August 2019 17:35 UTC

Return-Path: <jgs@juniper.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 D987612025F for <idr@ietfa.amsl.com>; Fri, 2 Aug 2019 10:35:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=juniper.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 YiMNEPrW_R6B for <idr@ietfa.amsl.com>; Fri, 2 Aug 2019 10:35:43 -0700 (PDT)
Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (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 21A0A1201AA for <idr@ietf.org>; Fri, 2 Aug 2019 10:35:43 -0700 (PDT)
Received: from pps.filterd (m0108156.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x72HY8hg019128; Fri, 2 Aug 2019 10:35:42 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=PPS1017; bh=VV7jPixs0Xcobcn5lLzhyOyibY39IBEh5cqjKCv7Bew=; b=j0+6lez8cCdVJABGiY3iXRf5THIxsgh+WGvCj+hIqdI0REfLUuiKNUbbhn+zkScsL6hI JS/ZYrCdV8VdJkY935pQMyFJZA2yYi9iqK0wFqaT3+Q3j1wsymadTnv2ICa+PLFiYzST CpQhUgW41R2+s8jZBRswi/cTIxSQbz7++ZXkcmuXwqfhgtXwBIBBbogBLNR9YSL8qlUP VYXqVq96jp/XxEfxK9CZpz4Mek1vZF+F40AtolUnX5gUWOfBrXF8QDQ/pFzqmc4dbINC XOZPSxsAJFCU+hvzeiyj+gPy/kHHK8fw3ag0QNZZe690O6UeT1te4AuO2XVuY3h1rPTS Vg==
Received: from nam03-co1-obe.outbound.protection.outlook.com (mail-co1nam03lp2059.outbound.protection.outlook.com [104.47.40.59]) by mx0a-00273201.pphosted.com with ESMTP id 2u4jh8rqsn-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 02 Aug 2019 10:35:42 -0700
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=hmD+2S3KXl2vGGqxiyy4VGMML0oy3DFvvVRz2P8rw/QsdBBcMTvPKhYFA76RUsKoucnFfEBmVnio3pNwkIBQlCPMGxxnjB92ZzYTXI2NgYs3vfgjB3Cm5vyU4LptzjAzViyy73YCoXpPrkyyoxMY06BV7MN0kaF9GqZae4LkKuEwwGv/IxZux/LFP2oh3+/CQyxQrlIbItKyDheR3saVsX8US0FRel48tXCFA9saxyloct+9n7fgflAwPUcnCH3nVsmvJNgXIgpZDaHAhAbukllM8cXt3IZeDQ0DGw2oJhr5jj+D35DG1IQh1KF8SXPb6K/JTxXcpBZcjBg0b8M9ug==
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=VV7jPixs0Xcobcn5lLzhyOyibY39IBEh5cqjKCv7Bew=; b=G3jzj9yrTbmPQmsTaNy4tmgpTzPi4QYvF6otb71qS7id5t3ndQx2Z+1BFsyD5JKBSRj/gCNA7rL6nn1U52W72gdUdAakXNU/tp3W+HjRm9cPoMVLxX9utqfmNKz3vUBvNjESf/0JSOyqdQ2Ao6PlXaC1xYBJ6tAkJhTO8wwipLfa08ZoJ5lDTIKtpUsigUaTOIdtP2cRC8yzNz6/ft26yew5yoI9AHaTw8KHpm2HV2SiHr0FbgFOshcTk1Ou3lYnSqBBDRq91fSxFexXKZ42w+IQuI4tiilK2AS5sD6dLjQtfFanMsLNAHfjb4bJtXFutUFxGuMAObSzqDwtmC/fVA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=juniper.net;dmarc=pass action=none header.from=juniper.net;dkim=pass header.d=juniper.net;arc=none
Received: from DM6PR05MB4714.namprd05.prod.outlook.com (20.176.110.82) by DM6PR05MB4298.namprd05.prod.outlook.com (20.176.82.19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2136.10; Fri, 2 Aug 2019 17:35:40 +0000
Received: from DM6PR05MB4714.namprd05.prod.outlook.com ([fe80::64b6:144d:5560:9148]) by DM6PR05MB4714.namprd05.prod.outlook.com ([fe80::64b6:144d:5560:9148%5]) with mapi id 15.20.2136.010; Fri, 2 Aug 2019 17:35:40 +0000
From: John Scudder <jgs@juniper.net>
To: Job Snijders <job@ntt.net>, Jeffrey Haas <jhaas@pfrc.org>
CC: "idr@ietf. org" <idr@ietf.org>
Thread-Topic: [Idr] New BGP capability to advertise running daemon version
Thread-Index: AQHVSPjW9Lk8zIisakSEsOCr2eBQWqbnsiOAgAA4BgCAAAGEAIAAM8eA
Date: Fri, 02 Aug 2019 17:35:40 +0000
Message-ID: <D8989E91-7DF8-4953-9E19-0FD0DEF13560@juniper.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> <CACWOCC-7q7F3pZxHjFURxyym4d7AJsC5RATb2cMPEgYj0oAD5w@mail.gmail.com>
In-Reply-To: <CACWOCC-7q7F3pZxHjFURxyym4d7AJsC5RATb2cMPEgYj0oAD5w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [66.129.241.12]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 3e69b781-fc40-49ea-2dff-08d7176fd6a6
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(4618075)(2017052603328)(7193020); SRVR:DM6PR05MB4298;
x-ms-traffictypediagnostic: DM6PR05MB4298:
x-microsoft-antispam-prvs: <DM6PR05MB4298195FA523EDDDAD48284AAAD90@DM6PR05MB4298.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 011787B9DD
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(366004)(396003)(39860400002)(346002)(376002)(136003)(199004)(189003)(3846002)(236005)(6246003)(4326008)(64756008)(36756003)(86362001)(486006)(71200400001)(8676002)(81156014)(110136005)(25786009)(81166006)(71190400001)(66066001)(8936002)(6486002)(6436002)(33656002)(229853002)(54896002)(11346002)(53936002)(6116002)(68736007)(6512007)(256004)(66946007)(5660300002)(2616005)(446003)(91956017)(53546011)(476003)(99286004)(66476007)(66446008)(316002)(478600001)(14454004)(76116006)(66556008)(7736002)(186003)(2906002)(76176011)(6506007)(102836004)(26005); DIR:OUT; SFP:1102; SCL:1; SRVR:DM6PR05MB4298; H:DM6PR05MB4714.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: zdrHIrDG1Q8DGoKB4lESciiF0MtM0Rw50J/T8sNxSqFu/0zD1KBANF60CX4xQmg3HP8WFyLVOBhExuoFgghuoWTZtEgZRpcAIBmYce0Z01SiTvrVtEhzvyFwevh8eckcl9Z5IwxxXj/HTBoo1GcDY4ZaLcYT9yYRcOY+Be0JNqlfdumDXBTMEtz1KYsCdWmoYE1eRxCY5PVkCMisRiQKPn4i8FmBKSv55wPsFLuJdEQcoh2RF1uAjnodtfUU/iq2E0BnFZYZXfYTT5CbUupgoBf8bNU60/MOUaQQcKX8qEO+zrlJIjEZECYkcuxv/jsE0i1fA4N52CJCB0SjX0m0YLqJ3+dlweuy8N2/LSVo8D+1Iry/iH5ifHJ505m5M2U+6l3I6qleTGLwRTauxgt4YsUnN+l5AEM2OzhBPPozMX4=
Content-Type: multipart/alternative; boundary="_000_D8989E917DF849539E190FD0DEF13560junipernet_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 3e69b781-fc40-49ea-2dff-08d7176fd6a6
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Aug 2019 17:35:40.4819 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: jgs@juniper.net
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR05MB4298
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-08-02_07:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1908020183
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/1RcRvcrkCo2K29ClheXbMcdXmFM>
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 17:35:45 -0000

(As a WG member)

If the conversation is moving on to resuscitating Operational Message, that’s fine, please disregard the below. Otherwise, a few remarks regarding the specific approach of using a Capability to send this info.

On Aug 2, 2019, at 10:30 AM, Job Snijders <job@ntt.net<mailto:job@ntt.net>> wrote:
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.

I believe there is a move afoot to dust off and renovate dynamic capability. If that moves forward this might be a good candidate.

On Aug 2, 2019, at 11:02 AM, Jeffrey Haas <jhaas@pfrc.org<mailto:jhaas@pfrc.org>> wrote:
Beyond that, items put into capabilities right now are intended to impact
operational behaviors.  This doesn't feel like the best fit for me.

FQDN has been mentioned a few times (and looks to have been the model for this draft). On the other hand, the working group decided to pass on FQDN; it’s not a working group draft much less an RFC. If the WG were to adopt the present draft, I think it would be a fair to question if FQDN should be reconsidered and if not, why not, and if FQDN were to be reconsidered I think it would be fair to ask if both should be bundled together, especially since both are just unstructured text.

If I could be talked into wanting this at all, I suspect I might be more
supportive of having this be an optional parameter rather than a capability.

The problem with that suggestion is that the defined behavior for receiving an optional parameter you don’t recognize is to reset the session. I presume you would not suggest that it’s desirable for an unrecognized version string to cause a session to not come up. Years ago we did recognize this issue and introduced a way to send parameters that if unrecognized are just ignored instead of causing a reset. We called those parameters “capabilities”. :-/

—John

v2.23.0 | Report a Bug | By Email