IETF Logo Mail Archive

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

Russ White <russw@riw.us> Wed, 16 November 2011 03:21 UTC

Return-Path: <russw@riw.us>
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 56F2611E80C7 for <idr@ietfa.amsl.com>; Tue, 15 Nov 2011 19:21:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.561
X-Spam-Level:
X-Spam-Status: No, score=-2.561 tagged_above=-999 required=5 tests=[AWL=0.038, 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 jByhMBG40RzO for <idr@ietfa.amsl.com>; Tue, 15 Nov 2011 19:21:35 -0800 (PST)
Received: from ecbiz91.inmotionhosting.com (ecbiz91.inmotionhosting.com [173.205.124.250]) by ietfa.amsl.com (Postfix) with ESMTP id DBBB311E809C for <idr@ietf.org>; Tue, 15 Nov 2011 19:21:35 -0800 (PST)
Received: from [107.17.45.77] (port=49807) by ecbiz91.inmotionhosting.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <russw@riw.us>) id 1RQW45-00029h-8W; Tue, 15 Nov 2011 22:21:33 -0500
Message-ID: <4EC32C36.8070902@riw.us>
Date: Tue, 15 Nov 2011 22:21:26 -0500
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: robert@raszuk.net
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>
In-Reply-To: <4EC28B45.1040509@raszuk.net>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ecbiz91.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - riw.us
Cc: "'idr@ietf.org List'" <idr@ietf.org>, "UTTARO, JAMES" <ju1738@att.com>
Subject: Re: [Idr] draft-uttaro-idr-bgp-persistence-00
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
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: <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 03:21:36 -0000

> I am personally completely not convinced that there is any value in
> informing my peers that one of my BGP sessions went down. You either
> have reachability to next hop and can attract traffic or you do not and
> if so you withdraw.
> 
> Telling peers that "I may be perhaps used to reach prefix X as last
> resort" is of highly questionable value.

I would go farther --this isn't questionable, it's really bad. If you
have a route you know exists, but you don't want people to use, set
things so it's a "last resort" (wait for BGP, wait for LDP, etc). If you
don't know whether or not you really have reachability, don't advertise it.

The possible problems involved in saying, "I might have a route to x,
just in case you don't have any other path there," will end up being
really, really ugly.

:-)

Russ

v2.23.0 | Report a Bug | By Email