On September 5, 2024 at 10:57:33 AM, Greg Mirsky wrote: Hi Greg!
> thank you for sharing the proposed updates to the SPRING charter. It all > looks good to me. I have a minor proposal to the extend the list of the > topics on which SPRING collaborates and coordinates adding the following: > IPPM on performance measurement methods and metrics After thinking about this, I'm inclined to cut the list instead of expanding it. Yes, you're right, the WG does interact with ippm. It also interacts with pim (on p2mp segments); rift (for example) is in the process of rechartering to include (among other things) SR extensions -- so maybe we should include them too. I'm sure there are others -- and I'm also sure we will forget someone. Instead of trying to be exhaustive, we should list the *required* groups we have to coordinate with. Here's the proposed text: OLD> The SPRING WG will coordinate and collaborate with other WGs as needed. Specific expected interactions include (but may not be limited to): mpls on the MPLS data plane and associated extensions 6man on the IPv6 data plane and associated extensions lsr on OSPF and IS-IS extensions idr on BGP extensions bess on VPN control plane pce on extensions for centralized solutions teas on traffic engineering architecture rtgwg on fast-reroute technologies srv6ops on SRv6 operations NEW> The SPRING WG is expected to coordinate and collaborate closely with the following WGs: mpls on the MPLS data plane and associated extensions 6man on the IPv6 data plane and associated extensions srv6ops on SRv6 operations As needed, the WG will also collaborate with other WGs to develop extensions and other SR-related solutions. Thoughts? Thanks! Alvaro. _______________________________________________ spring mailing list -- spring@ietf.org To unsubscribe send an email to spring-le...@ietf.org
