[spring] Re: AD review of https://datatracker.ietf.org/doc/draft-ietf-spring-cs-sr-policy/

[James Guichard <[e-mail]>]

Hi Christian,

Thanks for responding so quickly. I have request IETF last-call as you have satisfied my comments.

Jim

From: Christian Schmutzer (cschmutz) <[e-mail]>
Date: Friday, December 5, 2025 at 5:07 AM
To: James Guichard <[e-mail]>
Cc: Christian Schmutzer (cschmutz) <[e-mail]>, [e-mail] <[e-mail]>, spring Chairs <[e-mail]>, spring <[e-mail]>
Subject: Re: AD review of https://datatracker.ietf.org/doc/draft-ietf-spring-cs-sr-policy/

Hi Jim,

Thank you for the review and comments.

I just uploaded a new version addressing your comments.

On this one:

396         o  may be pre-computed.

398         o  may be pre-programmed.

400         o  may have to be disjoint.

Jim> Should the above bullet points be normative language e.g, s/may/MAY

I don’t think we need normative language there. Those bullets are simply a summary of the details covered later. But, through your comment I realised in the "1:1 Protection" section we were missing a sentence at the beginning saying "The second candidate path MUST be computed disjoint to the first candidate path” … I added that now
https://datatracker.ietf.org/doc/html/draft-ietf-spring-cs-sr-policy-13#name-11-protection


Regards
Christian

On 03.12.2025, at 17:06, James Guichard <[e-mail]> wrote:

Dear Authors,

Thank you for this document. I have only minor edits/comments as follows:

  Checking references for intended status: Informational
  ----------------------------------------------------------------------------

  == Outdated reference: A later version (-11) exists of
     draft-ietf-pce-circuit-style-pcep-extensions-09

  == Outdated reference: A later version (-19) exists of
     draft-ietf-pce-sr-bidir-path-16

Jim> Please update the above references.

122       irrespective of changing network utilization other services

Jim> s/other services/from other services.

135   architecture [RFC8402] together with a centralised controller such as

Jim> s/centralised/centralized

219   ensure SLA compliance for the live of the CS-SR Policy.

Jim> s/live/life

234   *  When using configuration, a appropriate YANG model such as

Jim> s/a/an

291 4.1.  Managing Bandwidth

293   In a network, resources are represented by links of certain
294   bandwidth.  In a circuit switched network such as SONET/SDH, OTN or
295   DWDM resources (timeslots or a wavelength) are allocated for a

Jim> Please expand SONET/SDH, OTN and DWDM as none of these are well-known abbreviations as per https://www.rfc-editor.org/rpc/wiki/doku.php?id=abbrev_list

299   be sent.  This allows for the total reservations to exceed the link
300   bandwidth as well in general for link congestion.

Jim> Please correct the last sentence above. “As well in general for link congestion” does not make sense.

329   *  Allocate a dedicated Diffserv codepoint to map traffic of CS-SR

Jim> Please provide a reference for Diffserv.

396         o  may be pre-computed.

398         o  may be pre-programmed.

400         o  may have to be disjoint.

Jim> Should the above bullet points be normative language e.g, s/may/MAY

491   A and Z to initiate the candiate paths of the CS-SR Policy by sending

Jim> s/candiate/candidate

556   signaling mechanism available..

Jim> s/../.

Jim