Re: [Idr] decraene-idr-next-hop-capability <-> ietf-idr-bgp-nh-cost

Robert Raszuk <robert@raszuk.net> Tue, 24 March 2015 21:42 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 616101A1AD9 for <idr@ietfa.amsl.com>; Tue, 24 Mar 2015 14:42:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 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, HTML_MESSAGE=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 im4TX8xE2G-u for <idr@ietfa.amsl.com>; Tue, 24 Mar 2015 14:42:53 -0700 (PDT)
Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com [IPv6:2607:f8b0:4001:c03::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 53AFD1A0E10 for <idr@ietf.org>; Tue, 24 Mar 2015 14:42:53 -0700 (PDT)
Received: by iecvj10 with SMTP id vj10so8772017iec.0 for <idr@ietf.org>; Tue, 24 Mar 2015 14:42:52 -0700 (PDT)
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; bh=nTxpc7prktzEhVqzr3A2/WV3gBKnJFdlvf7Cq1Se0xU=; b=YaJXGwyT6yhgsf3STJ33GOQ18LLkX0zqq0vaeF3JKj3rodF7wjqwAar3IbzTqx2Pkn Vku40OtGM24t7DcAgbVWNwlLrC4NaO3z2ygUqP+FD2G4eDLHe5VwtXO+cuV+7T4qMfdA QWYjQG08ctvPMYDfWOoQnUlr928UYCO+vj1JCV6iAVH7E+mPq6qTLfMrQWk9Gkg5M+CF sUHFHnja/lFLi5edZvjOTbj/NlRgUHBLPrl5Q8rdWXfeWlako4bvOY0PA07Kpla0SXvH r9VW0wfCsi4e5bTM3V1u0emku5zXIQny+QHsKMQjZ2auJiXfgwPkALSYgI2Fxm5bRF8b hrHw==
MIME-Version: 1.0
X-Received: by 10.50.29.109 with SMTP id j13mr25621032igh.2.1427233372847; Tue, 24 Mar 2015 14:42:52 -0700 (PDT)
Sender: rraszuk@gmail.com
Received: by 10.107.137.70 with HTTP; Tue, 24 Mar 2015 14:42:52 -0700 (PDT)
Received: by 10.107.137.70 with HTTP; Tue, 24 Mar 2015 14:42:52 -0700 (PDT)
In-Reply-To: <20150324212935.GG612698@eidolon>
References: <20150324212935.GG612698@eidolon>
Date: Tue, 24 Mar 2015 22:42:52 +0100
X-Google-Sender-Auth: usAe9Ps2bFeuO7UcG3ZGWxFTfMg
Message-ID: <CA+b+ERkRbpwWU8BsYG5h8ndBPrYDDjcaB9wYe+0EX2wgdQFiDA@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: David Lamparter <equinox@diac24.net>
Content-Type: multipart/alternative; boundary=047d7bd74a3033439305120faa47
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/KmNsXgumWKxNNwUJ2tLROfWmICw>
Cc: idr wg <idr@ietf.org>, ilya.varlashkin@easynet.com, Bruno Decraene <bruno.decraene@orange.com>
Subject: Re: [Idr] decraene-idr-next-hop-capability <-> ietf-idr-bgp-nh-cost
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: Tue, 24 Mar 2015 21:42:55 -0000

Hello David,

Yes I very much agree with you that nh safi is a much better fit for
transporting bgp next hop capabilities.

Many thx,
R.
On Mar 24, 2015 4:29 PM, "David Lamparter" <equinox@diac24.net> wrote:

> Hi Bruno, Ilya, Robert,
> Hi idr list,
>
>
> the next-hop-capability draft currently seems to target using the new
> nexthop capability on a per-advertisement level.  Considering that
> draft-idr-bgp-nh-cost adds a new SAFI to convey information about
> nexthops, it seems natural to tranposrt the capability information in
> that place?
>
> (That would also remove the question of what behaviour should be when
> you get different advertisements with the same nexthop, but with a
> different nexthop capability attribute.)
>
>
> -David
>