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

Robert Raszuk <robert@raszuk.net> Thu, 03 November 2011 06:15 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 4EFA61F0C81 for <idr@ietfa.amsl.com>; Wed, 2 Nov 2011 23:15:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150, 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 i5P32nFB1Rtk for <idr@ietfa.amsl.com>; Wed, 2 Nov 2011 23:15:04 -0700 (PDT)
Received: from mail37.opentransfer.com (mail37.opentransfer.com [76.162.254.37]) by ietfa.amsl.com (Postfix) with SMTP id 2E2691F0C78 for <idr@ietf.org>; Wed, 2 Nov 2011 23:15:04 -0700 (PDT)
Received: (qmail 6341 invoked by uid 399); 3 Nov 2011 06:15:03 -0000
Received: from unknown (HELO ?192.168.1.57?) (178.42.163.36) by mail37.opentransfer.com with SMTP; 3 Nov 2011 06:15:03 -0000
Message-ID: <4EB23167.1000307@raszuk.net>
Date: Thu, 03 Nov 2011 07:15:03 +0100
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: erosen@cisco.com
References: <14153.1320288579@erosen-linux> <4EB22F4F.9080604@raszuk.net>
In-Reply-To: <4EB22F4F.9080604@raszuk.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "idr@ietf.org List" <idr@ietf.org>, "UTTARO, JAMES" <ju1738@att.com>
Subject: Re: [Idr] draft-uttaro-idr-bgp-persistence-00: Security Considerations
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: Thu, 03 Nov 2011 06:15:05 -0000

Extending the question ...

 > How long RR will wait after coming up to get his previous IBGP
 > peering reestablished before starting the cleanup ?

Actually RR can not do any cleanup if RR - PE2 never comes up can it ? 
It seems that PE1 will continue in this case to keep zombie paths PE2 
via RR forever.

The possible solution would be for PE1 to not only invalidate paths with 
"blinked" next hop, but also when previously lost session given paths 
were received over got reestablished. But I do not think draft mandates 
such behaviour.

R.

> Eric,
>
>> If PE1 happens to have noticed that PE2 blinked out, it may be wise
>> for PE1
>> to invalidate the routes for which PE2 is the next hop. If PE1 did not
>> notice that PE2 blinked out, it will continue to make use PE2's old
>> VPN-IP
>> routes.
>
> So when RR is down PE2's BGP process restarts while IGP not - PE1 has no
> chance to notice any next hop blink - hence till RR comes up and cleans
> up the mess pretty much network is in a bad state.
>
> How long RR will wait after coming up to get his previous IBGP peering
> reestablished before starting the cleanup ?
 >
 >            / PE2
 > PE1 -- RR
 >            \ PE3
 >
> Thx,
> R.