IETF Logo Mail Archive

Re: [Idr] new thread regarding capabilities handling

Mikael Abrahamsson <swmike@swm.pp.se> Fri, 28 April 2017 05:11 UTC

Return-Path: <swmike@swm.pp.se>
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 6F4E1129B7E for <idr@ietfa.amsl.com>; Thu, 27 Apr 2017 22:11:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JpweH6qLQ9zm for <idr@ietfa.amsl.com>; Thu, 27 Apr 2017 22:11:21 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (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 13553129B61 for <idr@ietf.org>; Thu, 27 Apr 2017 22:08:52 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id AD9B4A6; Fri, 28 Apr 2017 07:08:49 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1493356129; bh=fW2RVgtTIau5soCHVPZCNkq/kmKlF26ya4LgxYoI3pg=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=EgVcUMDCLWScsVAYo2ueU1laerXxwER8zWVkBt1sdsGEIsRxol/qAnBsc/M8tQqz5 B4/T6C+3yKXDJFqg3alP60HlOrCzeLiasKtVJT5LBtvRraMWl17lP+rgbxNSRIVxfR F+nK3LCqSMoTpb9Cbeo2Zt/ffse723vstPBCZRqc=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 93395A4; Fri, 28 Apr 2017 07:08:49 +0200 (CEST)
Date: Fri, 28 Apr 2017 07:08:49 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Enke Chen <enkechen@cisco.com>
cc: idr@ietf.org
In-Reply-To: <e4ad3bd2-73cd-c1f7-6ef4-8bbd974974ae@cisco.com>
Message-ID: <alpine.DEB.2.02.1704280706040.5591@uplift.swm.pp.se>
References: <alpine.DEB.2.02.1704270713380.5591@uplift.swm.pp.se> <a7a10b72-2215-9968-e4c8-0592e29ce893@cisco.com> <alpine.DEB.2.02.1704270812470.5591@uplift.swm.pp.se> <20170427201736.GF22975@pfrc.org> <e4ad3bd2-73cd-c1f7-6ef4-8bbd974974ae@cisco.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/RDuSw774Tah4Q13Hkw8--0vz1-8>
Subject: Re: [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: Fri, 28 Apr 2017 05:11:23 -0000

On Thu, 27 Apr 2017, Enke Chen wrote:

> If there is sufficient interest, we can limit the capability to just 
> AFI/SAFI without much work.  With GR though the interest seems to have 
> dropped.

If someone had asked me 2 days ago "If you have GR enabled on a BGP 
session and add an address family to that session, will this affect 
forwarding when the session restarts" I would have said "YES!"

But from what I'm reading here, I would have been wrong? The session would 
go down but RIB/FIB would be untouched because GR?

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

v2.23.0 | Report a Bug | By Email