Re: [Lsr] Alvaro Retana's Discuss on draft-ietf-lsr-flex-algo-24: (with DISCUSS)

Alvaro Retana <aretana.ietf@gmail.com> Thu, 06 October 2022 11:51 UTC

Return-Path: <aretana.ietf@gmail.com>
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 D3811C14F72C; Thu, 6 Oct 2022 04:51:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 jt2cK6FamYQi; Thu, 6 Oct 2022 04:51:06 -0700 (PDT)
Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) (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 424DFC14F720; Thu, 6 Oct 2022 04:51:01 -0700 (PDT)
Received: by mail-pl1-x62b.google.com with SMTP id 10so1556750pli.0; Thu, 06 Oct 2022 04:51:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date :mime-version:references:in-reply-to:from:from:to:cc:subject:date; bh=f6jrVnw0BbDU/+PgrqUXXHFJYEUcWZtz3NRrFwUjghk=; b=hH1+Y7ptzP/SM2SBMOfO7J4pFiJ0K1RC4MtlzKAs73Tpw2JGGkax/cC+dhIo+DZFVF WyDW6sgkRMp7+qKr+h3pnn44NfXCEU8qWZZOkVuXFmIVVBl8xsCJkrR6XEhhtLs7o3Td Erfx4HCvOYd5ldxHY9uikMFW6fwoc/DKvNWXA5rm1iH5vLLOxWzqs4Wwwsvc1V0YX4fp EeL4zgpdkIbMj3Eb7C6dp2fuq3I+dYHUtTfIFyKeXVTPpuY/hwu0h1o1zbEt6b0airBE OxO4So66HS7bkW69/orL7iFbOYH3mnszWTR2Z6gdDikkyX+ViQKzgKXlchAHGEI9x3ts Z0gQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date :mime-version:references:in-reply-to:from:x-gm-message-state:from:to :cc:subject:date; bh=f6jrVnw0BbDU/+PgrqUXXHFJYEUcWZtz3NRrFwUjghk=; b=BjD+XgJsHgTvivwv3yYYc5JDZmB4Qy5QloEQv3sqHR2E7pzEjGCG4OrdwUHsmhH+rd W16wCq0RvandgbRPjMVD9SrQ03+bsvu0MeZLyVzNn3M+sEDxGEv9qwvRpek3NjFUzhab GWcphA3vjqO5tcWydua7rV/fMdc6tL5fg72NeTNGYXDC/kMZyHdU5pXAi/JJffQFOKIu vKDTi27tClNNVrPX/XjhOVvnw8SvMYALEN7XEA7jPFtCgTvdI0TeP9BY0f2LOq0Mqxnk AR88LF75Oq3hS328HpV+yZTSARD/6p8zGEsGsuIqbCLZPgFyR3q/yqURPFST+GJW2yXz EHSA==
X-Gm-Message-State: ACrzQf0V2/9idMOpU+EfRIQ66q5gsPb5oabfrsks5CkwkHymmqxDni9L jo1469lbXgN0No+4UtGLxyR3mLSNUeyQQgzaWmk=
X-Google-Smtp-Source: AMsMyM6DWmWeeY6Es0IHxBjFLTv3GNhCW5baNSWu5mR7DVb8P/3ddCHd1mTAmKH+q+pNinwj2u9JwOBDfdZgngHrMA8=
X-Received: by 2002:a17:903:2d1:b0:17d:ba07:42d4 with SMTP id s17-20020a17090302d100b0017dba0742d4mr4349750plk.92.1665057060595; Thu, 06 Oct 2022 04:51:00 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Thu, 6 Oct 2022 04:50:59 -0700
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <0d938afe-94b0-2186-cc04-42b2ccee19d5@cisco.com>
References: <166497948643.39691.5083450220590558021@ietfa.amsl.com> <5cf76c12-c928-ad9f-fa82-1776abbe2ad2@cisco.com> <CAMMESsy5wPBwYPKev2+sO2vD55_HrEGmk-zB5Nzr35rOAMQN_w@mail.gmail.com> <0d938afe-94b0-2186-cc04-42b2ccee19d5@cisco.com>
MIME-Version: 1.0
Date: Thu, 06 Oct 2022 04:50:59 -0700
Message-ID: <CAMMESswjYtGmQBXcRt8u7S3=PFb4V4rygN8o44JxETPxCaD7kA@mail.gmail.com>
To: Peter Psenak <ppsenak@cisco.com>, The IESG <iesg@ietf.org>
Cc: acee@cisco.com, draft-ietf-lsr-flex-algo@ietf.org, jgs@juniper.net, lsr-chairs@ietf.org, lsr@ietf.org, Christian Hopps <chopps@chopps.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/KduS2V-W52gg8-spRtnoUl5CnFE>
Subject: Re: [Lsr] Alvaro Retana's Discuss on draft-ietf-lsr-flex-algo-24: (with DISCUSS)
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, 06 Oct 2022 11:51:10 -0000

On October 6, 2022 at 6:58:18 AM, Peter Psenak wrote:


Peter:


...
> > (1) The text above instructs implementations of [RFC8667] and
> > [RFC8665] to stop advertising the specific Flex-Algorithm value, but
> > those RFCs (if I remember correctly) don't say anything about *not*
> > advertising the SR-Algorithm TLV/sub-TLV. This document should
> > formally Update those RFCs.
>
> ##PP2
> advertising the SR-Algorithm TLV is optional.
>
> https://datatracker.ietf.org/doc/html/rfc8665#section-3.1
>
> "The SR-Algorithm TLV is optional. It SHOULD only be advertised once
> in the Router Information Opaque LSA."
>
>
> Advertising any set of algorithms in this TLV is supported. A router is
> free to add or remove any algorithm value from the TLV. This is all well
> supported by both above mentioned RFCs. I don't see any need for update.

Even if optional, that concerns me is the contents of the TLV.
Looking at them, both RFCs say: "The SR-Algorithm TLV allows a router
to advertise the algorithms currently used by the router..."

Sure, there's a connection between "MUST NOT announce" (from 5.3) and
"currently used".   You're right, we don't need an update.



> > (2) The text related to the Update should be in §11, which is where
> > the participation advertisement is specified. Text should also be
> > added to §11.2 to indicate that other data-planes have to do the same
> > thing.
>
> ##PP2
> I have added following to the section 11:
>
> "Advertisement of the participation for any particular Flex-Algorithm
> in any data-plane is subject to the condition specified in
> Section 5.3."
>
> Would that be sufficient?

Yes, that's fine.


I'm ok with the other changes too.

I'll clear my DISCUSS.

Thanks!!

Alvaro.