IPv6 Operations (v6ops)

WG Name IPv6 Operations
Acronym v6ops
Area Operations and Management Area (ops)
State Active
Charter charter-ietf-v6ops-04-01 Internal review
Dependencies Document dependency graph (SVG)
Additional URLs Wiki
Issue tracker
Personnel Chairs Fred Baker
Lee Howard
Ron Bonica
Area Director Warren Kumari
Mailing list Address v6ops@ietf.org
To subscribe https://www.ietf.org/mailman/listinfo/v6ops
Archive https://mailarchive.ietf.org/arch/browse/v6ops/
Jabber chat Room address xmpp:v6ops@jabber.ietf.org?join
Logs https://jabber.ietf.org/logs/v6ops/

Charter for Working Group

The global deployment of IPv6 is underway, creating an Internet
consisting of IPv4-only, IPv6-only and IPv4/IPv6 networks and nodes.
This deployment must be properly handled to avoid the division of
the Internet into separate IPv4 and IPv6 networks, ensuring addressing
and connectivity for all IPv4 and IPv6 nodes.

The IPv6 Operations Working Group (v6ops) develops guidelines for
the operation of IPv6 networks, and provides operational guidance
on how to deploy and operate IPv6 in new and existing networks.

The main focus of the IPv6 Operations Working Group is to look at
the deployment and operational issues in IPv6 networks.

The goals of the v6ops working group are:

1. Solicit input from network operators and users to identify
operational issues with the IPv6 Internet, and determine solutions
or workarounds to those issues.

2. Solicit input from network operators and users to identify
operational interaction issues with the IPv4 Internet, and determine
solutions or workarounds to those issues.

3. Operational solutions for identified issues should be developed
in v6ops and documented in informational or BCP drafts.

These documents should document IPv6 operational experience, including
interactions with IPv4, in dual stack networks, IPv6 networks with
IPv4 delivered as an overlay or translation service, or IPv6-only

IPv6 operational and deployment issues with specific protocols or
technologies (such as Applications, Transport Protocols, Routing
Protocols, DNS or Sub-IP Protocols) are the primary responsibility
of the groups or areas responsible for those protocols or technologies.
However, the v6ops Working Group may provide input to those
areas/groups, as needed, and cooperate with those areas/groups in
reviewing solutions to IPv6 operational and deployment problems.

Future work items within this scope will be adopted by the Working
Group only if there is a substantial expression of interest from
the community and if the work clearly does not fit elsewhere in the

There must be a continuous expression of interest for the Working
Group to work on a particular work item. If there is no longer
sufficient interest in the Working Group in a work item, the item
may be removed from the list of Working Group items.


Date Milestone
Nov 2017 Requirements for IPv6 Routers in a general purpose network
Nov 2017 Update RFC 6555 with experience
Nov 2017 Update RFC 7084 (IPv6 CE Requirements)
Nov 2017 Advice on use of ULAs in networks
Nov 2017 Prefix for use by IPv4/IPv6 translators in a network
Jul 2017 File recommendation on how to build a commercial WiFi network
Jul 2017 Describe routing choices and trade-offs for enterprise and service provider networks
Done File report on behavior of IPv6 traffic with Extension Headers
Done Update RFC 6145 Translation in view of operational experience
Done Describe and recommend mitigations for energy consumption in Neighbor Discovery
Done Describe emerging IPv6 allocations to hosts
Done Describe a Translation solution for IPv6-only data centers