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

Uli Bornhauser <ub@cs.uni-bonn.de> Thu, 04 December 2008 12:30 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 E370228C0F4; Thu, 4 Dec 2008 04:30:18 -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 13C2A3A6A3B for <idr@core3.amsl.com>; Thu, 4 Dec 2008 04:30:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.249
X-Spam-Level:
X-Spam-Status: No, score=-4.249 tagged_above=-999 required=5 tests=[AWL=2.000, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
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 hPbfAIJPbGqg for <idr@core3.amsl.com>; Thu, 4 Dec 2008 04:30:15 -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 8C1893A6A38 for <idr@ietf.org>; Thu, 4 Dec 2008 04:30:15 -0800 (PST)
X-IAI-Env-From: <ub@cs.uni-bonn.de> : [87.78.40.53]
Received: from [192.171.2.3] (xdsl-87-78-40-53.netcologne.de [87.78.40.53]) by postfix.iai.uni-bonn.de (Postfix) with ESMTP id 54DAC5C828; Thu, 4 Dec 2008 13:30:07 +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: <4937CD49.80305@cs.uni-bonn.de>
Date: Thu, 04 Dec 2008 13:30:01 +0100
From: Uli Bornhauser <ub@cs.uni-bonn.de>
User-Agent: Thunderbird 2.0.0.18 (Windows/20081105)
MIME-Version: 1.0
To: raszuk@juniper.net
References: <200811241951.mAOJp1M40495@magenta.juniper.net> <6D26D1FE43A66F439F8109CDD4241965023565FA@INEXC1U01.in.lucent.com> <492BA8E7.9060909@cisco.com> <492D1324.40705@cs.uni-bonn.de> <492D2505.9080507@juniper.net> <49379FCA.6010805@cs.uni-bonn.de> <4937BF0E.1090408@juniper.net>
In-Reply-To: <4937BF0E.1090408@juniper.net>
X-Enigmail-Version: 0.95.7
Content-Type: multipart/mixed; boundary="------------050500090307080809050200"
Cc: Yakov Rekhter <yakov@juniper.net>, idr@ietf.org, "Horneffer, Martin" <Martin.Horneffer@t-com.net>
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 Robert,

I think I did not get your point yet. Why do you think that a
misconfiguration is needed for the example?
Client C-ID.5 keeps two eBGP sessions (to R-ID.6 and R-ID.3) and thus
receives q1 and p1. Client C-ID.8 also holds two external sessions (to
R-ID.9 and R-ID.2) and receives p2 and q2. The Route Reflector of
clients C-ID.5 and C-ID.8 receives all paths, and re-advertises its
first and second best (which are q1 and q2).
Thus, client C-ID.5 is provided with q1, q2, and p1. Knowing q2 has no
effect on its routing decision. Path p2 is not visible at C-ID.5 at all.

Can you please explain I detail from where client C-ID.5 should learn
path p2?

Thank you and Regards

Uli

Robert Raszuk schrieb:
> Hi Uli,
>
> > Client C-ID.5 receives the paths q1 and p1.
>
> This is already not the correct observation. In the correct
> architecture of this network (no misconfiguration) C-ID.5 would
> receive all 4 paths. Therefor p2 will win.
>
> Cheers,
> R.
>
>> Hi Robert,
>>
>> here should be a simple example for the problem regarding Add-path, Best
>> / Second Best, and Border Router Attr Set I mentioned:
>>
>> -------------------------------------
>>
>> ---------+        RR        +--------
>>       ASx|   d1 .    . d1   |ASy
>>          |     .      .     |
>>  R-ID.6.....C-ID.5  C-ID.8.....R-ID.2
>>      q1->|    .        .    |<-q2
>>          |    .        .    |
>> ---------+    .        .    +--------
>>               .        .
>>          MED2 .        . MED1
>>        +------.--------.----+
>>        |ASz p1.        .p2  |
>>        |      .        .    |
>>        |   R-ID.3    R-ID.9 |
>>
>> -------------------------------------
>> q1, q2, p1, p2: Paths advertised from neighboring systems.
>>      R: Routers in neighboring systems, Route Reflector or Clients
>>      C: Client in own System
>>     RR: Route Reflector in own System
>> *-ID.x: Router has BGP ID .x
>>     d1: Links with a distance of 1
>>    ASa: AS with ID a
>>
>> Client C-ID.5 receives the paths q1 and p1. Path p1 is the best (lower
>> BGP ID, .3) and path q1 is the second best.
>> Client C-ID.8 receives the paths q2 and p2. Path q2 is the best (lower
>> BGP ID, .2) and path p2 is the second best.
>>
>> Both clients advertise both path to the reflector RR of the system.
>>
>> Comparison of p1, p2, q1, q2 at RR:
>> p1 is discarded due to the higher MED (2, path p2 has a MED of 1)
>> p2 and q2 are discarded due to the higher BGP ID (.8)
>> --> Path q1 is the "first" best on RR.
>> --> Path p1 is also removed (due to the same BGP ID .5 (or even
>> Nexthop), cf. Draft)
>>
>> Comparison of p2, q2 at RR:
>> p2 is discarded due to the higher BGP ID in the Border Router
>> Attribute Set
>> --> Path q2 is the second best.
-- 
______________________________________________________________
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