Fwd: Question for TI-LFA

Stewart Bryant <stewart.bryant@gmail.com> Thu, 28 March 2024 18:35 UTC

Return-Path: <stewart.bryant@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 75F2CC169431 for <rtgwg@ietfa.amsl.com>; Thu, 28 Mar 2024 11:35:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.095
X-Spam-Level:
X-Spam-Status: No, score=-7.095 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_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 bAskU797KdHJ for <rtgwg@ietfa.amsl.com>; Thu, 28 Mar 2024 11:35:04 -0700 (PDT)
Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [IPv6:2a00:1450:4864:20::631]) (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 943DAC169409 for <rtgwg@ietf.org>; Thu, 28 Mar 2024 11:35:04 -0700 (PDT)
Received: by mail-ej1-x631.google.com with SMTP id a640c23a62f3a-a4702457ccbso177122966b.3 for <rtgwg@ietf.org>; Thu, 28 Mar 2024 11:35:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1711650901; x=1712255701; darn=ietf.org; h=message-id:to:cc:references:date:subject:mime-version:from:from:to :cc:subject:date:message-id:reply-to; bh=Es06xWD29l1UDW78tS2pKVUeAAETuhYE3Gr90yLunSc=; b=HROmQBsaqj8tPOAYnbgNCDjBIRnkC/UB/lfgLyBmp2Qp6N0wxuzaJlMW8cvQQfZ3xw hLZlbEj7FZDuae38jvpJLJY4WDr7l5xitY6BNj7qiwDYDJcuYOu/vLXtwO0s0jjRWSoy vYt2yOnb3YOogL9NeRwyaRIkhqoq/ZiKSP1AZjxgxOpG6ncM6D86PtQaeejYkx8f8Oa4 mcZty7h1IHDq8IMD4F3u6iWl1NGieKnx35EaB/bCFFZvqkFPUiw+8w54nmMVntVlkfoP aFEG9nr+l0yOAkfB0kRfJ/5T3U1ihE11hp19vOWrVAaUpAjgRAZrGxZgPxMtC+F2A/uN FOwQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711650901; x=1712255701; h=message-id:to:cc:references:date:subject:mime-version:from :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Es06xWD29l1UDW78tS2pKVUeAAETuhYE3Gr90yLunSc=; b=DdfosQToVRT+rOQ5gTWCnu5uZi/6xFeMqkR8pSX1cxaunUkMxOZlLuJV0wkW1f6FXJ zxCIbaIfgBVwtcMO0QrjiiHLv4TO8pdod61UIkQvFDGdaRkPmPP4e813xbbcd09SSrLs dzbzrNqyO44zcLE9qjchIkb8v81mR5Wf6uZYBxjUSN+ycQB8D1bQC+tluE3GC5dr4pk2 sBTozygjyy9H9QEMVhF9inbs6+U1Z/hJYg0hgqtYxZoKC8/0TP6H9yPDWvLN75D74KQL 7GlSPATvLkcn4EbH7DJt63WYDXK5BXLy7pq5ZgpbG07wgwSNlUP2fhzroR5qHrkywcTq GW7Q==
X-Gm-Message-State: AOJu0YztLQ3xgPFtSauXmUjAVng+N/SCMQqXmxQ3IdBv/F43nEj00wUe q2TiR1pYrC2rZTrBpNLEHwHZx3PvlWlmpYoDNxWGKZHAHA/aU7wBDmKixoTP
X-Google-Smtp-Source: AGHT+IGSFwxp985d64y6sPW5m2cNKHtrvy2WiY4xLk18ZPOfpoAmo0dY28HQBkE3oO337fr/QlNW8A==
X-Received: by 2002:a17:907:1c90:b0:a4e:2220:f748 with SMTP id nb16-20020a1709071c9000b00a4e2220f748mr72292ejc.40.1711650900325; Thu, 28 Mar 2024 11:35:00 -0700 (PDT)
Received: from smtpclient.apple ([148.252.146.254]) by smtp.gmail.com with ESMTPSA id n12-20020a1709061d0c00b00a4da28f42f1sm1040499ejh.177.2024.03.28.11.34.59 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 28 Mar 2024 11:34:59 -0700 (PDT)
From: Stewart Bryant <stewart.bryant@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_BDB9C826-64F7-4460-8118-5EC2DC7CAABE"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
Subject: Fwd: Question for TI-LFA
Date: Thu, 28 Mar 2024 18:34:48 +0000
References: <CAJO98mNUQ1JcHkbTPZmi_4Pq0G49ta366cmbsSxs4CHHHe=KWw@mail.gmail.com>
Cc: Stewart Bryant <stewart.bryant@gmail.com>, yasu1976@gmail.com
To: Routing WG <rtgwg@ietf.org>, James Guichard <james.n.guichard@futurewei.com>
Message-Id: <1FF74054-58C5-4B03-953B-A02260DDD9A8@gmail.com>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/qU1imn8FuBx2Wll7KM-uH8oKI2M>
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: Thu, 28 Mar 2024 18:35:08 -0000

An interesting point.

The RFC 7490 definition of P-space is


P-space:
      The P-space of a router with respect to a protected link is the
      set of routers reachable from that specific router using the pre-
      convergence shortest paths without any of those paths (including
      equal-cost path splits) transiting that protected link.

      For example, the P-space of S with respect to link S-E is the set
      of routers that S can reach without using the protected link S-E.





For safety the ECMP exclusion needs to apply to extended P-space as well. In both cases unless the ECMP behaviour of all nodes on the path is examined and the packet is specifically steered the safe way (something that cannot be done in the general case but could be done in Ti-LFA) it is unsafe to assume that ECMP will not cause a loop back to the PLR.

I therefore think that either the RFC7490 definition needs to be used, or  there needs to be  specific text included that provides guidance on the need to steer the repaired packet safely though any node that the repaired packet will be routed through that may ECMP via the failure.

Best regards

Stewart



> Begin forwarded message:
> 
> From: Yasuhiro Ohara <yasu1976@gmail.com>
> Subject: Question for TI-LFA
> Date: 24 March 2024 at 05:54:33 GMT
> To: rtgwg@ietf.org
> Cc: Yasuhiro Ohara <yasu1976@gmail.com>
> 
> 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