Return-Path: X-Original-To: pce@ietfa.amsl.com Delivered-To: pce@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C27BC1840F8 for ; Wed, 11 Sep 2024 21:11:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.907 X-Spam-Level: X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dhruvdhody-com.20230601.gappssmtp.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 4OcPZgqUsUQG for ; Wed, 11 Sep 2024 21:11:48 -0700 (PDT) Received: from mail-ot1-x32a.google.com (mail-ot1-x32a.google.com [IPv6:2607:f8b0:4864:20::32a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90B7AC1840F7 for ; Wed, 11 Sep 2024 21:11:48 -0700 (PDT) Received: by mail-ot1-x32a.google.com with SMTP id 46e09a7af769-710ea99f664so12836a34.3 for ; Wed, 11 Sep 2024 21:11:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dhruvdhody-com.20230601.gappssmtp.com; s=20230601; t=1726114308; x=1726719108; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=bemTctPbG65W65nApTAbz+yBwg41LEP9P/SfwLhXTVE=; b=sV/kEHvwL8poqqT96AeR+jpJQLq1DEalu0kepx4lDKlh2Wx9OffeLA3TQmWle3Vgmq c2S507gHK+ZAO0dBoQrK+/UbQ7Wh2BvsnjwQno0lFE100/wotmp3PVzEXnqTlh0ck3p1 SzmlEx2G/SCa4G2/0tlGWoKyq/DcKQbhyjSjkFCpNhrkW7Ag9afuj97bVmZw8S7AL8DU 9FfsWaIdd69kdoFje48DAOA9oyfun40GRj/FK7lV3WILoClo32eWd1xxzhanMTatlBC0 e4VS/MnQ4+niCqAyyVSkXqAXPtTwOdST3k1lJKgNd0gsDgqqLUUHi3ZHJ7tpwMindGcL 3ODg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726114308; x=1726719108; 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=bemTctPbG65W65nApTAbz+yBwg41LEP9P/SfwLhXTVE=; b=fKiC/h12OV/Rk3Po0FqB3ko+L/jqAzKIG6UQgASIxmPtImxWZaGLS4kDZOZdBt5Vi1 qxwrwgiRVYriAr4DVbXBrqkqYVIB8+0BaxlmMuv/UT8MgpeqWU0Yvn6gkCEQwREVp4lP O9N12sXzCqeYxu22EnyQxFzBvuxdgqorGlD6nEa17bWrr21E4A1MuNgLaSZCgt9pn3wn YI6rJnG09S2v4Igfowvc+XEXXnffkpiNNJjF3kLjxUDRjsXg78IqoNWi5tyILhdb1mcY RBIFkapxUQdZiW0Qc+zLFfugG7B7QcaE8ZxVEQQdcp+xI/4MMsx3akdRYrRVbgWiUrfR BSjg== X-Forwarded-Encrypted: i=1; AJvYcCWqQH7NodutJPT34rxiPbBE1Jew+g2vof5TPKZt2TgKGmCycgRqgfnk+6KvmgWoJ8rXUgA=@ietf.org X-Gm-Message-State: AOJu0YztBI0Ajp5YVt8YmZ0nnCOC5LacwXxLn8dnLZoZdXFQN8QEFJy+ hWRN7PuO87wh6MIbwJZx4Y6CPKZ9wP00aL0AP/0cLtcW4ul1v1zL2c6wLinAABm0gNVwOqonz42 2KBA2lq0M+ys4lWxt1JK+/G8tzJtdMavRpnQ4GQ== X-Google-Smtp-Source: AGHT+IEvlmk0szV8TSYD4qnnrrEuJtIp3b3SdZPuwcKiDUpx70I5VDAfAXaspD8exB0OHaEgPXQhJphYHS79wJGbSaE= X-Received: by 2002:a05:6870:1587:b0:278:35b:e9ef with SMTP id 586e51a60fabf-27c3f62c9a1mr249793fac.10.1726114307423; Wed, 11 Sep 2024 21:11:47 -0700 (PDT) MIME-Version: 1.0 References: <20240912110918929ARPKsDP4XNOcODIP-Q4rr@zte.com.cn> In-Reply-To: <20240912110918929ARPKsDP4XNOcODIP-Q4rr@zte.com.cn> From: Dhruv Dhody Date: Thu, 12 Sep 2024 09:41:10 +0530 Message-ID: To: xiong.quan@zte.com.cn Content-Type: multipart/alternative; boundary="00000000000022dbab0621e44efc" Message-ID-Hash: ZOPZZB2NBJEESWYJQTFEV7S5TDWLGSBE X-Message-ID-Hash: ZOPZZB2NBJEESWYJQTFEV7S5TDWLGSBE X-MailFrom: dd@dhruvdhody.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-pce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: draft-ietf-pce-sr-path-segment@ietf.org, pce@ietf.org X-Mailman-Version: 3.3.9rc4 Precedence: list Subject: =?utf-8?q?=5BPce=5D_Re=3A_I-D_Action=3A_draft-ietf-pce-sr-path-segment-10=2E?= =?utf-8?q?txt?= List-Id: Path Computation Element Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --00000000000022dbab0621e44efc Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks Quan! LGTM! On Thu, Sep 12, 2024 at 8:40=E2=80=AFAM wrote: > Hi Dhruv, > > > Thanks for your review and suggestions! > > Please see inline with [Quan]. > > The new version is attached. Thanks! > > > Best Regards, > > Quan > > > Original > *From: *DhruvDhody > *To: *=E7=86=8A=E6=B3=8900091065; > *Cc: *c.l@huawei.com ; > draft-ietf-pce-sr-path-segment@ietf.org < > draft-ietf-pce-sr-path-segment@ietf.org>;pce@ietf.org ; > *Date: *2024=E5=B9=B409=E6=9C=8811=E6=97=A5 23:26 > *Subject: **Re: [Pce] Re: I-D Action: > draft-ietf-pce-sr-path-segment-10.txt* > Hi Quan, Cheng > > For this text -> > > The ASSOCIATION object should also be carried in PCInitiate > message to indicate the SR policy association parameters as per > [I-D.ietf-pce-segment-routing-policy-cp], if this path segment > identifies an SR policy. > > Note that currently we do not have a way to signal if the path segment > identifies a CP or a SR-Policy. > (1) Is it required to be explicitly signalled? > (2) Or should you simply state that the SR policy association needs to be > included if the SR path belongs to an SR Policy? > > (3) Consider using normative keywords here MUST(?) > > > [Quan] From my understanding, it is not required to be exlicitly indicate= d > and it may need normative keywords MUST. > > So as you suggested, this text can be revised as following. > > "The ASSOCIATION object MUST also be carried in PCInitiate message to > indicate the SR policy association parameters as > per[I-D.ietf-pce-segment-routing-policy-cp], if this SR path belongs to a= n > SR policy." > > What is your thought? > > =3D=3D > > Consider adding this text in the Introduction -> > > Although [RFC9050] defines the PCE as the central controller (PCECC) mode= l, > where the PCE can instruct each hop (including the egress) on the > end-to-end path, PCE (as per [RFC5040], [RFC8231], and [RFC8281]) typical= ly > only communicates with the ingress node. However, since the path segment > identifies the SR path on the egress node, the PCE must also communicate > with the egress node. This document outlines a mechanism to use the > existing stateful message exchange with the egress node to signal both th= e > > SR path and the path segment. > > > [Quan] Thanks for your detailed texts. I think it is very great. It is > very appreciated. > > I suggest to add this texts to the end of the introduction section. Pleas= e > see the attachment. Thanks! > > > > =3D=3D > > Thanks! > Dhruv (as a WG participant) > > > On Wed, Sep 11, 2024 at 12:17=E2=80=AFPM wrote: > > > > > Hi Cheng and Co-authors, > > > > > > I have updated the draft as discussed and the diff file is attached. > > > > > Please review and comment and I will submit it before this weekend! Tha= nks! > > > > > > Best Regards, > > > > Quan > > > > > > Original > > *From: *ChengLi > > *To: *=E7=86=8A=E6=B3=8900091065;dd@dhruvdhody.com ; > > *Cc: *pce@ietf.org ; > draft-ietf-pce-sr-path-segment@ietf.org > > ; > > *Date: *2024=E5=B9=B409=E6=9C=8809=E6=97=A5 17:42 > > *Subject: **RE: [Pce] Re: I-D Action: > > draft-ietf-pce-sr-path-segment-10.txt* > > > > Hi Quan, > > > > > > > > Do you mind to lead this update? If yes, please update the xml(You can > > download it from the datatracker) and share the diff file for authors t= o > > review. > > > > > > > > I am crazy busy on updating 10+ drafts recently. If you can help on thi= s, > > I will be very appreciated! > > > > > > > > Thanks, > > > > Cheng > > > > > > > > > > > > *From:* xiong.quan@zte.com.cn > > *Sent:* Monday, September 9, 2024 11:23 AM > > *To:* dd@dhruvdhody.com > > *Cc:* jmh.direct@joelhalpern.com; gregimirsky@gmail.com; pce@ietf.org; > > draft-ietf-pce-sr-path-segment@ietf.org > > > *Subject:* Re: [Pce] Re: I-D Action: draft-ietf-pce-sr-path-segment-10.= txt > > > > > > > > > > > > Hi Dhruv and Joel, > > > > > > > > Thanks for your suggestion! > > > > > > > > The adding texts in my last email mainly clarify the path segment relat= ed > > parameters (e.g association) within an SR policy. I think the PCE > > communicates with the tail instead of a notification, for example, as > > figure 3 shown, it send PCInitiate message to the egress PCC for PCE ta= il > > notification, for example, as figure 3 shown. > > > > > > > > I agree that the path segment is the first function that requires > > > communication with both tail and head end cause the the path segment sh= ould > > be inserted at the ingress PCC and should be recognized at the egress P= CC > > > _______________________________________________ > Pce mailing list -- pce@ietf.org > To unsubscribe send an email to pce-leave@ietf.org > --00000000000022dbab0621e44efc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks Quan! LGTM!=C2=A0

On Thu, Sep 12= , 2024 at 8:40=E2=80=AFAM <xion= g.quan@zte.com.cn> wrote:

Hi Dhruv,


Thanks for your= review and suggestions!

Please see inli= ne with [Quan].=C2=A0

The new version is= attached. Thanks!


Best Regards,

Quan=


Original
Date:=C2=A02024=E5=B9=B409=E6=9C= =8811=E6=97=A5 23:26
Subject:=C2=A0= Re: [Pce] Re: I-D Action: draft-ietf-pce-sr-path-segment-10.txt
Hi=C2=A0Quan,=C2=A0Cheng

For=C2=A0this= =C2=A0text=C2=A0->

The=C2=A0ASSOCIATION=C2=A0object=C2=A0should= =C2=A0also=C2=A0be=C2=A0carried=C2=A0in=C2=A0PCInitiate
message=C2=A0to= =C2=A0indicate=C2=A0the=C2=A0SR=C2=A0policy=C2=A0association=C2=A0parameter= s=C2=A0as=C2=A0per
[I-D.ietf-pce-segment-routing-policy-cp],=C2=A0if=C2= =A0this=C2=A0path=C2=A0segment
identifies=C2=A0an=C2=A0SR=C2=A0policy.
Note=C2=A0that=C2=A0currently=C2=A0we=C2=A0do=C2=A0not=C2=A0have=C2= =A0a=C2=A0way=C2=A0to=C2=A0signal=C2=A0if=C2=A0the=C2=A0path=C2=A0segmentidentifies=C2=A0a=C2=A0CP=C2=A0or=C2=A0a=C2=A0SR-Policy.
(1)=C2=A0Is= =C2=A0it=C2=A0required=C2=A0to=C2=A0be=C2=A0explicitly=C2=A0signalled?
(= 2)=C2=A0Or=C2=A0should=C2=A0you=C2=A0simply=C2=A0state=C2=A0that=C2=A0the= =C2=A0SR=C2=A0policy=C2=A0association=C2=A0needs=C2=A0to=C2=A0be
include= d=C2=A0if=C2=A0the=C2=A0SR=C2=A0path=C2=A0belongs=C2=A0to=C2=A0an=C2=A0SR= =C2=A0Policy?

(3)=C2=A0Consider=C2=A0using=C2=A0normative=C2=A0keywor= ds=C2=A0here=C2=A0MUST(?)


[Quan] From my understanding, it= is not required to be exlicitly indicated and it may need normative keywor= ds MUST.

So as you suggested, this text can be revised as following.<= /p>

"The ASSOCIATION object MUST also be carried in PCInitiate messa= ge to indicate the SR policy association parameters as per[I-D.ietf-pce-seg= ment-routing-policy-cp], if this SR path belongs to an SR policy."

=

What is your thought?


=3D=3D

Consider=C2=A0adding=C2=A0th= is=C2=A0text=C2=A0in=C2=A0the=C2=A0Introduction=C2=A0->

Althoug= h=C2=A0[RFC9050]=C2=A0defines=C2=A0the=C2=A0PCE=C2=A0as=C2=A0the=C2=A0centr= al=C2=A0controller=C2=A0(PCECC)=C2=A0model,
where=C2=A0the=C2=A0PCE=C2= =A0can=C2=A0instruct=C2=A0each=C2=A0hop=C2=A0(including=C2=A0the=C2=A0egres= s)=C2=A0on=C2=A0the
end-to-end=C2=A0path,=C2=A0PCE=C2=A0(as=C2=A0per=C2= =A0[RFC5040],=C2=A0[RFC8231],=C2=A0and=C2=A0[RFC8281])=C2=A0typically
on= ly=C2=A0communicates=C2=A0with=C2=A0the=C2=A0ingress=C2=A0node.=C2=A0Howeve= r,=C2=A0since=C2=A0the=C2=A0path=C2=A0segment
identifies=C2=A0the=C2=A0S= R=C2=A0path=C2=A0on=C2=A0the=C2=A0egress=C2=A0node,=C2=A0the=C2=A0PCE=C2=A0= must=C2=A0also=C2=A0communicate
with=C2=A0the=C2=A0egress=C2=A0node.=C2= =A0This=C2=A0document=C2=A0outlines=C2=A0a=C2=A0mechanism=C2=A0to=C2=A0use= =C2=A0the
existing=C2=A0stateful=C2=A0message=C2=A0exchange=C2=A0with=C2= =A0the=C2=A0egress=C2=A0node=C2=A0to=C2=A0signal=C2=A0both=C2=A0the

S= R=C2=A0path=C2=A0and=C2=A0the=C2=A0path=C2=A0segment.


[Qua= n] Thanks for your detailed texts. I think it is very great. It is very app= reciated.

I suggest to add this texts to the end of the introduction = section. Please see the attachment. Thanks!



=3D=3D
Thanks!
Dhruv=C2=A0(as=C2=A0a=C2=A0WG=C2=A0participant)


O= n=C2=A0Wed,=C2=A0Sep=C2=A011,=C2=A02024=C2=A0at=C2=A012:17=E2=80=AFPM=C2=A0= <xiong.quan@z= te.com.cn>=C2=A0wrote:

>
>=C2=A0Hi=C2=A0Cheng=C2= =A0and=C2=A0Co-authors,
>
>
>=C2=A0I=C2=A0have=C2=A0upd= ated=C2=A0the=C2=A0draft=C2=A0as=C2=A0discussed=C2=A0and=C2=A0the=C2=A0diff= =C2=A0file=C2=A0is=C2=A0attached.
>
>=C2=A0Please=C2=A0review= =C2=A0and=C2=A0comment=C2=A0and=C2=A0I=C2=A0will=C2=A0submit=C2=A0it=C2=A0b= efore=C2=A0this=C2=A0weekend!=C2=A0Thanks!
>
>
>=C2=A0B= est=C2=A0Regards,
>
>=C2=A0Quan
>
>
>=C2= =A0Original
>=C2=A0*From:=C2=A0*ChengLi=C2=A0<c.l@huawei.com>
>=C2=A0*To:= =C2=A0*=E7=86=8A=E6=B3=8900091065;dd@dhruvdhody.com=C2=A0<dd@dhruvdhody.com>;
>=C2= =A0*Cc:=C2=A0*pce@ietf.or= g=C2=A0<pce@ietf.o= rg>;draft-ietf-pce-sr-path-segment@ietf.org
>=C2=A0<<= a href=3D"mailto:draft-ietf-pce-sr-path-segment@ietf.org" target=3D"_blank"= >draft-ietf-pce-sr-path-segment@ietf.org>;
>=C2=A0*Date:=C2=A0= *2024=E5=B9=B409=E6=9C=8809=E6=97=A5=C2=A017:42
>=C2=A0*Subject:=C2= =A0**RE:=C2=A0[Pce]=C2=A0Re:=C2=A0I-D=C2=A0Action:
>=C2=A0draft-ietf-= pce-sr-path-segment-10.txt*
>
>=C2=A0Hi=C2=A0Quan,
> >
>
>=C2=A0Do=C2=A0you=C2=A0mind=C2=A0to=C2=A0lead=C2=A0t= his=C2=A0update?=C2=A0If=C2=A0yes,=C2=A0please=C2=A0update=C2=A0the=C2=A0xm= l(You=C2=A0can
>=C2=A0download=C2=A0it=C2=A0from=C2=A0the=C2=A0datatr= acker)=C2=A0and=C2=A0share=C2=A0the=C2=A0diff=C2=A0file=C2=A0for=C2=A0autho= rs=C2=A0to
>=C2=A0review.
>
>
>
>=C2=A0I= =C2=A0am=C2=A0crazy=C2=A0busy=C2=A0on=C2=A0updating=C2=A010+=C2=A0drafts=C2= =A0recently.=C2=A0If=C2=A0you=C2=A0can=C2=A0help=C2=A0on=C2=A0this,
>= =C2=A0I=C2=A0will=C2=A0be=C2=A0very=C2=A0appreciated!
>
>
= >
>=C2=A0Thanks,
>
>=C2=A0Cheng
>
> >
>
>
>=C2=A0*From:*=C2=A0xiong.quan@zte.com.cn=C2=A0<xiong.quan@zte.com.cn= >
>=C2=A0*Sent:*=C2=A0Monday,=C2=A0September=C2=A09,=C2=A0202= 4=C2=A011:23=C2=A0AM
>=C2=A0*To:*=C2=A0dd@dhruvdhody.com
>=C2=A0*Cc:*=C2=A0jmh.direct@joel= halpern.com;=C2=A0gregimirsky@gmail.com;=C2=A0pce@ietf.org;
>=C2=A0draft-ietf-pce-sr-path-segmen= t@ietf.org
>=C2=A0*Subject:*=C2=A0Re:=C2=A0[Pce]=C2=A0Re:=C2=A0I-= D=C2=A0Action:=C2=A0draft-ietf-pce-sr-path-segment-10.txt
>
> =
>
>
>
>=C2=A0Hi=C2=A0Dhruv=C2=A0and=C2=A0Joel,<= br>>
>
>
>=C2=A0Thanks=C2=A0for=C2=A0your=C2=A0sugg= estion!
>
>
>
>=C2=A0The=C2=A0adding=C2=A0texts= =C2=A0in=C2=A0my=C2=A0last=C2=A0email=C2=A0mainly=C2=A0clarify=C2=A0the=C2= =A0path=C2=A0segment=C2=A0related
>=C2=A0parameters=C2=A0(e.g=C2=A0as= sociation)=C2=A0within=C2=A0an=C2=A0SR=C2=A0policy.=C2=A0=C2=A0I=C2=A0think= =C2=A0the=C2=A0PCE
>=C2=A0communicates=C2=A0with=C2=A0the=C2=A0tail= =C2=A0instead=C2=A0of=C2=A0a=C2=A0notification,=C2=A0for=C2=A0example,=C2= =A0as
>=C2=A0figure=C2=A03=C2=A0shown,=C2=A0it=C2=A0send=C2=A0PCIniti= ate=C2=A0message=C2=A0to=C2=A0the=C2=A0egress=C2=A0PCC=C2=A0for=C2=A0PCE=C2= =A0tail
>=C2=A0notification,=C2=A0for=C2=A0example,=C2=A0as=C2=A0figu= re=C2=A03=C2=A0shown.
>
>
>
>=C2=A0I=C2=A0agree= =C2=A0that=C2=A0the=C2=A0path=C2=A0segment=C2=A0is=C2=A0the=C2=A0first=C2= =A0function=C2=A0that=C2=A0requires
>=C2=A0communication=C2=A0with=C2= =A0both=C2=A0tail=C2=A0and=C2=A0head=C2=A0end=C2=A0cause=C2=A0the=C2=A0the= =C2=A0path=C2=A0segment=C2=A0should
>=C2=A0be=C2=A0inserted=C2=A0at= =C2=A0the=C2=A0ingress=C2=A0PCC=C2=A0and=C2=A0should=C2=A0be=C2=A0recognize= d=C2=A0at=C2=A0the=C2=A0egress=C2=A0PCC


<= /div>_______________________________________________
Pce mailing list -- pce@i= etf.org
To unsubscribe send an email to pce-leave@ietf.org
--00000000000022dbab0621e44efc--