[Teas] Re: Late WGLC review of draft-ietf-teas-5g-ns-ip-mpls

[Julian Lucek <[e-mail]>]

Hi Adrian

Many thanks for all the review comments. Please see a comment on section 7.2.3 below.

thanks

Julian



Juniper Business Use Only

From: Adrian Farrel <[e-mail]>
Organisation: Old Dog Consulting
Reply to: "[e-mail]" <[e-mail]>
Date: Thursday, 9 May 2024 at 10:25
To: Krzysztof Szarkowicz <[e-mail]>
Cc: 'TEAS WG' <[e-mail]>, 'TEAS WG Chairs' <[e-mail]>, "[e-mail]" <[e-mail]>, "'Mr. Mohamed Boucadair'" <[e-mail]>
Subject: RE: Late WGLC review of draft-ietf-teas-5g-ns-ip-mpls
Resent from: <[e-mail]>
Resent to: <[e-mail]>, <[e-mail]>, <[e-mail]>, <[e-mail]>, <[e-mail]>
Resent date: Thursday, 9 May 2024 at 10:24

[External Email. Be cautious of content]

Hi Krysztof and Med,

Thanks for your efforts on this.

I’ve cut out the agreed points and also the ones where you have a clear action (although I have not checked your git edits), so that this email serves as a marker of items still needing work.

Best,
Adrian

<snip>

7.2.3 seems to be floating a few ways of doing things in a rather
hypothetical way. Shouldn't you be referencing the technologies
that enable this?

[Med] There are many controllers out there which support such features. We don't want to add pointers to specific vendor implementations. However, that functionality is covered in 9522. Hence, this NEW text.

 "This approach is similar to that described in Section 4.3.1 of [RFC9522]."

[AF] OK. If your intention is to observe that many implementations do different things and that there are different ways of solving the problem, then I think you can say:

-          Many different acceptable approaches

-          Implementation choice

-          For example, an implementation might…

[JL] In our comments above, we didn’t really mean that different implementations do different things, we meant that there exist implementations that use the telemetry-driven automatic congestion avoidance that we described in section 7.3.2. We then referenced Section 4.3.1 of RFC 9522, as that describes this type of behaviour.