Re: Question for TI-LFA

Yasuhiro Ohara <yasu1976@gmail.com> Sun, 31 March 2024 01:57 UTC

Return-Path: <yasu1976@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2573C14F605 for <rtgwg@ietfa.amsl.com>; Sat, 30 Mar 2024 18:57:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.844
X-Spam-Level:
X-Spam-Status: No, score=-1.844 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, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 JsYyEz3I_SG8 for <rtgwg@ietfa.amsl.com>; Sat, 30 Mar 2024 18:57:30 -0700 (PDT)
Received: from mail-qv1-xf32.google.com (mail-qv1-xf32.google.com [IPv6:2607:f8b0:4864:20::f32]) (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 9A142C14F5FA for <rtgwg@ietf.org>; Sat, 30 Mar 2024 18:57:30 -0700 (PDT)
Received: by mail-qv1-xf32.google.com with SMTP id 6a1803df08f44-6969388c36fso17737316d6.1 for <rtgwg@ietf.org>; Sat, 30 Mar 2024 18:57:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1711850249; x=1712455049; darn=ietf.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=12kUjl9DKqFWSyIrpOcy5vqGqEMWtPfvUj5tMgE0PgI=; b=d/sjLnFs/yvAXn9gFEDENTX11gRObnYY4ObobjYUlZvpOJk1D9T3msH9EyytRtUbBL ZIDGbkrjMu8wcqkBI9lrhvuoIR6bgDcQty9zztnNOErmOjvO75DQlwFd0W5sFk3n36DI xeIoCasq2genB66Zh0lhxbC7F+ETtti7a9GsVl39N9G2CuvS3L1yCejVuCV6HHxpHGS7 MKYoQF8ThjFFJaFGpSpxv9GBc1SwWg6MykxLnc10Y5tzXqVPLed/7MVwjISjbf1R7SdY K4xrQhb2yyUj82ayO44nYvJUnFkN2WiWWtjJzaH5zx+xYuwjIN/il2rt22Oig+xLXkCU KZ6w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711850249; x=1712455049; h=content-transfer-encoding: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=12kUjl9DKqFWSyIrpOcy5vqGqEMWtPfvUj5tMgE0PgI=; b=X0GUiSH5yywP3o65x5UtMWEj6FurPXm5NdxgiQpLVGHYBnB4aHvNfIFrfnGTwd1NiS uR1rVjVmHbLIdcdTEz2y0VAN5dh5PCjHIor3UPSH2N69dSnRMfnV3G9ve2d8t/+4yenh iJbWZN1/R0Xhwlq+Y+Y2Yk49Xle7WN1MC8XQkrftMR2++i7854u/+YFFXs7/x4NyEzCB UExDpRX9XN2Bzom2RJ5ABcJv0nJkiUtA5fYGLVSF68RYmTkLnvjehbdokZ8YrKHBMxHG n0OZSOuboaAwejDoZimfPBGU8cPhD78i7QnXQVV01UTtjWSU6oSu9LaAxVVsFSKCDGXf SArw==
X-Gm-Message-State: AOJu0YyW7u77T+w28Po9XLm/qWPg5RzWphZmT2b0PSZBAtHOITK3809B fIJwqKqIwq+J5PUfj86uq7NKmaXNFYAMXY0HBU+H31qHBiHHnZ/NxEUghLUZHEA6ntqWQPsYMXy khUXgXVh4J8grihe1teNT+oCx7Hv7CRY2
X-Google-Smtp-Source: AGHT+IExF3EjJNWS23Q4ckZpVqrYOQznXLDo5jKU8/e2vrYfGM3rnr7wUI88u1tiXxgbmdyloAKY3znlKpvDiAZ/woo=
X-Received: by 2002:ad4:4111:0:b0:696:aeac:48ca with SMTP id i17-20020ad44111000000b00696aeac48camr6863149qvp.48.1711850249535; Sat, 30 Mar 2024 18:57:29 -0700 (PDT)
MIME-Version: 1.0
References: <CAJO98mNUQ1JcHkbTPZmi_4Pq0G49ta366cmbsSxs4CHHHe=KWw@mail.gmail.com> <DU0PR07MB95902158C073408479AB8CC5E23B2@DU0PR07MB9590.eurprd07.prod.outlook.com>
In-Reply-To: <DU0PR07MB95902158C073408479AB8CC5E23B2@DU0PR07MB9590.eurprd07.prod.outlook.com>
From: Yasuhiro Ohara <yasu1976@gmail.com>
Date: Sun, 31 Mar 2024 10:57:18 +0900
Message-ID: <CAJO98mOZcQhFG7Oz=p2N=r2DhNjhkxCqzVqcUmUXS4Tn5q+yiQ@mail.gmail.com>
Subject: Re: Question for TI-LFA
To: "Dirk Goethals (Nokia)" <dirk.goethals@nokia.com>
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/KGCFwdTAjka6-rT0zFmJdF8YtD0>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 31 Mar 2024 01:57:34 -0000

Thank you.

The example makes sense if it were the extended P-space, P'().

We'd better bear in mind that the use of P'() increases computational
complexity.
As an implementation developer, computation of an SPT (the routes to
every destination in the intra-net)
for all neighbors also requires some extra caution (such as upper
bounds for memory).

But yes, the I-D would be fine if the error in the example is fixed.
Please add some text if the extended P-space should be used
for the correct results in the example.

Best regards,
Yasu

2024年3月29日(金) 1:03 Dirk Goethals (Nokia) <dirk.goethals@nokia.com>:
>
> I think the P space calculation in Section 6 is the extended P-space
> as defined in RFC7490, i.e. path to R1 is no longer ECMP once N2
> is selected as next hop.
> See also  ecmp path to node C In figure 1 of that RFC7490.
> Dirk
> ________________________________
> Van: rtgwg <rtgwg-bounces@ietf.org> namens Yasuhiro Ohara <yasu1976@gmail.com>
> Verzonden: zondag 24 maart 2024 6:54
> Aan: rtgwg@ietf.org <rtgwg@ietf.org>
> CC: Yasuhiro Ohara <yasu1976@gmail.com>
> Onderwerp: Question for TI-LFA
>
> [Some people who received this message don't often get email from yasu1976@gmail.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> CAUTION: This is an external email. Please be very careful when clicking links or opening attachments. See the URL nok.it/ext for additional information.
>
>
>
> Hi,
>
> I have a question for the draft-ietf-rtgwg-segment-routing-ti-lfa-13.
> I wonder if it needs a fix.
>
> In the I-D, the Section 3. "Terminology" defines
> the P-space as the following.
>
> > The P-space P(R,X) of a router R with regard to a resource X (e.g. a
> > link S-F, a node F, or a SRLG) is the set of routers reachable from R
> > using the pre-convergence shortest paths without any of those paths
> > (including equal-cost path splits) transiting through X.
>
> The Figure 1 (Section 6) in the same I-D,
> the resulting P(S, N1) includes R1,
> but one of the S's ECMPs to R1 includes N1.
> S's ECMPs to R1: [(S-N1-R1), (S-N2-R1)].
> How can we include R1 in the P(S,N1),
> given the P-space definition?
>
> My current guess is that P-space definition needs additional
> explanation on the ECMP part.
> My guess for the correct definition is:
>         A router (say 'U') can be included in the P(R,X)
>         as long as the R can exclude all the nexthops
>         possibly transiting through X.
>
> I think we are implicitly assuming that S can eliminate sending
> through N1 to R1 by itself, and so the R1 can be include in P(S,N1)
> in Section 6.
>
> As a search for other problematic example,
> we can manipulate(generate artificially)
> the topology such that S's ECMPs to R1 consist of:
> S-X-A-R1
> S-B-R1
> S-C-X-R1
> S-D-E-R1
> S-D-X-R1
>
> In this case, R1 can be included only if S can eliminate the
> X, C, D from the nexthops to R1.
> S-X-A-R1 (NG, easily avoidable)
> S-B-R1 (OK)
> S-C-X-R1 (NG, avoidable after path calculation)
> S-D-E-R1 (NG, hard to avoid unless we compute ECMP from D to R1)
> S-D-X-R1 (NG, hard to avoid unless we compute ECMP from D to R1)
>
> The current definition seems to worry about inclusion of D nexthop case,
> and contradicts with the raised example which includes B nexthop case.
>
> By the way, I think Q-space definition is correct as is
> in the current version.
>
> Best regards,
> Yasu
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg