Hi Rob, The multicast in SR belongs to the same category as I highlighted in my last email. Just to repeat …
At IETF101, you and Bruno presented a slide based on the WG feedback on the mailing list (https://datatracker.ietf.org/meeting/101/materials/slides-101-spring-00-chairs-slides-01). During the Spring meeting, the WG agreed to add milestones to those items. In general, I see some milestones are not included in the proposed chartered text. Specifically, multicast in SR is included in that list with the "Ingress replication SID (Tree SID /spray)" bullet (and support during the WG meeting) but is missing in the proposed charter text. So, I agree with Xiejingrong and Michael highlighting the same. There is already interest and agreement shown by the WG to include multicast in SR in the charter. In the light of the above, please add a milestone for the WG to specify architecture, and the required protocol extensions for multicast in SR with MPLS and IPv6 data planes, including specification of the ingress replication SIDs (e.g., Tree SID, Spray). Nonetheless, I wholeheartedly agree that the actual protocol extension work should be done at the WG that owns the protocol. Thanks Regards … Zafar From: spring <[email protected]> on behalf of Rob Shakir <[email protected]> Date: Monday, June 4, 2018 at 12:45 PM To: Michael McBride <[email protected]> Cc: Xiejingrong <[email protected]>, "[email protected]" <[email protected]> Subject: Re: [spring] Updating the SPRING WG Charter Michael, Thanks for the comment. On Mon, Jun 4, 2018 at 9:42 AM Michael McBride <[email protected]<mailto:[email protected]>> wrote: It would be helpful, while updating the charter, to state whether multicast in SR is in/out of scope in order to know which wg to take our future work. I think this is impractical. If we state everything that is in or out of scope, we'll end up with a laundry list. The aim of the charter is to define clearly the work that the WG should focus on. It does not mean that we can never host discussion of individual drafts if they are relevant. If there are requirements, we can always recharter if something new becomes the highest priority for the industry w.r.t SR. Kind regards, r.
_______________________________________________ spring mailing list [email protected] https://www.ietf.org/mailman/listinfo/spring
