Re: [Idr] I-D Action: draft-ietf-idr-bgp-fwd-rr-02.txt

Robert Raszuk <robert@raszuk.net> Mon, 18 March 2024 16:11 UTC

Return-Path: <robert@raszuk.net>
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 B46E5C151710 for <idr@ietfa.amsl.com>; Mon, 18 Mar 2024 09:11:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=raszuk.net
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 gXRLM2NjHa2T for <idr@ietfa.amsl.com>; Mon, 18 Mar 2024 09:11:45 -0700 (PDT)
Received: from mail-ed1-x52b.google.com (mail-ed1-x52b.google.com [IPv6:2a00:1450:4864:20::52b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE549C15155A for <idr@ietf.org>; Mon, 18 Mar 2024 09:11:16 -0700 (PDT)
Received: by mail-ed1-x52b.google.com with SMTP id 4fb4d7f45d1cf-568a53d2ce0so5367332a12.0 for <idr@ietf.org>; Mon, 18 Mar 2024 09:11:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; t=1710778274; x=1711383074; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=rt84wV6oQzg5fSlYFDM9OKg4uRBWStUW8WKb4evPNjQ=; b=ZSf4XqICvrRxpy6gE0oYDizI1dMGJVtJTwDOEf4K8bKZpmJc7MG2aagUD5vDjkaDVn 1+023Q1NS0PZT1PV8YZP0mLdcQ837QEbVE3FQpS7MA6SbsJn1Ahc7aRBLfzIePYLvlG/ cbtSEf7Vp6p5uMIbZMhYFo7Q5p91A5suDWJioS6vade1A8Ix1IxhTbENMEhp5m1MtcH7 x84RChjrumxtrokfqsvSOtZup1HrojFOMrEkgMc4qYUn3e15JC50MKrUjAFaZxLEN6ce bJRiFGIX5Z9j0lSJY+DFZ2nqL1c8DhDTJpHKP67uzpHM6DdvxGkXH7IZePjIOGZ+akc/ uJjw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710778274; x=1711383074; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=rt84wV6oQzg5fSlYFDM9OKg4uRBWStUW8WKb4evPNjQ=; b=ikDhZ49h+5YXUnvzrw6U9PegodfJagNdTrjxK2TpKw9Cwln7qz/18VIdL15IdKHg5A viWc+CXT5fQ0PFK+HGl0HCTwBFy/Msd4wxvVlJSxsd8ecrWNfrzLaSWqu/YBESPmtFBP 98db/j4u5ZyI9ybZg0sE9xX+a8uIrdkvM8/8HGmgyxYleNGQAtu6MgKYn+uWZsIwf1jZ AIc0LSLsgGZZbjgrzqX1Vm3kUMWwYGYwclQSZsU02Myx1JJtHBZk7pUySv3lZeMD8TkA pGafI6sz0C4FUGJQgYB/Bb7PpBYaDviirzit/BJCjmcIhSSRu9hsC/n9ni2L3HWLw5tC kGAg==
X-Forwarded-Encrypted: i=1; AJvYcCUIfaUxaCIArptm8tcGkzFaynMTSPsR7Js/wb0SiEhA/QISWgr9OZ8AMAOtNdwKSJjGNPAYXZhuBcM0r38=
X-Gm-Message-State: AOJu0YzDynoKqIzRrWDiQdRvLzXKmiOZFM2c/MXrzOGcyWa/kPewYfmN tbXo769b7/gsyUn5L/Z4NqRetnxqOyAoKC7pF1Cf3yAGIYGW1uO9UySz9zTfIy12RP9Vf8fp64J u0ZJa/deA1Tl1aXHJoliJoK8DQs04URZY81sJHQ==
X-Google-Smtp-Source: AGHT+IGWcABl1iLCDXt3lPd4f/9QeNCS9YopqtHGQw5DLV5kJE1JnXGIOc3567eyqUgk4kSaHxb4jURQAWTkMYkX5ps=
X-Received: by 2002:a05:6402:1f4b:b0:568:b484:8a04 with SMTP id 11-20020a0564021f4b00b00568b4848a04mr7285961edz.35.1710778274220; Mon, 18 Mar 2024 09:11:14 -0700 (PDT)
MIME-Version: 1.0
References: <171065415177.59997.7631576612994148063@ietfa.amsl.com> <CAOj+MMEsp_UfuiHdc4U_Bv5o7xsYYK_RryusUZ88u+SH9xifSA@mail.gmail.com> <SJ0PR05MB86322B34D635E7F221C04C0FA22D2@SJ0PR05MB8632.namprd05.prod.outlook.com> <CAEfhRrxDVi_Yw2wtTWiGzjw4pQ-8TF-48UCY5AUxMpKdrbexZw@mail.gmail.com> <CAOj+MMHNAz741WP9Pf2UCSOQRj6YepFh=Q4tzedmwBCm6e289g@mail.gmail.com> <CAEfhRryMW9nyWfnDQdi+R5g-nypg5ppwFy_Gdf71pRMFmZysHA@mail.gmail.com> <CAOj+MMF2-oqZ29hSBgaO+gzYXXyvCRgJ0m-zW2K7CWattCpgrQ@mail.gmail.com> <CAEfhRrw=acXDgVtzUEhqxZcOPYbJwT0Ha36k-ADgZaiy863erg@mail.gmail.com> <CAOj+MMGnup=Qg7+XiyXtCJe0a2csmdFVVLtJj_TmoA4yysbghw@mail.gmail.com> <CAEfhRrxFBay_pctO32G9S9kL8Ry_Y2Cx+rQEknN3D6qU9XG2+Q@mail.gmail.com> <CAOj+MMFDUtDzSVWRyH6U2arCUWsn-hNTA-+_RXxan_hPLS=AAQ@mail.gmail.com> <CAEfhRrwxXgTNR0hWd96WnAi_wOvUqCsQkN=5bvbqycgxqMCkeg@mail.gmail.com> <CAOj+MMEpvT4f3W238RPr2bULuwyqTn0jwg6xRf01dLYp6H_6hg@mail.gmail.com> <CAEfhRrz+6ZP6DMgUj-MOwkGQDwj_Z-q0NUAo6VR2-V9fjk7KAw@mail.gmail.com>
In-Reply-To: <CAEfhRrz+6ZP6DMgUj-MOwkGQDwj_Z-q0NUAo6VR2-V9fjk7KAw@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Mon, 18 Mar 2024 17:11:03 +0100
Message-ID: <CAOj+MMFmY4LrUc=-Nb+rgOQywcTAQ3JZKA071hsHc9SEo=dM9g@mail.gmail.com>
To: Igor Malyushkin <gmalyushkin@gmail.com>
Cc: Kaliraj Vairavakkalai <kaliraj=40juniper.net@dmarc.ietf.org>, "idr@ietf. org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000053249d0613f19b49"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/c2i5SnS1RYza-75tut1w7EqM6oo>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-bgp-fwd-rr-02.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 18 Mar 2024 16:11:49 -0000

Hi Igor,


> This is crucial to my point. The local "repair" action is really not a
>> repair. When you loose your sessions on primary ABR1 to region-2, or you
>> get withdraws etc ...) you need to re-run local (on said ABR1) best path as
>> there is no other trigger to simply activate bulk switchover in data plane
>> to suddenly go to ABR2. This is the key.
>>
> [IM] I see at least three such triggers.
>

Ahhh see the crux of the matter is that none of those listed below is
applicable to support bulk data plane switchover to back ABR :(

An outgoing Region2-faced interface failure.
>

When you loose interface and ABR is (and should be) connected via at least
two interfaces to each region your IBGP sessions are intact.

And even if this is single interface and you invent new harmful knob to
invalidate IBGP sessions when interface X goes down (this is common
practice on directly connected EBGP sessions only) you still have zoo of
prefixes received over those IBGP sessions and each may have been
advertised with different label.

So you still need to run full best path and pick new (now backup path) on a
per prefix basis and install one by one in RIB/FIB/LFIB.


> An IGP event in Region 2 with a remote ASBR failure.
>

Ok you can invalidate a remote next hop. Sure. But that means as you have
observed already that each route may be incoming with different label so
you need prefix by prefix pick alternative label and install it in
RIB/FIB/LFIB locally.



> An RSVP event of underlying Region 2's LSP failure.
>

Whow ... now we see a soft state protocol through into this mix.  And when
an RSVP-TE LSP to remote next hop in region-2 goes down you want to
consider this a trigger to invalidate given next hop ? Ok but we are back
to #2 above. Still one by one ...


> All of them describe some group of prefixes and can influence the
> switchover to their backups.
>

That would be true for vanilla IPv4/\Pv6 SAFI 1. Not for SAFI 4 or SAFI 76.

Cheers,
R.