Re: [Last-Call] Re: Tsvart telechat review of draft-ietf-bfd-unaffiliated-echo-12

Erik Auerswald <auerswal@unix-ag.uni-kl.de> Fri, 18 October 2024 07:03 UTC

Return-Path: <auerswal@unix-ag.uni-kl.de>
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 CEAE7C169405; Fri, 18 Oct 2024 00:03:23 -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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7pfDauu_g6on; Fri, 18 Oct 2024 00:03:23 -0700 (PDT)
Received: from mailgw1.uni-kl.de (mailgw1.uni-kl.de [IPv6:2001:638:208:120::220]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1218C1516F8; Fri, 18 Oct 2024 00:03:21 -0700 (PDT)
Received: from sushi.unix-ag.uni-kl.de (sushi.unix-ag.uni-kl.de [IPv6:2001:638:208:ef34:0:ff:fe00:65]) by mailgw1.uni-kl.de (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id 49I73Hon161002 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 18 Oct 2024 09:03:17 +0200
Received: from sushi.unix-ag.uni-kl.de (ip6-localhost [IPv6:::1]) by sushi.unix-ag.uni-kl.de (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id 49I73Gv7032726 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 18 Oct 2024 09:03:16 +0200
Received: (from auerswal@localhost) by sushi.unix-ag.uni-kl.de (8.14.4/8.14.4/Submit) id 49I73Fwn032725; Fri, 18 Oct 2024 09:03:15 +0200
Date: Fri, 18 Oct 2024 09:03:15 +0200
From: Erik Auerswald <auerswal@unix-ag.uni-kl.de>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [Last-Call] Re: Tsvart telechat review of draft-ietf-bfd-unaffiliated-echo-12
Message-ID: <20241018070315.GA32215@unix-ag.uni-kl.de>
References: <172900211105.1006979.13185411143316403177@dt-datatracker-78dc5ccf94-w8wgc> <20241015204357.GA20184@unix-ag.uni-kl.de> <A1ABD509-5033-450D-BDEA-997A17E5B029@trammell.ch> <0C014316-CA00-4E4B-9DF2-98E2D057BD0D@pfrc.org> <CA+RyBmU0s=hj9tsFrWtx=pPqOKJe_p1k2r4vq0Un-tfY9gGo8g@mail.gmail.com> <D9F420E8-9C41-4EBB-B604-703D23BAD063@pfrc.org> <02b301db20cb$6c0fdb30$442f9190$@olddog.co.uk> <AFF12577-4DE4-4938-B11D-AC94662BCA25@pfrc.org> <2fd79283-5847-4aae-80e0-8396fcd1457a@cs.tcd.ie> <20241017211114.GA24478@unix-ag.uni-kl.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20241017211114.GA24478@unix-ag.uni-kl.de>
Author: Erik Auerswald <auerswal@unix-ag.uni-kl.de>
Message-ID-Hash: MIRPPXY6DRHV4RDPTNR6QSADTJQVSMBV
X-Message-ID-Hash: MIRPPXY6DRHV4RDPTNR6QSADTJQVSMBV
X-MailFrom: auerswal@unix-ag.uni-kl.de
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-rtg-bfd.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "Brian Trammell (IETF)" <ietf@trammell.ch>, tsv-art@ietf.org, draft-ietf-bfd-unaffiliated-echo.all@ietf.org, last-call@ietf.org, rtg-bfd@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection" <rtg-bfd.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/d96SdiasAQSnK4MqnHLCAbVd6H0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Owner: <mailto:rtg-bfd-owner@ietf.org>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Subscribe: <mailto:rtg-bfd-join@ietf.org>
List-Unsubscribe: <mailto:rtg-bfd-leave@ietf.org>

Hi,

On Thu, Oct 17, 2024 at 11:11:14PM +0200, Erik Auerswald wrote:
> On Thu, Oct 17, 2024 at 09:26:00PM +0100, Stephen Farrell wrote:
> > On 10/17/24 20:46, Jeffrey Haas wrote:
> > 
> > >  It's just doing IP forwarding.
> > 
> > You've said that a few times and I find it a little confusing.
> > 
> > "Just IP forwarding" to me would not include replying to the sender
> > of a BFD echo packet. ICMP yes, but I don't think BFD is a built-in
> > part of an IP stack in general and "just forwarding" would in general
> > be driven by rules wrt. the packet destination and not source.
> 
> That is exactly the point of "BFD Echo": there is no reply.
> 
> One and the same packet is sent out and received back again by the sender.
> Destination based IP forwarding delivers this packet.
> 
> > I wonder what I'm missing?
> 
> The BFD Echo packet is sent with a destination address that belongs to
> the sender.  Thus the first router forwarding this packet actually returns
> it to the sender.  This router does not implement any BFD functionality
> for this, just simple destination based IP forwarding.
> 
> That has always been the principle behind BFD Echo, as described in
> RFC 5880.  This principle is used by draft-ietf-bfd-unaffiliated-echo.
> This principle makes it possible to have "Unaffiliated BFD Echo" in the
> first place.
> 
> I'll try to illustrate this with a drawing:

There is one wrong IP address in the drawing: The router should have
192.0.2.2, not 192.0.2.1.  Please find the corrected version below:

       network 192.0.2.0/30                     network 203.0.113.0/30
                  |                                   |
 +[BFD endpoint]+ v  +----------[IP router]---------+ v
 |IP: 192.0.2.1 x----xIP: 192.0.2.2|IP: 203.0.113.1 x---...Internet...
 +--------------+    +------------------------------+         ^
                                                              |
 (1)  BFD endpoint creates and sends BFD Echo packet          |
                                                              |
         BFD Echo packet                        network 198.51.100.0/24
         Src: 198.51.100.47
         Dst: 192.0.2.1
         TTL: 255
         -----------------> travelling from BFD endpoint to IP router

 (2)  FIB lookup for destination based IP forwarding at router happens

 (3)  IP router decrements TTL and forwards packet towards destination

            BFD Echo packet
            Src: 198.51.100.47
            Dst: 192.0.2.1
            TTL: 254
            <----------------- travelling from IP router to BFD endpoint

 (4)  BFD endpoint receives its own BFD Echo packet

Best regards,
Erik