[Idr] new thread regarding capabilities handling

Mikael Abrahamsson <swmike@swm.pp.se> Thu, 27 April 2017 05:18 UTC

Return-Path: <swmike@swm.pp.se>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 876BB1315A9 for <idr@ietfa.amsl.com>; Wed, 26 Apr 2017 22:18:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Status: No, score=-4.301 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_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id RmpElQTClk8O for <idr@ietfa.amsl.com>; Wed, 26 Apr 2017 22:18:26 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se []) (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 6B43C131594 for <idr@ietf.org>; Wed, 26 Apr 2017 22:18:26 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 80A5FA6; Thu, 27 Apr 2017 07:18:24 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1493270304; bh=XfdL9h2CvFrgiJVdYThhe2EKecJxQuVvtaZ1Fh56jFE=; h=Date:From:To:Subject:From; b=Vi+buPKUN9qViF2kc3KW1tiQwbRXzYXXzYCf/FD/5avAUSDf6PiPKSAwBDGI+vgoV fAD3A8mZgSFqGa9Qd3+WUqAbSDxFMNPZHKOGbX86tncrwWnbqJu3HwT4eLz/j57h/8 ZGDVlsTpuv+UUZ8x7JcQQzXr5raSylSSmSZOQ4Pg=
Received: from localhost (localhost []) by uplift.swm.pp.se (Postfix) with ESMTP id 7CB75A4 for <idr@ietf.org>; Thu, 27 Apr 2017 07:18:24 +0200 (CEST)
Date: Thu, 27 Apr 2017 07:18:24 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: idr@ietf.org
Message-ID: <alpine.DEB.2.02.1704270713380.5591@uplift.swm.pp.se>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format="flowed"; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Y2BGqX1td4qX77OUSHVKHd_Mxro>
Subject: [Idr] new thread regarding capabilities handling
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 27 Apr 2017 05:18:27 -0000


disregard the part in my last email about asking why all bgp sessions in a 
peer group are flapped when one changes the config of that peer group. 
Let's discuss that here instead.

If I add "address-family ipv4 multicast" to my peer-group and it wasn't 
there before, all router OSes I know will just reset all the sessions. 
This is baffling.

I see two problems:

1. Why can't capabilities be renegotiated without BGP session restaart?

2. Why doesn't it require a command to flap the sessions to adapt to the 
new configuration? If I want to run-through my changed policy-map, I have 
to "clear soft in" (or out). Why isn't there a "clear 
all-sessions-where-capabilities-have-changed" (paraphrasing).

Current behaviour is very disruptive. You change a line of config that you 
might think is a minor change, and BOOM, all your sessions are reset and 
you have a many-minutes outage.

Mikael Abrahamsson    email: swmike@swm.pp.se