From nobody Mon May 1 14:48:35 2023 Return-Path: X-Original-To: rtg-dir@ietfa.amsl.com Delivered-To: rtg-dir@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1CE7C151539; Mon, 1 May 2023 14:48:33 -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_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 Zq04cMEraEPP; Mon, 1 May 2023 14:48:31 -0700 (PDT) Received: from mail-ua1-x933.google.com (mail-ua1-x933.google.com [IPv6:2607:f8b0:4864:20::933]) (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 7C8ACC14CE2E; Mon, 1 May 2023 14:48:31 -0700 (PDT) Received: by mail-ua1-x933.google.com with SMTP id a1e0cc1a2514c-77aad9ad986so23362279241.0; Mon, 01 May 2023 14:48:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682977709; x=1685569709; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=BQ93hGI4QpWHIswG8QkdyoOxpIzDG6wK9JiR2QnCwr0=; b=IUAetBP2c6m1rC0+htqxerIaiAxdkgD949zLRYhR2XUiKaRKwYxn4j1uKIRgsZ2tWr hKPgttGuyR+pNIiilFI+hM2dcgtRLXh6SyplSuepJT32fkdFYHfwqdJJcj3F4OBSTgTg GNjn2ysTfIWAuwtdryVvFxu1MPMYRUVc8AfElQa8cm+S9fCIV5Vt5bbDjLutBkaq9UZS TOoGDXEyB+m5uGNsyPD9h8ZRMF1DNKx1uWmxsh+6i8hrz5NHGOoItJ0J7vbFQsEhb0s7 LlJ1jKwyH6vxNiZesrfFm4yXzn64IEkXJvkVBJuQO/0t4Lyk39VLKpu2spASbF01LQhh dGpg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682977709; x=1685569709; 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=BQ93hGI4QpWHIswG8QkdyoOxpIzDG6wK9JiR2QnCwr0=; b=KZqpMMLh/T0GkaUMoqCurlVOhKBsLVCv3J42iCk+19vfYBqWohQhUkIhyZLiIYHaEq DHrhXY3lqffr1ro9uEDnWIBaiIKvDDMXlM2LpycH3Qczci0DoD+YhRpl8z+8stco+nqu WRN4rDkuylyd9w9EK7/w2S6LlcVUlCwtIB6K6kuf2/Mo6dYRbmS+OJxTTH2Dm2OQFl5k XxwhIjcRcRmMEphANNs1czLy5jCUdN8+g4h5pIe4rUpzJ+vSIyR97wzqabTMsM+raB4l AJZk2NPpa2eE/u57NknUc/t0+7imc3t5OFzAYmYkFJBqhrJLxllnW+9BDvsd7fz9wVT3 gCkw== X-Gm-Message-State: AC+VfDz42sxMNT33MaJPrmU0SY4kYklrz5epgSTLpn6Dz31rsThBZB34 W81O45Mg0lydAuvNIYxZTOpvvjnxTpNaQzagreCx8zg= X-Google-Smtp-Source: ACHHUZ5zGoV5GHwkndhghpd1h6sfoQBX0o+2kSrzZuJk2jJDYj2Qp2G+vvJRsj5b8u1YqkPdSyJp+bqQu9Nwv1dalrE= X-Received: by 2002:a05:6122:8d0:b0:440:9ae5:a3ca with SMTP id 16-20020a05612208d000b004409ae5a3camr7685970vkg.8.1682977709476; Mon, 01 May 2023 14:48:29 -0700 (PDT) MIME-Version: 1.0 References: <168296662458.49135.11152971610183102502@ietfa.amsl.com> In-Reply-To: From: Yingzhen Qu Date: Mon, 1 May 2023 14:48:18 -0700 Message-ID: To: "Jeffrey (Zhaohui) Zhang" Cc: "rtg-dir@ietf.org" , "draft-ietf-rtgwg-yang-rib-extend.all@ietf.org" , "last-call@ietf.org" , "rtgwg@ietf.org" Content-Type: multipart/alternative; boundary="00000000000089d22705faa8c83d" Archived-At: Subject: Re: [RTG-DIR] Rtgdir last call review of draft-ietf-rtgwg-yang-rib-extend-16 X-BeenThere: rtg-dir@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: Routing Area Directorate List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 May 2023 21:48:33 -0000 --00000000000089d22705faa8c83d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Jeffrey, I've submitted version -17 and updated the description. For the static routes, I'm leaving as it is unless we receive more feedback asking for augmentation of repair-path. Thanks, Yingzhen On Mon, May 1, 2023 at 2:05=E2=80=AFPM Jeffrey (Zhaohui) Zhang wrote: > Hi Yingzhen, > > > > I can go with that if that=E2=80=99s what the authors/WG=E2=80=99s prefer= ence, but my > preference would be to cover it in the base specification itself. What=E2= =80=99s > the harm? > > > > Anyway, this is not a blocking comment. > > > > Thanks. > > Jeffrey > > > > *From:* Yingzhen Qu > *Sent:* Monday, May 1, 2023 5:01 PM > *To:* Jeffrey (Zhaohui) Zhang > *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, > > > > Considering this is not commonly used, I'd suggest if someone really need= s > it they can do an easy augmentation using the grouping defined in this > draft. > > > > Thanks, > > Yingzhen > > > > On Mon, May 1, 2023 at 1:52=E2=80=AFPM Jeffrey (Zhaohui) Zhang > wrote: > > Hi Yingzhen, > > > > *From:* Yingzhen Qu > *Sent:* Monday, May 1, 2023 4:46 PM > *To:* Jeffrey (Zhaohui) Zhang > *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=E2=80=AFAM 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-ho= p > 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=E2=80=99= 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 > > > Juniper Business Use Only > --00000000000089d22705faa8c83d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Jeffrey,

I've submitted version = -17 and updated the description.=C2=A0

For the sta= tic=C2=A0routes, I'm leaving as it is unless we receive more feedback a= sking for augmentation of repair-path.

Thanks,
Yingzhen

On Mon, May 1, 2023 at 2:05=E2=80=AFPM Jeffrey (Zhaohu= i) Zhang <zzhang@juniper.net&g= t; wrote:

Hi Yingzhen,

=C2=A0

I can go with that if that=E2=80=99s what the author= s/WG=E2=80=99s preference, but my preference would be to cover it in the ba= se specification itself. What=E2=80=99s the harm?

=C2=A0

Anyway, this is not a blocking comment.

=C2=A0

Thanks.

Jeffrey

=C2=A0

From: Yingzhen Qu <yingzhen.ietf@gmail.com>
Sent: Monday, May 1, 2023 5:01 PM
To: Jeffrey (Zhaohui) Zhang <zzhang@juniper.net>
Cc: rtg-dir@ie= tf.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-ex= tend-16

=C2=A0

[External Email. Be cautious of content]

=C2=A0

Hi Jeffrey,

=C2=A0

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

=C2=A0

Thanks,

Yingzhen

=C2=A0

On Mon, May 1, 2023 at 1:52=E2=80=AFPM Jeffrey (Zhao= hui) Zhang <zzha= ng@juniper.net> wrote:

Hi Yingzhen,

=C2=A0

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@ie= tf.org; draft-ietf-rtgwg-yang-rib-extend.all@ietf.org; last-call@ietf.org<= /a>; rtgwg@ietf.org
Subject: Re: Rtgdir last call review of draft-ietf-rtgwg-yang-rib-ex= tend-16

=C2=A0

[External Email. Be cautious of content]

=C2=A0

Hi Jeffrey,

=C2=A0

Thanks for the review, please see my answers below.<= u>

=C2=A0

Thanks,

Yingzhen

=C2=A0

On Mon, May 1, 2023 at 11:43=E2=80=AFAM Zhaohui Zhan= g via Datatracker <noreply@ietf.org> wrote:

Reviewer: Zhaohui Zhang=
Review result: Has Issues

I have the following one nit comment and one question:

=C2=A0 augment "/rt:routing/rt:ribs/rt:rib/"
=C2=A0 =C2=A0 + "rt:routes/rt:route/rt:next-hop/rt:next-hop-options/&q= uot;
=C2=A0 =C2=A0 + "rt:next-hop-list/rt:next-hop-list/rt:next-hop" =C2=A0 {
=C2=A0 =C2=A0 description
=C2=A0 =C2=A0 =C2=A0 "Augment the multiple next hops with repair path.= ";
=C2=A0 =C2=A0 uses repair-path;
=C2=A0 }

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 wit= h a repair path."

=C2=A0

Zzh> Good.

=C2=A0

Shouldn't the repair path be applicable to stati= c routes as well?

[Yingzhen]: Theoretically you can have a repair-path= for a static route, but have you seen this in deployment?=C2=A0<= /u>

=C2=A0

Zzh> Whether anyone implemented/deployed it that = way, I think it=E2=80=99s quite reasonable and desired to have it covered i= n the spec. For example, a static route could be using if1 by default but if2 as backup (in case if1 is down).

=C2=A0

Zzh> Jeffrey

=C2=A0

Juniper Business Use Only


Juniper Business Use Only

--00000000000089d22705faa8c83d--