IETF Logo Mail Archive

Re: BFD chair response to presentation on draft-mirmin-bfd-extended

Robert Raszuk <robert@raszuk.net> Fri, 22 November 2019 22:08 UTC

Return-Path: <robert@raszuk.net>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3443E120137 for <rtg-bfd@ietfa.amsl.com>; Fri, 22 Nov 2019 14:08:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=raszuk.net
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 OxsEZAJsp4i6 for <rtg-bfd@ietfa.amsl.com>; Fri, 22 Nov 2019 14:07:59 -0800 (PST)
Received: from mail-qt1-x829.google.com (mail-qt1-x829.google.com [IPv6:2607:f8b0:4864:20::829]) (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 8F38B12013B for <rtg-bfd@ietf.org>; Fri, 22 Nov 2019 14:07:59 -0800 (PST)
Received: by mail-qt1-x829.google.com with SMTP id y10so9590590qto.3 for <rtg-bfd@ietf.org>; Fri, 22 Nov 2019 14:07:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=eNwuriUPpIuLZGdN18SgZNmsQvbQub45CMLE4si87xM=; b=Onw9dyhi7i1X1Cqed8mnOPEJHWGg02DT/WzEHJaUyE33HOEBAycrm0ZAY/HndXjWpX VeXClTgt5aWsOlhgHj7LwkJR862A28jgaJFCOZKIRFDiUFVSm/KW6D1V4jzEmgvy4tOn WWZJVqwGVtBwaWMVeCByd8nSQhOGwYg+QjyVUusAeX9+9T0tpUuy3TaQoUtgSclkEsd/ MhD5td044679qDz/i65Wbg82SWkD5Tk2ZnIn5Cm8hxdw1QKBR26MqEQdGJrFC6eSRCGT i5L3W/ckehQ+WeUCvIuv2U8EDrmxzfw5PLWqfSY6UU5lJoqPbTd6N1k6QLL+uCKHC5mO YU+w==
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=eNwuriUPpIuLZGdN18SgZNmsQvbQub45CMLE4si87xM=; b=DwEnUhnuaiY02DSokwbfUAv1KuhnKweb/Iy7jvEuuC/P3EGTOmTi2PjT2ASngNNxGG P7etusf5s65y8CTIPkFzncJfdGHj0lRl9erng5/sys9hE2jNB4Ftj7Ykt57J4my4cfSy QIRjsVbZ+Z5x3Opkc5BritOcQHEVvCJoWeeBg+i0TEANhWLG/XTGnATixHY/wKj+xrUh 7wN+YsAF/tfnA+3vBTOz8kpgiyxlxu8esUn/EDsX46QgLNqwZe6ztoHTk6kFlSE+Vpm+ /8T4yAKsxJ0tuGw5ycm7cFk7iNfT+W/jRW1k3FOcAk3ShUaq7hIATOPSvnhM9esoIjE1 RsWQ==
X-Gm-Message-State: APjAAAUPggHPNLoiz5g76IslcfJsM2mammhHJNfKCseRqWTSlofauZy6 gTZ7/p3o0Zc5HYkS9L8DHH2BF4E8VcM9pUX6hl480g==
X-Google-Smtp-Source: APXvYqzIVncXtEZNtxe7pFOxwICF40ngu5E5dC8Qtx7/ij665Z9mqbEYlyLapP5HDCWD1pyhIP5X6SJLH07qJJskgEs=
X-Received: by 2002:ac8:1017:: with SMTP id z23mr5415233qti.94.1574460478545; Fri, 22 Nov 2019 14:07:58 -0800 (PST)
MIME-Version: 1.0
References: <20191122025255.GW21134@pfrc.org> <MWHPR11MB1341FAFAD5169AC6E8843D20C1490@MWHPR11MB1341.namprd11.prod.outlook.com> <5013C7DE-81C0-44B6-B15B-8701527358E9@juniper.net>
In-Reply-To: <5013C7DE-81C0-44B6-B15B-8701527358E9@juniper.net>
From: Robert Raszuk <robert@raszuk.net>
Date: Fri, 22 Nov 2019 23:07:50 +0100
Message-ID: <CAOj+MMHWaxMjFMbbxgZbh4n7cgeEoMSBE_5ok=RR4kfxTVSZJA@mail.gmail.com>
Subject: Re: BFD chair response to presentation on draft-mirmin-bfd-extended
To: Dave Katz <dkatz=40juniper.net@dmarc.ietf.org>
Cc: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000089754c0597f6a521"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/BhV8WwC5dfptSCI70E5nqDOTIcw>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Nov 2019 22:08:01 -0000

Hi Dave,

I’ve been quoted in the past that BGP, used as a transport, is “TCP with
> beard.”  It would have been trivial to split out the minimal semantics the
> actual BGP protocol brought to the table.
>

BGP just because "it is there already" now transports link state database
and one SAFI of it is being called a link state protocol. Just because it
is there regardless of its p2mp nature is also being used for p2p
configuration push including ACLs.

It seems that BFD is heading the same way - again on the very same basis -
"it is there" - so let's use it.


> Part of the issue is that the IETF hasn’t bothered to put together a set
> of generic transports to build things like this on top of.


Spot on !

Except IETF does not ship router's code :). Vendors do.  And till we see a
generic transport perhaps ZeroMQ message bus like OpenR uses being
shipped across at least few vendors existing protocols will get abused more
and more ...

Best,
R.

v2.23.0 | Report a Bug | By Email