From: "Aijun Wang" <wangaijun@tsinghua.org.cn>
To: =?utf-8?B?J+OAkOWklumDqOi0puWPt+OAkSBKb2huIFNjdWRkZXIn?= <jgs@juniper.net>
Date: Wed, 28 Aug 2024 15:52:16 +0800
Message-ID: <003d01daf91f$33bce210$9b36a630$@tsinghua.org.cn>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Thread-Index: Adr5Hx9wXFZO+Xl8SDOU43Sg4pufbg==
Content-Language: zh-cn
Message-ID-Hash: EDJ7HB3PVBRWISPYLEICTHWZEN7BHKBA
CC: draft-ietf-pce-pcep-extension-native-ip@ietf.org,
 'The IESG' <iesg@ietf.org>, 'pce-chairs' <pce-chairs@ietf.org>, pce@ietf.org,
 'Murray Kucherawy' <superuser@gmail.com>
Precedence: list
Subject: =?utf-8?q?=5BPce=5D_Re=3A_Murray_Kucherawy=27s_No_Objection_on_draft-ietf-pc?=
	=?utf-8?q?e-pcep-extension-native-ip-34=3A_=28with_COMMENT=29?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/pce/pQLUPSw4P1pCDAQvKjrZ8Rh069o>

Hi, John:

Thanks! Yes, it should be the default preference and leave the =
flexibility for the operator to maneuver it.

I have changed the text and will upload it later together with other =
comments from the IANA, or RFC editors.


Best Regards

Aijun Wang
China Telecom

-----=E9=82=AE=E4=BB=B6=E5=8E=9F=E4=BB=B6-----
=E5=8F=91=E4=BB=B6=E4=BA=BA: forwardingalgorithm@ietf.org =
[mailto:forwardingalgorithm@ietf.org] =E4=BB=A3=E8=A1=A8 =
=E3=80=90=E5=A4=96=E9=83=A8=E8=B4=A6=E5=8F=B7=E3=80=91 John Scudder
=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2024=E5=B9=B48=E6=9C=8827=E6=97=A5 =
21:59
=E6=94=B6=E4=BB=B6=E4=BA=BA: Aijun Wang <wangaijun@tsinghua.org.cn>
=E6=8A=84=E9=80=81: draft-ietf-pce-pcep-extension-native-ip@ietf.org; =
The IESG <iesg@ietf.org>; pce-chairs <pce-chairs@ietf.org>; =
pce@ietf.org; Murray Kucherawy <superuser@gmail.com>
=E4=B8=BB=E9=A2=98: Re: [Pce] Murray Kucherawy's No Objection on =
draft-ietf-pce-pcep-extension-native-ip-34: (with COMMENT)

Hi Aijun,

Thanks for the update. I have one note on this revised paragraph:

   The path established by this object MUST have higher priority than
   the other paths calculated by dynamic IGP protocol, and MUST have
   lower priority than the static route configured by manual or NETCONF
   or any other static means.

IMO MUST without any qualification is too strong here, because generally =
in my experience, routing implementations let the operator configure the =
sorting/priority order of different protocols. Would it be correct to =
add =E2=80=9Cby default=E2=80=9D here, as in,=20

NEW:
   By default,=20
   the path established by this object MUST have higher priority than
   the other paths calculated by dynamic IGP protocol, and MUST have
   lower priority than the static route configured by manual or NETCONF
   or any other static means.

Thanks,

=E2=80=94John

> On Aug 27, 2024, at 3:22=E2=80=AFAM, Aijun Wang =
<wangaijun@tsinghua.org.cn> wrote:
>=20
> [External Email. Be cautious of content]
>=20
>=20
> Hi, John:
>=20
> Thanks for your remind.
> I upload again the updated version to solve Murray's comments on this =
document.
> The usage of "SHOULD" is decreased at it is replaced with non-RFC2119 =
work, or enhanced with the replace of "MUST=E2=80=9C.
>=20
> The updates covers the section 10 and section 7.3 that Murray =
mentioned, and also the section 7.2 and 7.4 for the similar =
descriptions.
>=20
> Wish they can address the concerns that raised by Murray.
> It seems after the several round changes, the mode for the=20
> "SHOULD/MUST" has fallen back to the version 34 in some extents, as=20
> you have suggested :)
>=20
>=20
> Best Regards
>=20
> Aijun Wang
> China Telecom
>=20
> -----=E9=82=AE=E4=BB=B6=E5=8E=9F=E4=BB=B6-----
> =E5=8F=91=E4=BB=B6=E4=BA=BA: forwardingalgorithm@ietf.org
> [mailto:forwardingalgorithm@ietf.org] =E4=BB=A3=E8=A1=A8 John Scudder
> =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: =
2024=E5=B9=B48=E6=9C=8827=E6=97=A5 2:34
> =E6=94=B6=E4=BB=B6=E4=BA=BA: =
draft-ietf-pce-pcep-extension-native-ip@ietf.org
> =E6=8A=84=E9=80=81: The IESG <iesg@ietf.org>; pce-chairs =
<pce-chairs@ietf.org>;=20
> pce@ietf.org; Murray Kucherawy <superuser@gmail.com>
> =E4=B8=BB=E9=A2=98: [Pce] Re: Murray Kucherawy's No Objection on
> draft-ietf-pce-pcep-extension-native-ip-34: (with COMMENT)
>=20
> Hi Authors,
>=20
> I think you might have overlooked replying to Murray=E2=80=99s =
question.
>=20
> =E2=80=94John
>=20
>> On Aug 22, 2024, at 2:39=E2=80=AFAM, Murray Kucherawy via Datatracker =
<noreply@ietf.org> wrote:
>>=20
>>=20
>> Murray Kucherawy has entered the following ballot position for
>> draft-ietf-pce-pcep-extension-native-ip-34: No Objection
>>=20
>> When responding, please keep the subject line intact and reply to all =

>> email addresses included in the To and CC lines. (Feel free to cut=20
>> this introductory paragraph, however.)
>>=20
>>=20
>> Please refer to
>> https://urldefense.com/v3/__https://www.ietf.org/about/groups/iesg/st
>> a
>> tements/handling-ballot-positions/__;!!NEt6yMaO-gk!CB1o2jlxBvTh_Pxjyz
>> g _DCX1oY1AUsUhpAhzalTBCr84oba8fUeDGriejxGLpyCDl4PbiJ1u4pva$
>> for more information about how to handle DISCUSS and COMMENT =
positions.
>>=20
>>=20
>> The document, along with other ballot positions, can be found here:
>> https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ie
>> t
>> f-pce-pcep-extension-native-ip/__;!!NEt6yMaO-gk!CB1o2jlxBvTh_Pxjyzg_D
>> C X1oY1AUsUhpAhzalTBCr84oba8fUeDGriejxGLpyCDl4PbiLZbCgGX$
>>=20
>>=20
>>=20
>> ---------------------------------------------------------------------
>> -
>> COMMENT:
>> ---------------------------------------------------------------------
>> -
>>=20
>> The SHOULD in Section 10 and the RECOMMENDED in Section 7.3 seem to=20
>> be unsupported.  Why might an implementer choose not to do what they =
say?
>> What's the impact to interoperability?
>>=20
>> I echo Roman's question about the document's status.
>>=20
>>=20
>>=20
>> _______________________________________________
>> Pce mailing list -- pce@ietf.org
>> To unsubscribe send an email to pce-leave@ietf.org
>=20
> _______________________________________________
> Pce mailing list -- pce@ietf.org
> To unsubscribe send an email to pce-leave@ietf.org
>=20