Re: [Idr] Status of "Carrying next-hop cost information in BGP" draft
Robert Raszuk <robert@raszuk.net> Thu, 11 December 2014 18:00 UTC
Return-Path: <rraszuk@gmail.com>
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 7EA9F1ACE47 for <idr@ietfa.amsl.com>; Thu, 11 Dec 2014 10:00:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
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 7KgOqPm9Q8GI for <idr@ietfa.amsl.com>; Thu, 11 Dec 2014 10:00:25 -0800 (PST)
Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFF381A907D for <idr@ietf.org>; Thu, 11 Dec 2014 10:00:24 -0800 (PST)
Received: by mail-ie0-f173.google.com with SMTP id y20so5273708ier.4 for <idr@ietf.org>; Thu, 11 Dec 2014 10:00:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=ZFidncd8Ra871gaGcwJV99xruYcqFUtUfTMqN0uB6bw=; b=jBRvFhW/D4YhrTKaxc7ZB7S3bMnRIYfNHKu7KPaifZwqmW7t2+Qr/pUW0MbvMZomzL i4Tv2xhI26B7VXQ68MD72MSbIMuIgU1I1FYwKXV5XN/UDb/bJJmk443ZT19fZ6JtdmM8 Lb6o0aVjXpkzlaz9fchYRe/Kzkjpa9hGGD/Z38DfEOu8IhMF9yzepoIWaJNLWfBfXgeY ibna7oiDmpBs/ANbP6DWrUbm6Uft51yMp8bJ/wxzgaPWVJOLzkV9wpBHKCrrLEwAbKq1 MWbzQlA0lKi3cF51gxPl4bgQELp19oiVMRsONKAW5S9BvTz/6y//Pft9/z25m/v+HAIW aHIQ==
MIME-Version: 1.0
X-Received: by 10.107.165.75 with SMTP id o72mr8120338ioe.33.1418320823741; Thu, 11 Dec 2014 10:00:23 -0800 (PST)
Sender: rraszuk@gmail.com
Received: by 10.107.34.133 with HTTP; Thu, 11 Dec 2014 10:00:23 -0800 (PST)
In-Reply-To: <DB24E095-0F51-4AE6-A044-ECEAC8B4A6A4@nobulus.com>
References: <E77E868E-4683-4489-8A21-4FD0CEDDA4F9@de-cix.net> <DB24E095-0F51-4AE6-A044-ECEAC8B4A6A4@nobulus.com>
Date: Thu, 11 Dec 2014 10:00:23 -0800
X-Google-Sender-Auth: lygOGRsYdSn7_gOQeuc7eYaVJLM
Message-ID: <CA+b+ERm900Fzm+EWXwy6UpK_1GLv20YeqP77oh-d3hZHa1DDTQ@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: iLya Varlashkin <ilya@nobulus.com>, Thomas King <thomas.king@de-cix.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/idr/QQ4y9n-sVfhKXjY6dYF7WikAf2I
Cc: "idr@ietf.org" <idr@ietf.org>
Subject: Re: [Idr] Status of "Carrying next-hop cost information in BGP" draft
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: Thu, 11 Dec 2014 18:00:26 -0000
Just an update ... Related draft Optimal RR reflection has been implemented at least by two big commercial vendors. Exa-BGP was also looking at it. The comment I got when asking for this extension implementation was that next hop cost can be already taken from BGP-LS extension so there is no need to implement yet another mechanism. While it is possible for just IGP metric the scope of this document was broader allowing non metric related responses. For those extending the IGP + BGP-LS as indirect mechanism may not be the most lucky choice. Rgs, r. On Thu, Dec 11, 2014 at 9:22 AM, iLya Varlashkin <ilya@nobulus.com> wrote: > Hi Thomas, > > great to hear about practical case for NH SAFI draft. Although currently the draft is in latent state, it’s not abandoned. Basically there’s a need in implementation to figure out how proposed encoding format fits existing code bases. Are you working on a code that could incorporate this feature? If so, let discuss in more details. > > Kind regards, > iLya > > On 11 Dec 2014, at 16:41, Thomas King <thomas.king@de-cix.net> wrote: > >> Hello Ily and Robert, >> >> I am a big fan of your draft "Carrying next-hop cost information in BGP" [0]. Unfortunately, I do not see much progress on the draft since a couple of months. I am currently working with a bunch of guys on a draft about a feature for route servers which relies on ideas proposed by your draft. So it is crucial for me to understand if this draft is dead or still alive. Could you please give me the status of the draft from your point of view? >> >> Thanks in advance, >> Thomas >> >> [0]: http://tools.ietf.org/html/draft-ietf-idr-bgp-nh-cost-01 >> >> -- >> Dr. Thomas King >> Manager Research & Development >> >> DE-CIX Management GmbH | Lindleystraße 12 | 60314 Frankfurt am Main | Germany | www.de-cix.net >> Phone +49 69 1730902 87 | Mobile +49 175 1161428 | Fax +49 69 4056 2716 | thomas.king@de-cix.net >> Geschaeftsfuehrer Harald A. Summa | Registergericht AG Koeln HRB 51135 >> >
- [Idr] Status of "Carrying next-hop cost informati… Thomas King
- Re: [Idr] Status of "Carrying next-hop cost infor… iLya Varlashkin
- Re: [Idr] Status of "Carrying next-hop cost infor… Robert Raszuk