Re: [Lsr] I-D Action: draft-ietf-lsr-igp-flex-algo-reverse-affinity-02.txt

Robert Raszuk <robert@raszuk.net> Thu, 21 March 2024 16:53 UTC

Return-Path: <robert@raszuk.net>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B18BC151069 for <lsr@ietfa.amsl.com>; Thu, 21 Mar 2024 09:53:00 -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_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=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DXmEdP0rUGsI for <lsr@ietfa.amsl.com>; Thu, 21 Mar 2024 09:52:55 -0700 (PDT)
Received: from mail-lf1-x134.google.com (mail-lf1-x134.google.com [IPv6:2a00:1450:4864:20::134]) (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 EE138C151062 for <lsr@ietf.org>; Thu, 21 Mar 2024 09:52:55 -0700 (PDT)
Received: by mail-lf1-x134.google.com with SMTP id 2adb3069b0e04-513d3746950so1517744e87.1 for <lsr@ietf.org>; Thu, 21 Mar 2024 09:52:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; t=1711039974; x=1711644774; 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=kpT3p+IOTM4NBArEU1AVJitc325MvBHMyoX1tsf49Ws=; b=U27uIz8O9cW3aC8t5+8i0+8ZCu9UUsix8nHsLb9On7BPQed7lBxQUTz3B9/2iPULyB Dd5WR4I6QVQSoiyfsO6NSpZozQVrwoMsB8w4aGrGkxCjWNyE5aYXAab0x/yCED894W5b wMy/kkPF33/p4aFvZCsTmtWUlWlZtDVaIYK2GrKRIesjHJjdhl70m99YpzrVX2mNVu+y 9wLqMSqtTguyy1+B+xlbzekNfq7PuWCMVE+YZ1btzWl4biRLhsf46UifkTn9hr5KOCGP ewLt9+wDIpbf8A36coqGgXO59Hpqhwx+rbd5ZZFpi0cUg4qi1TdJzidYskH4BlelSs2k bf7w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711039974; x=1711644774; 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=kpT3p+IOTM4NBArEU1AVJitc325MvBHMyoX1tsf49Ws=; b=n3L3X4V2UJZAsYbiLoCADhAMpS/jRKXve9zShkfUsrsIY1nToKSXjj4Emc4zIXhbNZ SmectnC64IcG3dm1AmdOSituTGWQrwQMQHUby0vuJ3JIV9sYqBXSiRmRi0zYJ61VmCwX oMHQoiGnAya7qLidHLlbdW0ZYhmVEyWVlEqvY8+op69LIYeCc1/y+h1gPXbycQXpmE1s ATkeJErOwgkyHpmnmnCJFgwQVvEsk4CjsDTdwPgEFeizTT9kaEv2QSPufuCZwcMgRFoe NaKWya0UsRWf9Ykbt7M0+HuQsFjyFoN8BnCdkbhb4Mn68eL+7U9+HQYJIGP0fIPBoNwI MfNQ==
X-Gm-Message-State: AOJu0YyWEKIfWDopLya1raY8nkwGbD0dOlKUeiEHuNI2CSplFHUBTauO TVStdgCBB50cVaO8mAug4LBQBbKl0YEtrJAjyrz4G8ViL101kfcCu7PBxhh9Am8dJZubA3g5ViN b40LjM0+yeRPAK9IjYiJzUmKPW+aTNqrdU8TpZ7ym/nFdIMQy2Fw=
X-Google-Smtp-Source: AGHT+IEZhseBrt9BeHF9pz0fpeRQnlldB7MsBG19iqOtuSiU5Z5S4NT1PnCrIC5vHpIixWEMeghXus3HfXpDaKG/+Pk=
X-Received: by 2002:a19:e04a:0:b0:513:c174:c3f6 with SMTP id g10-20020a19e04a000000b00513c174c3f6mr3820741lfj.40.1711039973699; Thu, 21 Mar 2024 09:52:53 -0700 (PDT)
MIME-Version: 1.0
References: <171074954656.55060.8460468585109925265@ietfa.amsl.com>
In-Reply-To: <171074954656.55060.8460468585109925265@ietfa.amsl.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Thu, 21 Mar 2024 17:52:43 +0100
Message-ID: <CAOj+MMFsx1WLeRFLNozmit8Ptc-NHmiKWw6YHDLtN=YEvY=JAw@mail.gmail.com>
To: Peter Psenak <ppsenak@cisco.com>
Cc: lsr@ietf.org
Content-Type: multipart/alternative; boundary="000000000000d4512906142e8950"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/opG-rlgf42tDb4Bg89-HrndIOfE>
Subject: Re: [Lsr] I-D Action: draft-ietf-lsr-igp-flex-algo-reverse-affinity-02.txt
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2024 16:53:00 -0000

Hi,

> When Flex-Algorithm calculation processes the link A to B, it may look at
> the 'colors' of the link in the reverse direction, e.g., link B to A.
This would
> allow the operator to exclude such link from the Flex-Algorithm topology.

Why do we need the notion of "reverse direction" to be any different then
the notion of forward direction from node B to A on a link ?

Can't we just use the reverse metrics locally by computing node without
flooding
anything new ?

> An operator may measure the rate of such input errors and set certain
'color' on a link
> locally on node B when the input error rate crosses a certain threshold.

IMO the draft should go into more detail or at least provide a pointer to
another document with description how to protect from continued churn in
propagating those colors when oscillate and go below and above a set
threshold many times per second.

Then aside from reducing the propagation frequency local protection from
continued SPF runs should also be mentioned. I guess you assume that this
is in place anyway.

> The IS-IS Flexible Algorithm Exclude Reverse Admin Group (FAERAG)

I think "FAERAG" is very hard to say. How about just "ERAG" as an acronym ?

Thx,
R.


On Mon, Mar 18, 2024 at 9:12 AM <internet-drafts@ietf.org> wrote:

> Internet-Draft draft-ietf-lsr-igp-flex-algo-reverse-affinity-02.txt is now
> available. It is a work item of the Link State Routing (LSR) WG of the
> IETF.
>
>    Title:   IGP Flexible Algorithms Reverse Affinity Constraint
>    Authors: Peter Psenak
>             Jakub Horn
>             Amit Dhamija
>    Name:    draft-ietf-lsr-igp-flex-algo-reverse-affinity-02.txt
>    Pages:   9
>    Dates:   2024-03-18
>
> Abstract:
>
>    An IGP Flexible Algorithm (Flex-Algorithm) allows IGPs to compute
>    constraint-based paths.
>
>    This document extends IGP Flex-Algorithm with additional constraints.
>
> The IETF datatracker status page for this Internet-Draft is:
>
> https://datatracker.ietf.org/doc/draft-ietf-lsr-igp-flex-algo-reverse-affinity/
>
> There is also an HTMLized version available at:
>
> https://datatracker.ietf.org/doc/html/draft-ietf-lsr-igp-flex-algo-reverse-affinity-02
>
> A diff from the previous version is available at:
>
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-lsr-igp-flex-algo-reverse-affinity-02
>
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
>
>
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
>