Hi Sue and all,
I read the latest version of this document and the responses from the authors.
I think the draft is sufficiently clear and ready for adoption.
From the Spring concept, the SR policy in the composite path can be distributed
by BGP as described in [RFC9830], by PCEP as described in [RFC9862],
or through static configuration. A Parent SR Policy is the composite candidate
path that acts as a container for grouping SR Policies.
The composite candidate paths can be distributed via the PCEP (as per
[I-D.draft-ietf-pce-multipath]) and also via BGP (as per this document).
From my understanding, this document therefore fills the capability gap by
defining the required BGP extensions that enable composite SR candidate paths
to reference constituent SR Policies via their Color identifiers. There may be
no technical limit for the creating.
Best Regards,
Quan
<Greetings Spring and IDR:
<Please note that IPR may exist for this technology. If you are participating
in this discussion and know of IPR, please see the IETF IPR rules.
<The authors of draft-jiang-idr-sr-policy-composite-path-04 have requested WG
LC. During IETF-125, I spent a lengthy time discussing the issues of creating
BGP routes from any dynamic source (e.g. IGP). The authors indicated that
these BGP composite paths would come from explicit SR Policy Candidate
Policies, which are statically configured.
<This document's abstract states:
SR Policy Architecture [RFC9256] defines the concept of a Composite
Candidate Path. A regular SR Policy Candidate Path outputs traffic
to a set of Segment Lists, while an SR Policy Composite Candidate
Path outputs traffic recursively to a set of SR Policies on the same
headend. This document defines extensions to BGP to distribute SR
policies carrying composite candidate path information. So that
composite candidate paths can be installed when the SR policy is
applied.
<The authors have indicated that the source for the composite policy would be
BGP explicit SR Candidate Paths.
<The SR policy in the composite path can be distributed
by BGP as described in [RFC9830], by PCEP as described in [RFC
9862], or through static configuration.
<I have 3 groups of questions as the shepherd for this draft:
<1) Can composite SR Candidate Paths be limited to be created from only
explicit (aka Static) BGP SR Candidate path?
<< * If so, how is it done (technically)?
< * What text should be found in draft-jiang-idr-sr-policy-composite-path-04
on this limited?
< * Is it there?
<2) Is the limitation of composite path to specific BGP sources an appropriate
use of the composite concept from SPRING?
<3) How does this interact with the PCE composite CPs?
<Cheerily, Sue Hares
_______________________________________________
spring mailing list -- [email protected]
To unsubscribe send an email to [email protected]
