[Pals] Re: Jim Guichard's No Objection on draft-ietf-pals- ple-12: (with COMMENT)

James Guichard <[email protected]> Tue, 3 Dec 2024 22:11:42 +0000
Newsgroups gmane.ietf.pwe3
Message-ID <MW5PR13MB54850086479ED171C31CAE27D2362@MW5PR13MB5485.namprd13.prod.outlook.com>
--===============1685930694826339999==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_MW5PR13MB54850086479ED171C31CAE27D2362MW5PR13MB5485namp_"

--_000_MW5PR13MB54850086479ED171C31CAE27D2362MW5PR13MB5485namp_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Looks good!

Jim

From: Christian Schmutzer (cschmutz) <[email protected]>
Date: Tuesday, December 3, 2024 at 4:38 PM
To: James Guichard <[email protected]>
Cc: Christian Schmutzer (cschmutz) <[email protected]>, The IESG <iesg@iet=
f.org>, [email protected] <[email protected]>, pals-c=
[email protected] <[email protected]>, [email protected] <[email protected]>, stewa=
[email protected] <[email protected]>, [email protected] <agmalis@=
gmail.com>
Subject: Re: Jim Guichard's No Objection on draft-ietf-pals-ple-12: (with C=
OMMENT)
Hi Jim,

Thank you for your review. Please see responses below via [cs]. Changes are=
 included in new -13 draft revision

Christian

> On 02.12.2024, at 00:17, Jim Guichard via Datatracker <[email protected]> =
wrote:
>
> Jim Guichard has entered the following ballot position for
> draft-ietf-pals-ple-12: No Objection
>
> 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 this
> introductory paragraph, however.)
>
>
> Please refer to https://nam11.safelinks.protection.outlook.com/?url=3Dhtt=
ps%3A%2F%2Fwww.ietf.org%2Fabout%2Fgroups%2Fiesg%2Fstatements%2Fhandling-bal=
lot-positions%2F&data=3D05%7C02%7Cjames.n.guichard%40futurewei.com%7C21dd54=
efe91c47d0320608dd13e2bfa8%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C638=
688586795604737%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjA=
uMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdat=
a=3DVyd0AF6oCsrGIfstbv71eLIotIVEJcfRvhJ9Nkc76QQ%3D&reserved=3D0<https://www=
.ietf.org/about/groups/iesg/statements/handling-ballot-positions/>
> for more information about how to handle DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fdatat=
racker.ietf.org%2Fdoc%2Fdraft-ietf-pals-ple%2F&data=3D05%7C02%7Cjames.n.gui=
chard%40futurewei.com%7C21dd54efe91c47d0320608dd13e2bfa8%7C0fee8ff2a3b24018=
9c753a1d5591fedc%7C1%7C0%7C638688586795622059%7CUnknown%7CTWFpbGZsb3d8eyJFb=
XB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldU=
IjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=3Df6bmBC1OCB0QAi2WGDQJKsDGel9Kd2RMEn6qo5SnE=
lQ%3D&reserved=3D0<https://datatracker.ietf.org/doc/draft-ietf-pals-ple/>
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Thanks for this document. Minor comments:
>
> Section 3.1 'Terminology' - 'SRH - Segment Routing Header' is defined in =
RFC
> 8754 NOT RFC 8402.

[cs] uups, cut&paste error. fixed

> Section 3.1 'Terminology' - 'SR-TE - Segment Routing Traffic Engineering
> [RFC9256]'. RFC 9256 defines Segment Routing Policy Architecture. Please =
use a
> reference that accurately reflects where you use the SR-TE term.

[cs] I did the opposite and change from "SR-TE" to "SR policies=94 and remo=
ve the entry from terminology

>
>
>

--_000_MW5PR13MB54850086479ED171C31CAE27D2362MW5PR13MB5485namp_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/of=
fice/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Aptos;
	panose-1:2 11 0 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:12.0pt;
	font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Aptos",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;
	mso-ligatures:none;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style>
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap:brea=
k-word">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt">Looks good!<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt">Jim<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt"><o:p>&nbsp;</o:p></=
span></p>
<div id=3D"mail-editor-reference-message-container">
<div>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><b><span style=3D"col=
or:black">From:
</span></b><span style=3D"color:black">Christian Schmutzer (cschmutz) &lt;c=
[email protected]&gt;<br>
<b>Date: </b>Tuesday, December 3, 2024 at 4:38 PM<br>
<b>To: </b>James Guichard &lt;[email protected]&gt;<br>
<b>Cc: </b>Christian Schmutzer (cschmutz) &lt;[email protected]&gt;, The I=
ESG &lt;[email protected]&gt;, [email protected] &lt;draft-ietf-pals=
[email protected]&gt;, [email protected] &lt;[email protected]&gt;, pals@=
ietf.org &lt;[email protected]&gt;, [email protected] &lt;stewart.bryant=
@gmail.com&gt;,
 [email protected] &lt;[email protected]&gt;<br>
<b>Subject: </b>Re: Jim Guichard's No Objection on draft-ietf-pals-ple-12: =
(with COMMENT)<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:11.0pt">Hi Jim,<br>
<br>
Thank you for your review. Please see responses below via [cs]. Changes are=
 included in new -13 draft revision<br>
<br>
Christian <br>
<br>
&gt; On 02.12.2024, at 00:17, Jim Guichard via Datatracker &lt;noreply@ietf=
.org&gt; wrote:<br>
&gt; <br>
&gt; Jim Guichard has entered the following ballot position for<br>
&gt; draft-ietf-pals-ple-12: No Objection<br>
&gt; <br>
&gt; When responding, please keep the subject line intact and reply to all<=
br>
&gt; email addresses included in the To and CC lines. (Feel free to cut thi=
s<br>
&gt; introductory paragraph, however.)<br>
&gt; <br>
&gt; <br>
&gt; Please refer to <a href=3D"https://www.ietf.org/about/groups/iesg/stat=
ements/handling-ballot-positions/">
https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.iet=
f.org%2Fabout%2Fgroups%2Fiesg%2Fstatements%2Fhandling-ballot-positions%2F&a=
mp;data=3D05%7C02%7Cjames.n.guichard%40futurewei.com%7C21dd54efe91c47d03206=
08dd13e2bfa8%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C63868858679560473=
7%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiO=
iJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&amp;sdata=3DVyd0AF=
6oCsrGIfstbv71eLIotIVEJcfRvhJ9Nkc76QQ%3D&amp;reserved=3D0</a>
<br>
&gt; for more information about how to handle DISCUSS and COMMENT positions=
.<br>
&gt; <br>
&gt; <br>
&gt; The document, along with other ballot positions, can be found here:<br=
>
&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-pals-ple/">http=
s://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fdatatracker=
.ietf.org%2Fdoc%2Fdraft-ietf-pals-ple%2F&amp;data=3D05%7C02%7Cjames.n.guich=
ard%40futurewei.com%7C21dd54efe91c47d0320608dd13e2bfa8%7C0fee8ff2a3b240189c=
753a1d5591fedc%7C1%7C0%7C638688586795622059%7CUnknown%7CTWFpbGZsb3d8eyJFbXB=
0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIj=
oyfQ%3D%3D%7C0%7C%7C%7C&amp;sdata=3Df6bmBC1OCB0QAi2WGDQJKsDGel9Kd2RMEn6qo5S=
nElQ%3D&amp;reserved=3D0</a><br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; ----------------------------------------------------------------------=
<br>
&gt; COMMENT:<br>
&gt; ----------------------------------------------------------------------=
<br>
&gt; <br>
&gt; Thanks for this document. Minor comments:<br>
&gt; <br>
&gt; Section 3.1 'Terminology' - 'SRH - Segment Routing Header' is defined =
in RFC<br>
&gt; 8754 NOT RFC 8402.<br>
<br>
[cs] uups, cut&amp;paste error. fixed<br>
<br>
&gt; Section 3.1 'Terminology' - 'SR-TE - Segment Routing Traffic Engineeri=
ng<br>
&gt; [RFC9256]'. RFC 9256 defines Segment Routing Policy Architecture. Plea=
se use a<br>
&gt; reference that accurately reflects where you use the SR-TE term.<br>
<br>
[cs] I did the opposite and change from &quot;SR-TE&quot; to &quot;SR polic=
ies=94 and remove the entry from terminology<br>
<br>
&gt; <br>
&gt; <br>
&gt; <o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_MW5PR13MB54850086479ED171C31CAE27D2362MW5PR13MB5485namp_--


--===============1685930694826339999==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KUGFscyBtYWls
aW5nIGxpc3QgLS0gcGFsc0BpZXRmLm9yZwpUbyB1bnN1YnNjcmliZSBzZW5kIGFuIGVtYWlsIHRv
IHBhbHMtbGVhdmVAaWV0Zi5vcmcK

--===============1685930694826339999==--