IETF Logo Mail Archive

Re: [Idr] draft-uttaro-idr-bgp-persistence-00

Robert Raszuk <robert@raszuk.net> Wed, 16 November 2011 02:03 UTC

Return-Path: <robert@raszuk.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 D376211E817D for <idr@ietfa.amsl.com>; Tue, 15 Nov 2011 18:03:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.733
X-Spam-Level:
X-Spam-Status: No, score=-1.733 tagged_above=-999 required=5 tests=[AWL=0.866, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cZScJocNyhM7 for <idr@ietfa.amsl.com>; Tue, 15 Nov 2011 18:03:23 -0800 (PST)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 9A31E11E815B for <idr@ietf.org>; Tue, 15 Nov 2011 18:03:23 -0800 (PST)
Received: (qmail 3800 invoked by uid 399); 16 Nov 2011 02:03:22 -0000
Received: from unknown (HELO ?10.0.1.3?) (130.129.67.115) by mail1310.opentransfer.com with ESMTP; 16 Nov 2011 02:03:22 -0000
X-Originating-IP: 130.129.67.115
Message-ID: <4EC319EA.7010801@raszuk.net>
Date: Wed, 16 Nov 2011 03:03:22 +0100
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: "UTTARO, JAMES" <ju1738@att.com>
References: <4EA1F0FB.3090100@raszuk.net> <4EA487E4.2040201@raszuk.net> <B17A6910EEDD1F45980687268941550FA20750@MISOUT7MSGUSR9I.ITServices.sbc.com> <4EA84254.9000400@raszuk.net> <4EA8A91C.4090305@cisco.com> <B17A6910EEDD1F45980687268941550FA20BB8@MISOUT7MSGUSR9I.ITServices.sbc.com> <4EAA496C.9070605@cisco.com> <B17A6910EEDD1F45980687268941550FA21F96@MISOUT7MSGUSR9I.ITServices.sbc.com> <B17A6910EEDD1F45980687268941550FA324FA@MISOUT7MSGUSR9I.ITServices.sbc.com> <4EC21062.5020504@raszuk.net> <B17A6910EEDD1F45980687268941550FA32664@MISOUT7MSGUSR9I.ITServices.sbc.com> <4EC28B45.1040509@raszuk.net> <B17A6910EEDD1F45980687268941550FA327F2@MISOUT7MSGUSR9I.ITServices.sbc.com>
In-Reply-To: <B17A6910EEDD1F45980687268941550FA327F2@MISOUT7MSGUSR9I.ITServices.sbc.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "'idr@ietf.org List'" <idr@ietf.org>
Subject: Re: [Idr] draft-uttaro-idr-bgp-persistence-00
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
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: <http://www.ietf.org/mail-archive/web/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: Wed, 16 Nov 2011 02:03:24 -0000

>[Jim U>] Ok so GR is still propagating some
> path from a BGP session that went down or is compromised.. So what is
> the point here? Ok for GR but not ok for Persistence??

GR is not propagating anything .. it is just not withdrawing nor 
re-advertising it for GR timer which is much much shorter anyway then 
what persistent draft calls as a examples of timer.

Side note:

If the BGP is used for pushing configuration information which are 
stable and should stay in the network till operator decides to remove it 
- regardless of session state they were distributed by - I have no 
problem with that.

However I am of the opinion that to accomplish that you should not just 
stuck new community and re-advertise when the session goes down. You 
should up front advertise such routes with either persistent community 
or perhaps new SAFI capability flag.

Thx,
R.

v2.23.0 | Report a Bug | By Email