Skip to main content

Proposed WG SRv6 Operations (srv6ops)

WG Name SRv6 Operations
Acronym srv6ops
Area Operations and Management Area (ops)
State Proposed
Charter charter-ietf-srv6ops-00-03 Start Chartering/Rechartering (Internal Steering Group/IAB Review)
Document dependencies
Additional resources GitHub Repository
Personnel Area Director Jim Guichard
Mailing list Address
Chat Room address

Charter for proposed Working Group

Editor's note: We are in the process of trying to convert the BoF group into a WG. This means that the list address is currently incorrect, there are no chairs listed, etc... Please be patient while we turn the administrative crank...

Proposed Charter for SRv6 Operations (SRv6OPS)

The Segment Routing (SR) instantiation on the IPv6 data plane is known as SRv6.


The SRv6OPS Working Group (WG) is dedicated to the operational aspects of deploying and managing Segment Routing over IPv6 (SRv6) networks. Our mission includes:

  • Gathering input from network operators to identify operational issues in SRv6 networks.

  • Developing operational guidelines to ensure secure, reliable, efficient, and scalable SRv6 network operations.

  • Identifying and resolving operational challenges encountered during SRv6 deployments.


The SRv6OPS WG is dedicated to creating informational documents that provide deployment guidance, address operational issues, identify gaps, and explore potential operational experiments.

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 Area Director (AD) before adopting documents that discuss operational considerations and guidance for SRv6-related technologies under development in other WGs (such as SPRING and 6MAN). Discussions and presentations aimed at raising awareness of operational artefacts and 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 requirements may not be published as RFCs but may be maintained in draft form or in a collaborative Working Group space.

  • Deployment Scenarios: Considering operational considerations for various network environments and use cases.

  • SRv6 Network Management Guidance: Providing insights on configuration, observability, assurance, and performance optimization.

Key Deliverables:

The SRv6OPS WG will focus on the following items:

  • 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 essential for effective network management.

  • Providing SRv6 network management guidance for configuration, automation, and performance optimization.

  • Developing SRv6 network observability guidance for 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: Close cooperation on operational guidance and addressing deployment challenges.

  • 6MAN WG: Cooperation on core IPv6 functionalities, requirements, and operational considerations.

  • BESS WG: Close cooperation on SRv6-based protocol extensions for BGP-enabled services, new service transport requirements, and operational considerations.

  • IDR WG: Close cooperation on SRv6-based BGP extensions, new SRv6-based attributes and encodings, and operational considerations.

  • PCE WG: Close cooperation on SRv6-based PCEP extensions, new SRv6-based attributes and encodings, and operational considerations.

  • LSR WG: Close 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.