IETF Logo Mail Archive

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

Victor Kuarsingh <victor@jvknet.com> Sun, 22 July 2018 14:09 UTC

Return-Path: <victor@jvknet.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 81C07130F30 for <idr@ietfa.amsl.com>; Sun, 22 Jul 2018 07:09:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=jvknet-com.20150623.gappssmtp.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 qBBl0cX2-Z_l for <idr@ietfa.amsl.com>; Sun, 22 Jul 2018 07:09:24 -0700 (PDT)
Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::236]) (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 50EB0130E1D for <idr@ietf.org>; Sun, 22 Jul 2018 07:09:24 -0700 (PDT)
Received: by mail-oi0-x236.google.com with SMTP id b15-v6so28927237oib.10 for <idr@ietf.org>; Sun, 22 Jul 2018 07:09:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jvknet-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6ErYiZMfGlTVaWpCWo9z1f3MxY9OwFzWRraNArI/bYs=; b=YsVvy6Z+VHPWAe8aaslRmRvwn+ycElvqNrVVntCV8X9Q4mN3VnBWqKg26/RffByRJE LGdhzDDZuJ+H+0TQOL1HdmIKMnUxoHBjdfgQk/3cGnsFquqn7t5ASOyTOkIBhRJx/3YX Ob17TTywYJqo2MwO94q5+otdxlLO+V0ao2e7mQZVHWylWA1gxPtpfoYEvA7zvOgJuu6+ AG5qsoQ6mMd+X1bXD0MrS2cUVqQy3Lho+Rfj3gnBW+PlmpuXJvDPDfBYwKuYD3ZTol6c ibgV6RyqhbMY03DAWaIzXUw6L3DJK+YZGE1r1tzzjHKa+KOO3IlGzqUcd/RSOw3j9oX6 G/kA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6ErYiZMfGlTVaWpCWo9z1f3MxY9OwFzWRraNArI/bYs=; b=gCjKg849iSKDU5hBFhrWkZTiX+RhVKxhGtEnqWXZpdDCOBXx5fiBAi6lV0zqB6QHcP mvY9skHa3abI7dc4AmsH5dOG9ohgznpQzc4lXXf+FIFALofCrN9U0hgoWbqETF1xOfy3 QG9cHsSIjAZRpyP85cdtMBa0Hr+Mt98gEMeu+SdnBq2xu8XzFvxT20kiJcg1r5s5lWtg QQi+ghQr6oMfUnMd5oyF1esrOgDwzSkKvD+UENQMUmBZYd+d4HeAnjUbsZj54wkzgGpE TqcC1QE8JEGT5hVgU064FK3l+Rm30msAIkMvphvV5Orp8/QNuuBDIrbpbvIQeKd64NWO aBTg==
X-Gm-Message-State: AOUpUlE1HRRzjVEB942fkGkrjEK/MiDXAw+UnMncGP7rPSBJuRy+vlWD 6+dsm2jRItWYsuuv0naGJIifhi/iJt8Ks10bo6rpBg==
X-Google-Smtp-Source: AAOMgpfpC936uf03KbkprTFXtm8sa/MKkC8EYY2MWWlfFC1MJIHJVR4gmVRVZ15c9Y6b74dvWpf5+NuU39QTRDpTTFc=
X-Received: by 2002:aca:6287:: with SMTP id w129-v6mr5672997oib.122.1532268563359; Sun, 22 Jul 2018 07:09:23 -0700 (PDT)
MIME-Version: 1.0
References: <fb35cb79-881d-4ca2-8a0b-738886d28b8f.xiaohu.xxh@alibaba-inc.com> <bd5ff63067a8446ca8e2267c891933ad@XCH-ALN-014.cisco.com> <m2muujec6q.wl-randy@psg.com>
In-Reply-To: <m2muujec6q.wl-randy@psg.com>
From: Victor Kuarsingh <victor@jvknet.com>
Date: Sun, 22 Jul 2018 10:09:12 -0400
Message-ID: <CAJc3aaNCM0XCDEVmkKxxvKxXdMdKsB+YDWLM3qGo83x271D-ow@mail.gmail.com>
To: Randy Bush <randy@psg.com>
Cc: "Jakob Heitz (jheitz)" <jheitz@cisco.com>, "Lsvr@ietf.org" <Lsvr@ietf.org>, "idr@ietf.org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006b7b1d057197136e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/_2IsAudSG5-SpUyVf9fT1Ki-mi4>
Subject: Re: [Idr] 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 14:09:27 -0000

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
>

v2.23.0 | Report a Bug | By Email