IETF Logo Mail Archive

Re: [Idr] I-D Action: draft-ietf-idr-bgp-nh-cost-02.txt

Nick Hilliard <nick@foobar.org> Fri, 22 May 2015 11:44 UTC

Return-Path: <nick@foobar.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 181721ACD65 for <idr@ietfa.amsl.com>; Fri, 22 May 2015 04:44:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fSlbyUDrdgBe for <idr@ietfa.amsl.com>; Fri, 22 May 2015 04:44:32 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F307A1ACD63 for <idr@ietf.org>; Fri, 22 May 2015 04:44:31 -0700 (PDT)
X-Envelope-To: idr@ietf.org
Received: from crumpet.local (089-101-195154.ntlworld.ie [89.101.195.154] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.1/8.14.9) with ESMTPSA id t4MBiT4p094831 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 22 May 2015 12:44:30 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.netability.ie: Host 089-101-195154.ntlworld.ie [89.101.195.154] (may be forged) claimed to be crumpet.local
Message-ID: <555F169D.1050602@foobar.org>
Date: Fri, 22 May 2015 12:44:29 +0100
From: Nick Hilliard <nick@foobar.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: iLya Varlashkin <ilya@nobulus.com>
References: <20150516095828.7350.47849.idtracker@ietfa.amsl.com> <55588CCA.5030709@foobar.org> <6B55178C-498B-4185-AD33-C359B425C32F@nobulus.com>
In-Reply-To: <6B55178C-498B-4185-AD33-C359B425C32F@nobulus.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/_O6aDxGS6hFttOLd5WB9GF55oeY>
Cc: idr@ietf.org
Subject: Re: [Idr] I-D Action: draft-ietf-idr-bgp-nh-cost-02.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 22 May 2015 11:44:34 -0000

On 18/05/2015 08:46, iLya Varlashkin wrote:
> Yes, RR will calculate best path per client, that’s the whole idea. This
> has been discussed with previous versions of this draft as well as in
> regards to draft-ietf-idr-bgp-optimal-route-reflection (ORR). In fact
> ORR draft provides the foundation (per client calculations) while this
> draft provides means of conveying next-hop cost information.
> 
> Also, section 3 of draft-ietf-idr-bgp-nh-cost-02 does say that NHIB
> information is used instead of speaker’s own IGP cost.

ok cool. this addresses any concerns I have about the draft.

Nick

v2.23.0 | Report a Bug | By Email