Re: [Idr] [Lsvr] Why L2 liveness needed for BGP-SPF

Robert Raszuk <robert@raszuk.net> Sun, 22 July 2018 22:49 UTC

Return-Path: <rraszuk@gmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6458F1277CC; Sun, 22 Jul 2018 15:49:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 dxhb7hn858t2; Sun, 22 Jul 2018 15:49:01 -0700 (PDT)
Received: from mail-pf1-x430.google.com (mail-pf1-x430.google.com [IPv6:2607:f8b0:4864:20::430]) (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 CA3C912426A; Sun, 22 Jul 2018 15:49:01 -0700 (PDT)
Received: by mail-pf1-x430.google.com with SMTP id b17-v6so532434pfi.0; Sun, 22 Jul 2018 15:49:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=pTm95djLm/6tGKOxlSoek6njaI7p770T7JT9dDgyk3Q=; b=Y7ogB0Jjy6vAYehJVnIHkstfWuSbjqdI8f3KUuLtK6F3ZfCH1P7lK2s5+k43QAY328 12M2iHnAdnT8id1nLUlz8HpLt2lG6jvMB1658WtQPkdvnEWfGBV4169cUjcaJMiBVXP/ O5++l19HIp870JYiKR17xsNz3iQPn73XhEGFYQ2QymT7cWWAH8SmPFli2Nu1vQTNIqp/ v6dwA3yrHOhEz7y54owd7EyP03bhrkPvbUyR64KefOmLiq/UkIQE1ndG+I/FcUcWyivR tM/4Vb6tb/J+BpwTwEHOnucxgZDC+Zljgwmu8EZmYEgAxwE8/+phRs8KzHbCaug2oco8 rxlA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=pTm95djLm/6tGKOxlSoek6njaI7p770T7JT9dDgyk3Q=; b=tsYaydYTjqhfTsADz9XFfdXiQCbN0nqNMiiZKMQB4B4geq6mg2d3XZlIAIRhyBBHuJ 6pfyGFciftYyP2yieRyUbYCuRFpYJvDc3qD73F1Q2gSsESO7kfTZJkW4IACLk4uIoBPt qr+dNJybBRyEUggLsOZtrF6HjrFGQaK1/7WohCjTE0Njp2AZ/ujiU2zAonyDyWPUhLCp RDmlRT5SbETRF+0geR1Ca2UMuj9nAT3HPJSyJl+6lactMX6Ahuja6oxAyrXxI26d6kLr B1/mXaoNlZQm6EaZeGYAm1wGQ5cS2Z5Ky5+aNadL2QjulBcoYOvVKFn7Vx8s8idpXXlz VtvA==
X-Gm-Message-State: AOUpUlHSC5QuGDuYRiNOyzpnopvPO0yEmthE6P9xdeLIpKbv6ihdpXuX CPUQufdnntd1HqiPXL2h29K0LA9pkJQIwOuy3XU=
X-Google-Smtp-Source: AAOMgpedAvPTjfRDQMCY8EeFyhFrtm2xOMM3azysPiQhntmY636jGWblOKsZOOMBStz+H7LWDcVzkjEcQAKtvBBMGFU=
X-Received: by 2002:a65:5641:: with SMTP id m1-v6mr10187760pgs.246.1532299740882; Sun, 22 Jul 2018 15:49:00 -0700 (PDT)
MIME-Version: 1.0
Sender: rraszuk@gmail.com
Received: by 2002:a17:90a:d396:0:0:0:0 with HTTP; Sun, 22 Jul 2018 15:49:00 -0700 (PDT)
In-Reply-To: <CA+RyBmV9QzaqbLZ=gbtaQ3+bpsH+zSfmxOvPkczJYCXas9HjEA@mail.gmail.com>
References: <fb35cb79-881d-4ca2-8a0b-738886d28b8f.xiaohu.xxh@alibaba-inc.com> <bd5ff63067a8446ca8e2267c891933ad@XCH-ALN-014.cisco.com> <m2muujec6q.wl-randy@psg.com> <CAJc3aaNCM0XCDEVmkKxxvKxXdMdKsB+YDWLM3qGo83x271D-ow@mail.gmail.com> <CA+RyBmXvE2gJVuXBB31jj8+CDRB8zBq+97fhhgzpJbNAVDbmZg@mail.gmail.com> <m2k1pne0pp.wl-randy@psg.com> <CA+RyBmV9QzaqbLZ=gbtaQ3+bpsH+zSfmxOvPkczJYCXas9HjEA@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Mon, 23 Jul 2018 00:49:00 +0200
X-Google-Sender-Auth: 12rARLyyi3M923gklqMNYQCLW_A
Message-ID: <CA+b+ERmfSmjJJVLNs8HnG34Y3q6PJVLntvx+hb4fCpWXgWsr9Q@mail.gmail.com>
To: Greg Mirsky <gregimirsky@gmail.com>
Cc: Randy Bush <randy@psg.com>, idr wg <idr@ietf.org>, "Lsvr@ietf.org" <Lsvr@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000beab9c05719e550c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/pdgNRMRpB2kqST6E57v1wjCDvN0>
Subject: Re: [Idr] [Lsvr] Why L2 liveness needed for BGP-SPF
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.27
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: <https://mailarchive.ietf.org/arch/browse/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: Sun, 22 Jul 2018 22:49:05 -0000

Hey Greg,

I don't think this is about liveness or connectivity verification.

It is all about physical topology discovery at L2 without one of two
popular link state protocol which today do the job just fine. Whoever is
asking for it is however correct that we don't have a protocol independent
way of discovering Ethernet topologies. If it is a feature or a drawback
remains to be seen.

I was observing identical struggle in OF .. as expected it failed pretty
badly !

Just to note L3 BGP Hellos to discover topology is terrible idea even worse
then LLDP one.

Thx,
R.


On Sun, Jul 22, 2018 at 7:16 PM, Greg Mirsky <gregimirsky@gmail.com> wrote:

> Hi Randy,
> thank you for the quick response to my question. BFD monitors path
> continuity at the layer 3, though there's BFD over LAG that picks into the
> layer 2. One cannot differentiate between liveness of the remote system and
> availability of the path between two systems. If we are not interested
> whether packets from the particular source and only that source received,
> then we use path continuity check protocol. BFD is the example of the CC
> while CFM, Layer 2, is the connectivity verification.
>
> Regards,
> Greg
>
> On Sun, Jul 22, 2018, 10:42 Randy Bush <randy@psg.com> wrote:
>
>> > hope an easy question you'll help me with. Liveness as path continuity
>> > check or as connectivity verification.
>>
>> layer 2 link liveness.  we have other tools above layer 2; e.g. bfd.
>>
>> randy
>>
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>
>