ICYMI — FYI
The IESG chartered this new WG. Please look at the charter below — there will be close coordination between spring and srv6ops. Join the srv6ops mailing list if you’re interestef in SRv6 deployments. The chairs recently issued a call for agenda items for their first meeting at IETF 120: https://mailarchive.ietf.org/arch/msg/srv6ops/b8uHUF4TmQ0ZcTUrWVfZNVdOjF0/ Alvaro. On June 14, 2024 at 1:31:36 PM, The IESG (iesg-secret...@ietf.org) wrote: A new IETF WG has been formed in the Operations and Management Area. For additional information, please contact the Area Directors or the WG Chairs. SRv6 Operations (srv6ops) ----------------------------------------------------------------------- Current status: Proposed WG Chairs: Dhruv Dhody <dhruv.i...@gmail.com> Weiqiang Cheng <chengweiqi...@chinamobile.com> Dan Voyer <daniel.vo...@bell.ca> Assigned Area Director: Jim Guichard <james.n.guich...@futurewei.com> Operations and Management Area Directors: Warren Kumari <war...@kumari.net> Mahesh Jethanandani <mjethanand...@gmail.com> Mailing list: Address: srv6...@ietf.org To subscribe: https://mailman3.ietf.org/mailman3/lists/srv6ops.ietf.org/ Archive: https://mailarchive.ietf.org/arch/browse/srv6ops/ Group page: https://datatracker.ietf.org/group/srv6ops/ Charter: https://datatracker.ietf.org/doc/charter-ietf-srv6ops/ # Charter for SRv6 Operations (SRv6OPS) The Segment Routing (SR) instantiation on the IPv6 data plane is known as SRv6. ## Objective: The SRv6OPS Working Group (WG) is dedicated to the operational aspects of deploying and managing SRv6 networks. Our mission includes: * Being a forum for network operators to discuss operational matters in SRv6 networks. * Identifying and addressing operational challenges encountered during SRv6 deployments. Additionally, developing operational guidelines to ensure secure, reliable, efficient, and scalable SRv6 network operations. ## Scope: The SRv6OPS WG is dedicated to creating informational documents that provide deployment guidance, address operational issues, and identify gaps. The development of protocols and protocol extensions is beyond the scope of the SRv6OPS WG. The chairs of the SRv6OPS WG will consult with the responsible Area Director (AD) before adopting documents that discuss operational considerations and guidance for SRv6-related technologies still under development in other WGs (such as SPRING and 6MAN). Presentations on relevant operational topics and discussions aimed at gathering feedback from the operator community deploying SRv6 are encouraged. The SRv6OPS WG scope includes: * Operational Issues and Requirements: Addressing IPv6 address planning for SRv6 Segment Identifiers (SIDs), protection, inter-domain, and interworking with other technologies. The WG may choose not to publish requirements as an RFC, but maintain them in a draft form or a collaborative WG space. * Deployment Scenarios: Discussing operational considerations for various network environments and use cases. * SRv6 Network Management Guidance: Providing insights on configuration, observability, service assurance, and performance optimization. ## Key Deliverables: The SRv6OPS WG will focus on the following items: * Documenting operational or management issues encountered during SRv6 deployment. * Documenting SRv6 deployment experiences, including different deployment scenarios (metro, core, and enterprise networks), scalability, and inter-domain implementations. * Providing recommendations and guidance for various aspects such as IPv6 address planning, block size allocation, and the division of global/local identifiers block (GIB/LIB) for SRv6 SIDs, both with and without SRv6 compression techniques. * Providing SRv6 network management guidance for configuration, automation, and performance optimization. * Developing SRv6 network observability guidance for service assurance and troubleshooting. ## Relationships with Other WGs: The SRv6OPS WG will cooperate with other WGs as necessary. Key interactions include (but are not limited to): * SPRING WG: Close cooperation on SRv6 protocol extensions, new requirements, and operational considerations. * V6OPS WG: Cooperation on operational guidance and addressing deployment challenges. * 6MAN WG: Cooperation on core IPv6 functionalities, requirements, and operational considerations. * BESS WG: Cooperation on SRv6-based protocol extensions for BGP-enabled services, new service transport requirements, and operational considerations. * IDR WG: Cooperation on SRv6-based BGP extensions, new SRv6-based attributes and encodings, and operational considerations. * PCE WG: Cooperation on SRv6-based PCEP extensions, new SRv6-based attributes and encodings, and operational considerations. * LSR WG: Cooperation on SRv6-based IGP protocol extensions, new SRv6-based attributes and encodings, and operational considerations. The chairs will ensure that Working Group Last Call (WGLC) and Adoption notices are cross-posted to the relevant WGs. Milestones: Dec 2024 - Adopt a document describing operational and management issues encountered during SRv6 network deployment. Mar 2025 - Adopt a document describing SRv6 network deployment scenarios and related operational considerations. Mar 2025 - Adopt a document that makes SRv6 operational recommendations. _______________________________________________ IETF-Announce mailing list -- ietf-annou...@ietf.org To unsubscribe send an email to ietf-announce-le...@ietf.org
_______________________________________________ spring mailing list -- spring@ietf.org To unsubscribe send an email to spring-le...@ietf.org
