Re: Rtgdir last call review of draft-ietf-rtgwg-yang-rib-extend-16

Yingzhen Qu <yingzhen.ietf@gmail.com> Mon, 01 May 2023 21:01 UTC

Return-Path: <yingzhen.ietf@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 D1DE3C14F74A; Mon, 1 May 2023 14:01:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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] 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 3bwag9f4GZxD; Mon, 1 May 2023 14:01:31 -0700 (PDT)
Received: from mail-vk1-xa2c.google.com (mail-vk1-xa2c.google.com [IPv6:2607:f8b0:4864:20::a2c]) (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 4D0EFC14CE47; Mon, 1 May 2023 14:01:31 -0700 (PDT)
Received: by mail-vk1-xa2c.google.com with SMTP id 71dfb90a1353d-44062aa1b5bso855690e0c.1; Mon, 01 May 2023 14:01:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682974890; x=1685566890; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=KBviheHctG0DwKL/F1PQGvHLcRcrncCKp4U2YcTr39I=; b=Kfg7AeV5UB8u9TesQNWVkdtmnCJkxyZ6Vh0eqb0ZqUQdqwoJodNF8+Qy+P1TGCK1xR E3zwpIZ1uoN+4DdsyMYATbbyJWc72Qs98jVuyupHt31oFZ59UDbdoCEscLSg4hxo13B5 f7FOWHvA3+aSgtGRqAiwsetZ/9oHA2X94JrIwalpKwDw4IHmPuXTGP3Lun5Kf2EkgnTR RvqfLI1JTyzhaJsJVxoQKqnk59LfN/3DOTMZE+g91BtC+ojBeQsrg/yt6B0ok0eXTKQA FOwUomQP/RZZzl4bioAWWyaXBipklmcpOBZZ/EERtAqxU9quwtwzy8a4Jk/brpSzkxvn 5I5w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682974890; x=1685566890; 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=KBviheHctG0DwKL/F1PQGvHLcRcrncCKp4U2YcTr39I=; b=IhK13oHY+wJta6KQwBqHSTZShLcEO6RcSbmk84481ga+yLbvWm7pzXhLfqnMsZ/GzT rtwf3wHv4IQ0gfS5aBTlW6fxiN3rTIGABiUMZqubbBgmmmDzMDmFlF9C0cwmfUug0zSh EB1nUdiCI8aoJUKC6mFQgyz2f0dVwNbVoab5KAmoHDQTIx0vkvxlEqmTy9TtI4jBVgIu U3z6xrZX7i7la/fnNFxlWrKafrVQupaeSl0W38kx8UMSA8hnNXRgr1g45O/ilyNuB1Cb TNVOi49SueIRSgemhQ+d4hpNVOJJumnLUibkWFdiFTUTQrKpg/FcxxXcBRb+yZzggovo aerw==
X-Gm-Message-State: AC+VfDyAoIY57pgU3gBkBTX/9IDr/gxghdjjc0hncIShH+f7iRfWnNHH GrcRFK9F3iyGAigkx59aPS67Hmy4yM6mbdz2sw==
X-Google-Smtp-Source: ACHHUZ6hhOia75wI9c8MLM1Df2z9ohlGMSE10q/1NCXDkrv5T7iv2bcKlT1dyYLds04uTLvm2VED0vcrwyYl1uDqKuU=
X-Received: by 2002:a1f:4981:0:b0:43f:ea0c:6ded with SMTP id w123-20020a1f4981000000b0043fea0c6dedmr4392750vka.4.1682974889482; Mon, 01 May 2023 14:01:29 -0700 (PDT)
MIME-Version: 1.0
References: <168296662458.49135.11152971610183102502@ietfa.amsl.com> <CABY-gOMerNd0=P2zwdt4b=y0_wHUsWqYAi+Q0He38EiYPz0Qeg@mail.gmail.com> <BL0PR05MB56522903F5682207980F1908D46E9@BL0PR05MB5652.namprd05.prod.outlook.com>
In-Reply-To: <BL0PR05MB56522903F5682207980F1908D46E9@BL0PR05MB5652.namprd05.prod.outlook.com>
From: Yingzhen Qu <yingzhen.ietf@gmail.com>
Date: Mon, 01 May 2023 14:01:18 -0700
Message-ID: <CABY-gOPy6kuCeL80USyLtNxZPNeFdStfZ94_n4NHXjH8M2CaKQ@mail.gmail.com>
Subject: Re: Rtgdir last call review of draft-ietf-rtgwg-yang-rib-extend-16
To: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
Cc: "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "draft-ietf-rtgwg-yang-rib-extend.all@ietf.org" <draft-ietf-rtgwg-yang-rib-extend.all@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000741da405faa820d8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/jejbvRCOc4RzgS4ghHyA-30ECTk>
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: Mon, 01 May 2023 21:01:35 -0000

Hi Jeffrey,

Considering this is not commonly used, I'd suggest if someone really needs
it they can do an easy augmentation using the grouping defined in this
draft.

Thanks,
Yingzhen

On Mon, May 1, 2023 at 1:52 PM Jeffrey (Zhaohui) Zhang <zzhang@juniper.net>
wrote:

> Hi Yingzhen,
>
>
>
> *From:* Yingzhen Qu <yingzhen.ietf@gmail.com>
> *Sent:* Monday, May 1, 2023 4:46 PM
> *To:* Jeffrey (Zhaohui) Zhang <zzhang@juniper.net>
> *Cc:* rtg-dir@ietf.org; draft-ietf-rtgwg-yang-rib-extend.all@ietf.org;
> last-call@ietf.org; rtgwg@ietf.org
> *Subject:* Re: Rtgdir last call review of
> draft-ietf-rtgwg-yang-rib-extend-16
>
>
>
> *[External Email. Be cautious of content]*
>
>
>
> Hi Jeffrey,
>
>
>
> Thanks for the review, please see my answers below.
>
>
>
> Thanks,
>
> Yingzhen
>
>
>
> On Mon, May 1, 2023 at 11:43 AM Zhaohui Zhang via Datatracker <
> noreply@ietf.org> wrote:
>
> Reviewer: Zhaohui Zhang
> Review result: Has Issues
>
> I have the following one nit comment and one question:
>
>   augment "/rt:routing/rt:ribs/rt:rib/"
>     + "rt:routes/rt:route/rt:next-hop/rt:next-hop-options/"
>     + "rt:next-hop-list/rt:next-hop-list/rt:next-hop"
>   {
>     description
>       "Augment the multiple next hops with repair path.";
>     uses repair-path;
>   }
>
> The description is slightly misleading. It is to agument a single next-hop
> in
> the next-hop-list, not "multiple next hops".
>
> [Yingzhen] how about: "Augment the next-hop with a repair path."
>
>
>
> Zzh> Good.
>
>
>
> Shouldn't the repair path be applicable to static routes as well?
>
> [Yingzhen]: Theoretically you can have a repair-path for a static route,
> but have you seen this in deployment?
>
>
>
> Zzh> Whether anyone implemented/deployed it that way, I think it’s quite
> reasonable and desired to have it covered in the spec. For example, a
> static route could be using if1 by default but if2 as backup (in case if1
> is down).
>
>
>
> Zzh> Jeffrey
>
> Juniper Business Use Only
>