[spring] Re: [SRv6OPS] Re: Second WG Last Call: draf t-ietf-spring-srv6-security-14 (Ends 2026-06-02)
Joel Halpern <[email protected]> Thu, 21 May 2026 14:13:19 -0400
| Newsgroups | gmane.ietf.spring,gmane.ietf.ipv6 |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============4875557770665817587==
Content-Type: multipart/alternative;
boundary="------------q6QJHVvUyV3DwGlldbLDTto5"
Content-Language: en-US
This is a multi-part message in MIME format.
--------------q6QJHVvUyV3DwGlldbLDTto5
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
(as an individual) COmmenting below.
Joel
On 5/21/2026 1:52 PM, Andrew Stone (Nokia) wrote:
> Hi SPRING WG, Authors
>
> I support publication of the document. It's well-written and an easy
> read, and I appreciate how tricky it must have been to balance scoping
> the document to SRv6 without bleeding into other technology security
> considerations.
>
> Some minor non-blocking comments and feedback:
>
>
> Introduction:
>
> The list of segments is in the SRH and may not be processed at each
> hop in the case of non-SR capable hops. So Perhaps:
>
> OLD
> "list of segments that are processed at each hop along the signaled path"
>
> NEW
> "list of segments that are processed at each SR capable hop along the
> signaled path"
>
> (or replace /capable/supporting/supported/aware etc. or equivalent)
I had missed that wording. As you say "processed at each hop" is too
strong. But I think even "processed at each SR capable hop" is too
strong. How about"list of segments that are processed at each addressed
node along the path". (Not worrying about SR capable as if they
designate a non-capable node it is still supposed to process it, even if
it can't. And removing "signaled" as we don't useusally describe the SR
path as being signaled. I think you were trying to get at this same
point by adding that word.)
Yours,
Joel
--------------q6QJHVvUyV3DwGlldbLDTto5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>(as an individual) COmmenting below.</p>
<p>Joel</p>
<div class="moz-cite-prefix">On 5/21/2026 1:52 PM, Andrew Stone
(Nokia) wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CH0PR08MB735359950E3FABD00ACAF870910E2@CH0PR08MB7353.namprd08.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div
style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hi SPRING WG, Authors</div>
<div
style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div
style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I support publication of the document. It's well-written and an
easy read, and I appreciate how tricky it must have been to
balance scoping the document to SRv6 without bleeding into other
technology security considerations.</div>
<div
style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div
style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Some minor non-blocking comments and feedback:</div>
<div
style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div
style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div
style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Introduction: </div>
<div
style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div
style="margin-right: 40px; margin-left: 40px; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
The list of segments is in the SRH and may not be processed at
each hop in the case of non-SR capable hops. So Perhaps: </div>
<div
style="direction: ltr; margin-right: 40px; margin-left: 40px; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div
style="margin-right: 40px; margin-left: 40px; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
OLD</div>
<div
style="margin-right: 40px; margin-left: 40px; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
"list of segments that are processed at each hop along the
signaled path"</div>
<div
style="direction: ltr; margin-right: 40px; margin-left: 40px; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div
style="margin-right: 40px; margin-left: 40px; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
NEW</div>
<div
style="margin-right: 40px; margin-left: 40px; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
"list of segments that are processed at each SR capable hop
along the signaled path"</div>
<div
style="direction: ltr; margin-right: 40px; margin-left: 40px; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div
style="margin-right: 80px; margin-left: 80px; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
(or replace /capable/supporting/supported/aware etc. or
equivalent)</div>
</blockquote>
<p>I had missed that wording. As you say "processed at each hop" is
too strong. But I think even "processed at each SR capable hop"
is too strong. How about"list of segments that are processed at
each addressed node along the path". (Not worrying about SR
capable as if they designate a non-capable node it is still
supposed to process it, even if it can't. And removing "signaled"
as we don't useusally describe the SR path as being signaled. I
think you were trying to get at this same point by adding that
word.)</p>
<p>Yours,</p>
<p>Joel</p>
<blockquote type="cite"
cite="mid:CH0PR08MB735359950E3FABD00ACAF870910E2@CH0PR08MB7353.namprd08.prod.outlook.com">
<div
style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="white-space: pre-wrap">
</span></div>
</blockquote>
</body>
</html>
--------------q6QJHVvUyV3DwGlldbLDTto5--
--===============4875557770665817587==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18Kc3ByaW5nIG1h
aWxpbmcgbGlzdCAtLSBzcHJpbmdAaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFp
bCB0byBzcHJpbmctbGVhdmVAaWV0Zi5vcmcK
--===============4875557770665817587==--