Re: [Rift] AD Review of draft-ietf-rift-rift-12 (Part 3)

Alvaro Retana <aretana.ietf@gmail.com> Fri, 10 February 2023 13:00 UTC

Return-Path: <aretana.ietf@gmail.com>
X-Original-To: rift@ietfa.amsl.com
Delivered-To: rift@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DDFEC14CF09; Fri, 10 Feb 2023 05:00:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.098
X-Spam-Level:
X-Spam-Status: No, score=-7.098 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 n18tonaTip-Y; Fri, 10 Feb 2023 05:00:04 -0800 (PST)
Received: from mail-pg1-x530.google.com (mail-pg1-x530.google.com [IPv6:2607:f8b0:4864:20::530]) (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 931C0C14F749; Fri, 10 Feb 2023 05:00:04 -0800 (PST)
Received: by mail-pg1-x530.google.com with SMTP id r18so3626014pgr.12; Fri, 10 Feb 2023 05:00:04 -0800 (PST)
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 :message-id:reply-to; bh=/wLT4ZvJ2cL9hWeycUvouHnfQcQm/BT+0/u51o4IL34=; b=N0QozZF3JQF1NmMrztz2KVcpvPVXF8YoU6YAaVsvZAbwbnzLYHAgBduPdxy6DmrdYO IFWAfUehKVoi9WHJwWXx3eY8ySlTvRq4ciOsW83fY41QDCHn6L4zE5MAw19fOIyLmdwQ y7kzNM7yovuziQxOLEbN5wC2HXCQo8ZIBWQfz+iOldD49FnSpYE+Apv4UErQPp+R/dXb uzp+KvJwz85CS5YBUuYOdFcOeA096jVc1s+IuF1UVMEeZrmip1h2mIltQKlgM4+uHFK5 sZFLeMszm0B08xSsD5Z72NY4hMJab2Ie/DW8dcEG2m0SlhBrG9YeaHPOIqc7tkj96bZr bxkg==
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:message-id:reply-to; bh=/wLT4ZvJ2cL9hWeycUvouHnfQcQm/BT+0/u51o4IL34=; b=6x1rKQLooLGG1V9MqcNHRj4GoxZvvkBCRka5ogGb6UMpltYx8Jiq64Zr76ZLh4tytY gNsUj6zh9uVcP34+4ReVsidZQvBzjhs8zMRhJ3fr5Z0OqDvZmGeW18z2fCA1jDHXQ2Ag 70SgfbUwZ0qa/mFkZ4JbNeXVCX7M5kdplrjOWaIUEkBCrPLdHOOHZRyoBIq7HaUk5qpc Vzz3rjqcmzE2FtzAhoWVKwMT4WAcQkTGxGjqMoT89OTYMw+eQIMdixILygM3r4r0xSyb FJEvoKioPMdPLVx1mU7rdaSLw5HArBJc2wKQWD2n3S8+vtgacNGP7u6D9ihX+KJx4Cb9 jBHg==
X-Gm-Message-State: AO0yUKVsVNERYLsr04GCln9IR6GStOa3elzSQZTgRKxejwgEol5X9miW mBt8tS6ZaSMC9qlJjNvqch7yls0lgvYjD3+Qt5s=
X-Google-Smtp-Source: AK7set/a8JTmuJAkbjEH04oLrXpwhyqxiYyfzp4gNb7ZNX9xOqU5JSvqgaf0B1wRmGbTGfkZ7cVPUSPlhattvoOWHDc=
X-Received: by 2002:a63:af15:0:b0:4a0:8210:f47a with SMTP id w21-20020a63af15000000b004a08210f47amr2798215pge.14.1676034003871; Fri, 10 Feb 2023 05:00:03 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Fri, 10 Feb 2023 07:00:02 -0600
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <96A91330-0191-4AA7-871F-AFDD6B45DFB7@juniper.net>
References: <CAMMESszRdNW5nJppTynF8yRMfMcP4O=gGB24UQNNzQbeyPMMzg@mail.gmail.com> <CA+wi2hOnDgtow4nF4oA3voJT_bfFsRMqWt+vO3uGC8PExvkJcw@mail.gmail.com> <CAMMESszg0hyRVrg6xYM-NX_VzhuW4nBzM3g606Y+dJ+fn09itQ@mail.gmail.com> <96A91330-0191-4AA7-871F-AFDD6B45DFB7@juniper.net>
MIME-Version: 1.0
Date: Fri, 10 Feb 2023 07:00:02 -0600
Message-ID: <CAMMESsw+KMJKm_UrKah1Spnjio=npbo_D8xe9QdGk0xV9TtwKg@mail.gmail.com>
To: Jordan Head <jhead@juniper.net>
Cc: "rift@ietf.org" <rift@ietf.org>, "EXT-zhang.zheng@zte.com.cn" <zhang.zheng@zte.com.cn>, "rift-chairs@ietf.org" <rift-chairs@ietf.org>, "draft-ietf-rift-rift@ietf.org" <draft-ietf-rift-rift@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rift/6WABIkOy0AE2xhD7tp1s98yzdiw>
Subject: Re: [Rift] AD Review of draft-ietf-rift-rift-12 (Part 3)
X-BeenThere: rift@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussion of Routing in Fat Trees <rift.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rift>, <mailto:rift-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rift/>
List-Post: <mailto:rift@ietf.org>
List-Help: <mailto:rift-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rift>, <mailto:rift-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2023 13:00:05 -0000

On September 13, 2022 at 8:39:48 AM, Jordan Head wrote:


...
> [major] "neighbors did not see any valid LIEs from a neighbor"
>
> The text is not precise. You're referring to what the local node has
> received (or not) -- using "neighbors did not see...from a neighbor"
> gives both the impression that the state is controlled by others, or
> that the local node is not involved (because the definition is based
> on its neighbors).
>
> I was going to make a suggestion, but the description is not clear to
> me. Reading from the FSM... In OneWay, the node hasn't seen a new
> neighbor (NewNeighbor) but it may have sent a LIE already (not
> necessary), right?
>
> Suggestion>
> OneWay: Initial state. In this state the node has not received
> a valid LIE from another node on the interface.
>
> jhead>> Fixed in new language.

I wasn't clear.  The new text says:

   OneWay: initial state the FSM is starting from. In this state
   the neighbors did not receive any valid LIEs from a neighbor
   after the state was entered.

The part that I'm having a problem with is where it says that "the
neighbors did not receive any valid LIEs from a neighbor".  Which
neighbors did not receive something from which neighbor?  It seems
that one of these neighbors (maybe the first one?) is the local node.
Right?

Suggestion>
   OneWay: initial state the FSM is starting from. In this state
   the router has not received a valid LIE from a neighbor.



...
> 1865 * MultipleNeighborsWait: occurs normally when more than two nodes
> 1866 see each other on the same link or a remote node is quickly
> 1867 reconfigured or rebooted without regressing to `OneWay` first.
> 1868 Each occurrence of the event SHOULD generate a clear, according
> 1869 notification to help operational deployments.
>
> [minor] Maybe I don't remember this from the overview -- where is it
> specified that only point-to-point links (or links with only two
> nodes) are supported?
>
> jhead>> This was in the requirements section but was removed based on previous
> review/comments, would you like us to re-introduce it?

A quick mention (in the Introduction maybe) that rift expects all the
links to be p2p, or only have two nodes would be great.