Re: [Lsvr] [Idr] Why L2 liveness needed for BGP-SPF
Robert Raszuk <robert@raszuk.net> Sun, 22 July 2018 14:55 UTC
Return-Path: <rraszuk@gmail.com>
X-Original-To: lsvr@ietfa.amsl.com
Delivered-To: lsvr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E2B1130E42; Sun, 22 Jul 2018 07:55:39 -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 gkbKoLDUa8TK; Sun, 22 Jul 2018 07:55:37 -0700 (PDT)
Received: from mail-pg1-x541.google.com (mail-pg1-x541.google.com [IPv6:2607:f8b0:4864:20::541]) (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 251F0126CC7; Sun, 22 Jul 2018 07:55:37 -0700 (PDT)
Received: by mail-pg1-x541.google.com with SMTP id s7-v6so6968408pgv.3; Sun, 22 Jul 2018 07:55:37 -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=HYpdab3IGIGtjADm/5pnYgc7msNU/nB0t0YoBBVrmA0=; b=Eux+SsmQsQV0MiEGaM/8X+qRmQTWD/rchGK6hlb1mjePpQ+D/shLjdNuadJNEZjnmG M7p9s3wk1WGe7C5ovmc8sW3fSSgwltpbaTMNSyYPsZ5Ok3nfBrOsWP1bsRN0JMiW+sz7 3uFclcK+gtp9Av9pduGehbPt4iR24JEsohzfrljS0JRjB89kL/mVEB8nUBUnoKi6o0X9 MBftoLsPiHldic+g6Aot3ZTDgjNvDoFQyjvSTs/amHN4lE/7KaPRUNoWn6ec7+G2+W8W /fxcLGOiddI23wq3K2w1jc2uyPSj1SaifMyQFx9Ba+WEOqeb16o1J7ahJMl+ckxacCze ADLA==
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=HYpdab3IGIGtjADm/5pnYgc7msNU/nB0t0YoBBVrmA0=; b=pfTS6fcwUqVjBe3Se17Vtx+B08DdXRUdweKWWrZ3r02gH864zvgoD0yC/95qcjk+iw 8KK1mC5ePkxu/3h/3d9C0TDRpM37kWRKpOqxuM2Yi62QKrTL68yE1ALYVl3e/pEKZSRR kPL2W+XRiX46olujqE3wQQGvlqWwHDRWZuvI7UJUe/AakL2Fdy/P2n1pARN3j29dtf6m wz3caUeYyRuK5mYXCc5TY6MPLUIMn/ayKRP20RCsftcztNRqtK8gQxsNq+mcPpT+CDHV MVwkTBXhGPEhZIpnSYSvTsom84m2vGqjGI1Q4Ft6LPRuxyoqtC15ZJu7AC+zv5UCTS9m 1SOw==
X-Gm-Message-State: AOUpUlGOcmf5+a7zp04KGl3MuMrsJqW62Jjk/p5qAlHh3yVmKlkyzDt6 VBlLj8suUI+JxWLAZqMEQdnNCyRhsvSyErCPnMFWbMwU
X-Google-Smtp-Source: AAOMgpdjALAlEmTmvsrtwu9y3SWGcVQYADxJWcVKiRabqBA/uCs+xwSsv6PxUylN0q1j8tc1GfgvnBqGGqttsrgOU2s=
X-Received: by 2002:a65:4107:: with SMTP id w7-v6mr8581348pgp.302.1532271336445; Sun, 22 Jul 2018 07:55:36 -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 07:55:35 -0700 (PDT)
In-Reply-To: <CA+RyBmXvE2gJVuXBB31jj8+CDRB8zBq+97fhhgzpJbNAVDbmZg@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>
From: Robert Raszuk <robert@raszuk.net>
Date: Sun, 22 Jul 2018 16:55:35 +0200
X-Google-Sender-Auth: Y4zhQZCzB2SPr_FBQXNs5Q3wLaw
Message-ID: <CA+b+ERnvaTMw5QrjYPq0PJtUMdcOXatmuT1041zVZF9uJVfMLg@mail.gmail.com>
To: Greg Mirsky <gregimirsky@gmail.com>
Cc: Victor Kuarsingh <victor@jvknet.com>, Randy Bush <randy@psg.com>, idr wg <idr@ietf.org>, "Jakob Heitz (jheitz)" <jheitz@cisco.com>, "Lsvr@ietf.org" <Lsvr@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b55d4d057197b8ef"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsvr/qE7YEzznOObb9mEMvRz8My63GXw>
Subject: Re: [Lsvr] [Idr] Why L2 liveness needed for BGP-SPF
X-BeenThere: lsvr@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Link State Vector Routing <lsvr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsvr>, <mailto:lsvr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsvr/>
List-Post: <mailto:lsvr@ietf.org>
List-Help: <mailto:lsvr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsvr>, <mailto:lsvr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jul 2018 14:55:40 -0000
Is IETF a new forum for Ethernet specification ? I was always under slight impression that this is rather IEEE Ethernet WG ... http://www.ieee802.org/3/ On Sun, Jul 22, 2018 at 4:43 PM, Greg Mirsky <gregimirsky@gmail.com> wrote: > Dear All, > hope an easy question you'll help me with. Liveness as path continuity > check or as connectivity verification. > > Regards, > Greg > > On Sun, Jul 22, 2018, 09:09 Victor Kuarsingh <victor@jvknet.com> wrote: > >> >> >> On Sun, Jul 22, 2018 at 7:35 AM Randy Bush <randy@psg.com> wrote: >> >>> > L2 can be Ethernet, Token Ring, ATM, Frame Relay, PPP, SLIP, MTP2 and >>> > others that may be invented in the future. >>> >>> it could be tin cans and a string. but out here in the internet, it's >>> ethernet. there are tiny vestiges of sonet, which you seem to have >>> forgotten; but no one is gonna run bgp-spf over them. it is a mono- >>> culture; ethernet won. >> >> >>> >> At this point, the current applicability for BGP-SPF is Data Center / >> CLOS networks as described in the applicability document ( >> https://tools.ietf.org/html/draft-keyupate-lsvr-applicability-02) >> >> There is some texts around future use of this protocol (SP backbone), but >> again not the focus of our current work. >> >> That said, as noted by Randy, these topologies are currently Ethernet (at >> least in the cases we are aware of). >> >> Regards, >> >> Victor K >> >> >> >> >>> randy >>> >>> _______________________________________________ >>> Idr mailing list >>> Idr@ietf.org >>> https://www.ietf.org/mailman/listinfo/idr >>> >> _______________________________________________ >> Lsvr mailing list >> Lsvr@ietf.org >> https://www.ietf.org/mailman/listinfo/lsvr >> > > _______________________________________________ > Lsvr mailing list > Lsvr@ietf.org > https://www.ietf.org/mailman/listinfo/lsvr > >
- [Lsvr] Why L2 liveness needed for BGP-SPF =?UTF-8?B?5b6Q5bCP6JmOKOS5ieWFiCk=?=
- Re: [Lsvr] [Idr] Why L2 liveness needed for BGP-S… Jakob Heitz (jheitz)
- Re: [Lsvr] [Idr] Why L2 liveness needed for BGP-S… =?UTF-8?B?5b6Q5bCP6JmOKOS5ieWFiCk=?=
- Re: [Lsvr] [Idr] Why L2 liveness needed for BGP-S… Randy Bush
- Re: [Lsvr] [Idr] Why L2 liveness needed for BGP-S… Victor Kuarsingh
- Re: [Lsvr] [Idr] Why L2 liveness needed for BGP-S… Greg Mirsky
- Re: [Lsvr] [Idr] Why L2 liveness needed for BGP-S… Robert Raszuk
- Re: [Lsvr] [Idr] Why L2 liveness needed for BGP-S… Randy Bush
- Re: [Lsvr] [Idr] Why L2 liveness needed for BGP-S… Greg Mirsky
- Re: [Lsvr] [Idr] Why L2 liveness needed for BGP-S… Robert Raszuk
- Re: [Lsvr] [Idr] Why L2 liveness needed for BGP-S… Greg Mirsky