Speaking as an individual contributor.
I may be misreading this. It looks like the first draft depends upon a
definition of a valid or invalid segment list, but does not provide a
definition for that. It looks like the second draft provides a precise
definition for an invalid segment list. Do the author's of the first
draft envision some other definition of an invalid segment list? If so,
what? If not, doesn't that result in close coupling between the two drafts?
Yours,
Joel
On 8/30/2023 4:22 AM, chen....@zte.com.cn wrote:
Hi WG, Hi Ketan,
we received some comments about merging the two drafts at the IETF
117th. After discussion between the authors of the two drafts, we
believe that there are differences between the two drafts. We hope to
move forward separately, and make some distinctions in content and
title. The main difference is:
Draft #1 Link:
https://www.ietf.org/archive/id/draft-chen-spring-sr-policy-cp-validity-00.txt
This draft is for the scenario where multiple segment list are in a CP
of a SR policy. When some of the segment list become invalid and it
can not meet the required quality of service. The validity of the
current path is judged based on the set effective SL number or
effective SL weight.
Draft #2 Link:
https://datatracker.ietf.org/doc/draft-liu-spring-sr-policy-flexible-path-selection/
This draft is to check the validity of path quality for SR policies.
When the path quality of the corresponding segmentlist decreases and
fails to meet the requirements of a single path, the current path is
marked as invalid, triggering a path switch. It is applicable to both
single Seglist and multiple Seglist scenarios.
Best Regards,
Ran
_______________________________________________
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring
_______________________________________________
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring
