Re: [Lsvr] WGLC for draft-ietf-lsvr-applicability-09 (to end May 4, 2023)

Ketan Talaulikar <ketant.ietf@gmail.com> Thu, 04 May 2023 11:11 UTC

Return-Path: <ketant.ietf@gmail.com>
X-Original-To: lsvr@ietfa.amsl.com
Delivered-To: lsvr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58FBEC1519AF; Thu, 4 May 2023 04:11:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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_NONE=-0.0001, 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 Eap3GN1KNnAE; Thu, 4 May 2023 04:11:07 -0700 (PDT)
Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (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 6A784C15199A; Thu, 4 May 2023 04:11:07 -0700 (PDT)
Received: by mail-ed1-x532.google.com with SMTP id 4fb4d7f45d1cf-50bc2feb320so505581a12.3; Thu, 04 May 2023 04:11:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683198665; x=1685790665; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=y99eeuBGGIGOPgNYkPWTFco1lMC8T8zZO9InLcRS1rE=; b=TAstRuxN8qfSfsUuhItyV6Cg5kQHPiNgohn1MBOVtuuvj2+G3b+VZGNNWiRs5Yc2d+ iX5F5ZIPGhoIKrAA8kMcUFvkxcnloWgSmVnoAyq+nVE+/62puYx14e1s8UfXFygyPDfI eF/FEKp9NA410ttre3Qyz3C76kLHY10fN6gFyB/tDibM9QtMdGYIpEbRaqbJpeYe2Aqm A1FdVzR18eKzRqpFMSYZ3Twh0xBNrWN1whhh7FwLqnTgrWeqYUZdCDUYBQmB5Y4kI5C4 tY+FhOkF863OFmYf3yLHhf1Jsr/yNezA7VJT2T+gvGV1I3RHndKOK+kx40K4BP2koKFV 0I2g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683198665; x=1685790665; 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=y99eeuBGGIGOPgNYkPWTFco1lMC8T8zZO9InLcRS1rE=; b=KxUb+mOR4fLiSL3N5dFRHtehqCcnObRG6YwVQDWHHmpJVU69I/SZxbIHHn29nL/vtU kYE9XUjxcB2vy0HmSW2KX/gNYj6dq2hjpYhEY0dRhNH5X2AyziWZE0pegEpqwweVVg9y fJTZWnRm4iu8mbzbeVXxycNqIkbgCCJg+q6Ns11e3w6Rv/S59fvkbKPRNMVupNJNeFJ0 zutrzosxyVUFfKYUUoLWKY5ei1ZX1HxlGUVp/YzsLMT36Rg+H2ybOIUa7O9hy4XffQ/V cSJ56OjgAMpYrBrB6cDGXiSi2PM5a9ZQROSjkRaA0e9t2iojjhyeEUUZ8Autda526xZU 7fCQ==
X-Gm-Message-State: AC+VfDzjdseLBEdGBembjhcG1L/dddfvhenPqcJIHMWNyqoK6EOoKIOb go14P4dhCQvVaf6oF9xsMrjRztzvTYzHfPQy5w0etY0t
X-Google-Smtp-Source: ACHHUZ7UAcBn13qqH8X4puoUFhglExgSlH8Sxbs1ZyE0n57g7zAFggieCknholph9zdCFLLEoIq474mdA6geSuX8SPo=
X-Received: by 2002:a17:907:3fa2:b0:94d:7b6b:fda6 with SMTP id hr34-20020a1709073fa200b0094d7b6bfda6mr6687211ejc.22.1683198665338; Thu, 04 May 2023 04:11:05 -0700 (PDT)
MIME-Version: 1.0
References: <AS1PR07MB85895509126E024FF43E9F4AE0639@AS1PR07MB8589.eurprd07.prod.outlook.com> <AS1PR07MB85898F62F643689CC7D94D76E0639@AS1PR07MB8589.eurprd07.prod.outlook.com> <MN2PR13MB4206AD2609819D62A02F938AD2639@MN2PR13MB4206.namprd13.prod.outlook.com> <CAH6gdPwjQ-AHRBx27Hw2GMM2f=qBf-jMMfb_=ifv2oFy7KB_jg@mail.gmail.com> <MN2PR13MB4206546FADAD3F89074F70BED2639@MN2PR13MB4206.namprd13.prod.outlook.com>
In-Reply-To: <MN2PR13MB4206546FADAD3F89074F70BED2639@MN2PR13MB4206.namprd13.prod.outlook.com>
From: Ketan Talaulikar <ketant.ietf@gmail.com>
Date: Thu, 04 May 2023 16:40:54 +0530
Message-ID: <CAH6gdPwJee-HQ4vUwDSV+tTS=SaVWtv_ap7kTjZYumk4RR9jng@mail.gmail.com>
To: lsvr@ietf.org, draft-ietf-lsvr-applicability@ietf.org
Cc: James Guichard <james.n.guichard@futurewei.com>, lsvr-chairs@ietf.org
Content-Type: multipart/alternative; boundary="00000000000088b0c005fadc3a51"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsvr/A2yilS0nKCMWAK1p7fbPCpsv20Q>
Subject: Re: [Lsvr] WGLC for draft-ietf-lsvr-applicability-09 (to end May 4, 2023)
X-BeenThere: lsvr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Link State Vector Routing <lsvr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsvr>, <mailto:lsvr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsvr/>
List-Post: <mailto:lsvr@ietf.org>
List-Help: <mailto:lsvr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsvr>, <mailto:lsvr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 May 2023 11:11:11 -0000

Relaying some comments from Jim that he has shared from his initial/quick
review


On Thu, Apr 20, 2023 at 7:28 PM James Guichard <
james.n.guichard@futurewei.com> wrote:

>
>
> Section 1:
>
>
>
> Really picky comment but i find the introduction awkward as it talks in
> the future tense. For example, the text "Section 5 will describe ..." would
> read
>
> better as "Section 5 describes ..".Also, CLOS here appears to be a name
> rather than a reference so should be Clos (
> https://en.wikipedia.org/wiki/Clos).
>
> See also my section 4 comments.
>
>
>
> Section 4:
>
>
>
> First sentence is not complete. Perhaps "Within a Data Center, servers are
> commonly interconnected using a [CLOS] topology". However, shouldnt CLOS be
>
> "Clos" (https://en.wikipedia.org/wiki/Clos) as used in RFC 7938 (when not
> used as a reference) for example? See section 3.2 of that RFC. Also, you
>
> use CLOS and [CLOS] which is confusing - the former see my "Clos" comment
> and for the latter it is an informative reference which is also used by
>
> RFC 7938?
>
>
>
> Section 5:
>
>
>
> The [RFC7752] reference needs to change to [draft-ietf-idr-rfc7752bis] or
> whatever you want to call the reference.
>
>
>
> Section 6:
>
>
>
>    With the BGP SPF extensions [I-D.ietf-lsvr-bgp-spf], the BGP best-
>
>    path computation and route computation are replaced with OSPF-like
>
>    algorithms [RFC2328]
>
>
>
> It might be better to say "replaced with link-state algorithms such as
> those used by [RFC2328]".
>
>
>
> Section 6.2.1:
>
>
>
> - Need a reference for IEBGP.
>
>
>
> - For example,
>
>    in a Spine-Leaf topology, each leaf switch would only peer with a
>
>    subset of the spines dependent on the flooding redundancy required to
>
>    be reasonably certain that every node within the BGP-LS SPF routing
>
>    domain has the complete topology (refer to Section 6.2.1).
>
>
>
> I do not understand this reference as the text is part of the same section
> that is being referenced ?
>
>
>
> Jim
>
>
>