Re: [mpls] Rtgdir early review of draft-ietf-mpls-sr-epe-oam-08

[Shraddha Hegde <[e-mail]>]

I have updated the draft with the text Matthew proposed in the version -11

Rgds
Shraddha


Juniper Business Use Only
-----Original Message-----
From: Loa Andersson <[e-mail]>
Sent: Tuesday, August 22, 2023 3:47 PM
To: Matthew Bocci (Nokia) <[e-mail]>; Shraddha Hegde <[e-mail]>; [e-mail]
Cc: [e-mail]; [e-mail]
Subject: Re: Rtgdir early review of draft-ietf-mpls-sr-epe-oam-08

[External Email. Be cautious of content]


Shraddha,

I have not seen a response on this, I might have missed. If you are OK with MAtthew's proposal can you update and will start first the IPR and when that is done the WGLC.

/Loa

On 2023-08-14 15:18, Matthew Bocci (Nokia) wrote:
> Hi Shraddha
>
> Thanks for addressing most of my comments in the revised draft. I don’t see a response to my opening comment below:
>
> “However, it does rely on the head end of the SR Policy / SR-TE LSP knowing the types of the SIDs along the path.”
>
> This really relates to the following text in the draft which is buried in the “Theory of Operation” section. The ability of the head end to determine the SID type and so construct the FEC stack TLV is fundamental to whether this solution is feasible.
>
> [I-D.ietf-idr-segment-routing-te-policy<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-ietf-idr-segment-routing-te-policy-23__;!!NEt6yMaO-gk!ELDoAa3hvtqJGBQ8ZvbiOVigPiGJgSfVAkQuEolZRjfwL65NqOYmW7FCb1ZKyO7Z0vdHszv6sQ$ >] and [RFC8664<https://urldefense.com/v3/__https://www.rfc-editor.org/info/rfc8664__;!!NEt6yMaO-gk!ELDoAa3hvtqJGBQ8ZvbiOVigPiGJgSfVAkQuEolZRjfwL65NqOYmW7FCb1ZKyO7Z0vezf8_0_g$ >] do not define how to carry the details of the SID that can be used to construct the FEC. Such extensions are out of scope for this document. The node initiating the data plane monitoring may acquire the details of EPE-SIDs through BGP-LS advertisements as described in [RFC9086<https://urldefense.com/v3/__https://www.rfc-editor.org/info/rfc9086__;!!NEt6yMaO-gk!ELDoAa3hvtqJGBQ8ZvbiOVigPiGJgSfVAkQuEolZRjfwL65NqOYmW7FCb1ZKyO7Z0vce66p3-w$ >]. There may be other possible mechanisms to learn the definition of the SID from controller. Details of such mechanisms are out of scope for this document.
>
> I would propose to address this by adding a sentence up front in the introduction that states something like “This solution requires that the node constructing the target FEC stack is able to determine the type of the SIDs along the path of the LSP.”, or something similar, to help scope the applicability of the draft.
>
> Best regards
>
> Matthew
>
>
>
> From: Shraddha Hegde <[e-mail]>
> Date: Monday, 14 August 2023 at 11:17
> To: Matthew Bocci (Nokia) <[e-mail]>, [e-mail]
> <[e-mail]>
> Cc: [e-mail]
> <[e-mail]>, [e-mail]
> <[e-mail]>
> Subject: RE: Rtgdir early review of draft-ietf-mpls-sr-epe-oam-08 [You
> don't often get email from [e-mail]. Learn why this is
> important at
> https://urldefense.com/v3/__https://aka.ms/LearnAboutSenderIdentificat
> ion__;!!NEt6yMaO-gk!ELDoAa3hvtqJGBQ8ZvbiOVigPiGJgSfVAkQuEolZRjfwL65NqO
> YmW7FCb1ZKyO7Z0vfE7QtzVA$  ]
>
> CAUTION: This is an external email. Please be very careful when clicking links or opening attachments. See the URL nok.it/ext for additional information.
>
>
>
> Hi Matthew,
>
> Thank you for careful review and comments.
> Pls see inline for replies..
>
> I have posted -09 version with updates.
> Let me know any further comments.
>
> Rgds
> Shraddha
>
>
> Juniper Business Use Only
> -----Original Message-----
> From: Matthew Bocci via Datatracker <[e-mail]>
> Sent: Tuesday, August 8, 2023 7:29 PM
> To: [e-mail]
> Cc: [e-mail]; [e-mail]
> Subject: Rtgdir early review of draft-ietf-mpls-sr-epe-oam-08
>
> [External Email. Be cautious of content]
>
>
> Reviewer: Matthew Bocci
> Review result: Has Nits
>
> RtgDir Early review: draft-ietf-mpls-sr-epe-oam-08.txt
>
> Hello
>
> I have been selected to do a routing directorate “early” review of
> this draft.
> https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-foo
> -name/__;!!NEt6yMaO-gk!DHrhtn6R3nI56afrsFP8kYO_p0FvEFYRLjw5YylcakWYc2q
> 5QCytHRyn7o9cVE0zOhb0wtzKi3uIZ-rn$<https://urldefense.com/v3/__https:/
> datatracker.ietf.org/doc/draft-foo-name/__;!!NEt6yMaO-gk!DHrhtn6R3nI56
> afrsFP8kYO_p0FvEFYRLjw5YylcakWYc2q5QCytHRyn7o9cVE0zOhb0wtzKi3uIZ-rn$>
>
> The routing directorate will, on request from the working group chair, perform an “early” review of a draft before it is submitted for publication to the IESG. The early review can be performed at any time during the draft’s lifetime as a working group document. The purpose of the early review depends on the stage that the document has reached.
>
> As this document is in working group last call, my focus for the review was to determine whether the document is ready to be published. Please consider my comments along with the other working group last call comments.
>
> For more information about the Routing Directorate, please see
> https://urldefense.com/v3/__https://wiki.ietf.org/en/group/rtg/RtgDir_
> _;!!NEt6yMaO-gk!DHrhtn6R3nI56afrsFP8kYO_p0FvEFYRLjw5YylcakWYc2q5QCytHR
> yn7o9cVE0zOhb0wtzKix3GFrlE$<https://urldefense.com/v3/__https:/wiki.ie
> tf.org/en/group/rtg/RtgDir__;!!NEt6yMaO-gk!DHrhtn6R3nI56afrsFP8kYO_p0F
> vEFYRLjw5YylcakWYc2q5QCytHRyn7o9cVE0zOhb0wtzKix3GFrlE$>
>
> Document: draft-ietf-mpls-sr-epe-oam-08.txt
> Reviewer: Matthew Bocci
> Review Date: 8th August 2023
> Intended Status: Standards Track
>
> Summary:
>
> I have some minor concerns about this document that I think should be resolved before it is submitted to the IESG.
>
> Comments:
>
> The draft is generally very readable - thanks! There are one or two paragraphs, particularly in the introduction where the definite article (the/a, etc) is missing or not used correctly. I have tried to capture some examples in my list of 'nits' below.
>
> In general, I don't have an issue with the mechanism described in the
> draft

--
Loa Andersson                        email: [e-mail]
Senior MPLS Expert                          [e-mail]
Bronze Dragon Consulting             phone: [phone]