Re: [Idr] draft-walton-bgp-add-paths-06.txt as IDR WG document

Uli Bornhauser <ub@cs.uni-bonn.de> Wed, 26 November 2008 09:13 UTC

Return-Path: <idr-bounces@ietf.org>
X-Original-To: idr-archive@megatron.ietf.org
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 204B93A6B46; Wed, 26 Nov 2008 01:13:28 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7F7E93A6B46 for <idr@core3.amsl.com>; Wed, 26 Nov 2008 01:13:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X0C1jaNuJfcH for <idr@core3.amsl.com>; Wed, 26 Nov 2008 01:13:24 -0800 (PST)
Received: from postfix.iai.uni-bonn.de (postfix.iai.uni-bonn.de [131.220.8.4]) by core3.amsl.com (Postfix) with ESMTP id DD9533A6B35 for <idr@ietf.org>; Wed, 26 Nov 2008 01:13:23 -0800 (PST)
X-IAI-Env-From: <ub@cs.uni-bonn.de> : [87.78.61.161]
Received: from [192.171.2.3] (xdsl-87-78-61-161.netcologne.de [87.78.61.161]) by postfix.iai.uni-bonn.de (Postfix) with ESMTP id 454EE5C831; Wed, 26 Nov 2008 10:13:15 +0100 (MET) (envelope-from ub@cs.uni-bonn.de) (envelope-to VARIOUS) (5) (internal use: ta=1, tu=1, te=1, am=P, au=ub)
Message-ID: <492D1324.40705@cs.uni-bonn.de>
Date: Wed, 26 Nov 2008 10:13:08 +0100
From: Uli Bornhauser <ub@cs.uni-bonn.de>
User-Agent: Thunderbird 2.0.0.18 (Windows/20081105)
MIME-Version: 1.0
To: Enke Chen <enkechen@cisco.com>
References: <200811241951.mAOJp1M40495@magenta.juniper.net> <6D26D1FE43A66F439F8109CDD4241965023565FA@INEXC1U01.in.lucent.com> <492BA8E7.9060909@cisco.com>
In-Reply-To: <492BA8E7.9060909@cisco.com>
X-Enigmail-Version: 0.95.7
Content-Type: multipart/mixed; boundary="------------010802020202020205020504"
Cc: Yakov Rekhter <yakov@juniper.net>, "Horneffer, Martin" <Martin.Horneffer@t-com.net>, idr@ietf.org
Subject: Re: [Idr] draft-walton-bgp-add-paths-06.txt as IDR WG document
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Hi Enke, Manav,

I agree to Manav that Addpath is sufficient to advertise and withdraw
multiple paths.

Enke Chen schrieb:
> Hi, Mnav:
>
> As described in the add-path document (sect. 7), the specific
> applications are to be addressed by the application documents.  For
> example, currently there are two such documents:
>
>   1) BGP Persistent Route Oscillation Solution,
> draft-walton-bgp-route-oscillation-stop-01.txt  (out-dated, needs update)
>
>  2)Fast Connectivity Restoration Using BGP Add-path,
> draft-pmohapat-idr-fast-conn-restore-00
>
> The issue of "active path" vs "inavtive path" is more relevant to #2,
> and it is indeed addressed there.
The idea sketched in the Fast Connectivity Restoration draft is a step
in the right direction. However, there are still configurations possible
where inactive paths are incorrectly rated as active ones. Such examples
show that the Border router attr_set as currently design is not
sufficient to solve the active/inactive rating problem in general. As
Manav, I believe that Addpath in hardly usable without having a
mechanism that inherently avoids this problem. I hope I will find some
time to email an ASCII example for such a configuration.

Regards

Uli
>
> Thanks.   -- Enke
>
> Bhatia, Manav (Manav) wrote:
>> Hi,
>>
>> I've read enough to believe that the proposed mechanism is sufficient to
>> advertise and withdraw multiple paths.  I am ok with this part.
>> However, one key thing that isn't obvious from this draft is how the
>> active path(s) (the ones(s) actually inserted in the FIB and being used
>> for forwarding traffic) of the advertising speaker is differentiated
>> from other non-active paths.
>>
>> Cheers, Manav
>>  
>>> -----Original Message-----
>>> From: idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] On Behalf
>>> Of Yakov Rekhter
>>> Sent: Tuesday, November 25, 2008 1.21 AM
>>> To: idr@ietf.org
>>> Subject: [Idr] draft-walton-bgp-add-paths-06.txt as IDR WG document
>>>
>>> Folks,
>>>
>>> Please send your comments on the attached. The deadline for comments
>>> is Dec 12, 2008.
>>>
>>> Yakov.
>>> ------- Forwarded Message
>>>
>>> Date:    Mon, 24 Nov 2008 14:44:00 -0500
>>> From:    "John G. Scudder" <jgs@juniper.net>
>>> To:      Yakov Rekhter <yakov@juniper.net>, skh@ghs.com
>>> cc:      Inter-Domain Routing List <idr@ietf.org>
>>> Subject: draft-walton-bgp-add-paths-06.txt as IDR WG document
>>>
>>> The authors would like to request that draft-walton-bgp-add-
>>> paths-06.txt be adopted as an IDR WG document.
>>>
>>> Thanks,
>>>
>>> - --John
>>>
>>> ------- End of Forwarded Message
>>>
>>> _______________________________________________
>>> Idr mailing list
>>> Idr@ietf.org
>>> https://www.ietf.org/mailman/listinfo/idr
>>>
>>>     
>> _______________________________________________
>> Idr mailing list
>> Idr@ietf.org
>> https://www.ietf.org/mailman/listinfo/idr
>>   
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr

-- 
______________________________________________________________
ULI BORNHAUSER                University of Bonn
                              Institute of Computer Science IV
Web:   www.cs.bonn.edu/IV/ub  Roemerstr. 164
Email: ub@cs.uni-bonn.de      D - 53117 Bonn
Phone: +49 (228) 73 - 4550    Germany
Fax:   +49 (228) 73 - 4571

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr