IPv6 Operations (v6ops)

Last Modified: 2006-02-18

Additional information is available at tools.ietf.org/wg/v6ops

Chair(s):

Fred Baker <fred.baker@cisco.com>

Kurt Lindqvist <kurtis@kurtis.pp.se>

Operations and Management Area Director(s):

Dan Romascanu <dromasca@avaya.com>

David Kessens <david.kessens@nokia.com>

Operations and Management Area Advisor:

David Kessens <david.kessens@nokia.com>

Mailing Lists:

General Discussion: v6ops@ops.ietf.org
To Subscribe: majordomo@ops.ietf.org
In Body: subscribe v6ops
Archive: http://ops.ietf.org/lists/v6ops/

Description of Working Group:

The global deployment of IPv6 is underway, creating an IPv4/IPv6
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 while ensuring
addressing and connectivity for all IPv4 and IPv6 nodes.

The IPv6 Operations Working Group (v6ops) develops guidelines for the
operation of a shared IPv4/IPv6 Internet and provides operational
guidance on how to deploy IPv6 into existing IPv4-only networks,
as well as into new network installations.

The main focus of the v6ops WG is to look at the immediate
deployment issues; more advanced stages of deployment and transition
are a lower priority.

The goals of the v6ops working group are:

1. Solicit input from network operators and users to identify
operational issues with the IPv4/IPv6 Internet, and
determine solutions or workarounds to those issues. These issues
will be documented in Informational or BCP RFCs, or in
Internet-Drafts.

This work should primarily be conducted by those areas and WGs
which are responsible and best fit to analyze these problems, but
v6ops may also cooperate in focusing such work.

2. Publish Informational or BCP RFCs that identify potential security
risks in the operation of shared IPv4/IPv6 networks, and document
operational practices to eliminate or mitigate those risks.

This work will be done in cooperation with the Security area and
other relevant areas or working groups.

3. As a particular instance of (1) and (2), provide feedback to
the IPv6 WG regarding portions of the IPv6 specifications that
cause, or are likely to cause, operational or security concerns,
and work with the IPv6 WG to resolve those concerns. This feedback
will be published in Internet-Drafts or RFCs.

4. Publish Informational or BCP RFCs that identify and analyze
solutions
for deploying IPv6 within common network environments, such as
ISP Networks, Enterprise Networks, Unmanaged Networks (Home/Small
Office), and Cellular Networks.

These documents should serve as useful guides to network
operators and users on possible ways how to deploy IPv6 within their
existing IPv4 networks, as well as in new network installations.

These documents should not be normative guides for IPv6 deployment,
and the primary intent is not capture the needs for new solutions,
but rather describe which approaches work and which do not.

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 WG 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 WG only if
there is a substantial expression of interest from the community and
if the work clearly does not fit elsewhere in the IETF.

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

Specifying any protocols or transition mechanisms is out of scope of
the WG.

Goals and Milestones:

Done		Publish Cellular Deployment Scenarios as a WG I-D
Done		Publish Unmanaged Network Deployment Scenarios as a WG I-D
Done		Publish Survey of IPv4 Addresses in IETF Standards as WG I-D
Done		Publish Cellular Deployment Solutions as a WG I-D
Done		Publish Unmanaged Network Deployment Solutions as a WG I-D
Done		Submit Cellular Deployment Scenarios to IESG for Info
Done		Submit Unmanaged Network Deployment Scenarios to IESG for Info
Done		Publish Enterprise Deployment Scenarios as a WG I-D
Done		Submit Survey of IPv4 Addresses in IETF Standards to IESG for Info
Done		Publish ISP Deployment & Solutions as a WG I-D
Done		Submit Cellular Deployment Solutions to IESG for Info
Done		Submit Transition Mechanisms to IESG for PS
Done		Submit IPv6 Neighbor Discovery On-Link Assumption to IESG for Info
Done		Submit Dual Stack IPv6 on by Default to IESG for Informational
Done		Submit Unmanaged Network Deployment Solutions to IESG for BCP
Done		Submit ISP Deployment Scenarios & Solutions to IESG for Info
Done		Submit Application Aspects of IPv6 Transition to IESG for Informational
Done		Submit 6to4 Security Analysis to IESG for Informational
Done		Submit Enterprise Deployment Scenarios to IESG for Info
Done		Submit Renumbering Procedures to IESG for Info
Done		Adopt IPv6 Network Architecture Protection as WG item
Done		Adopt document describing how to use IPsec with draft-ietf-v6ops-mech-v2 as WG item
Done		Adopt IPv6 Security Overview as WG item
Apr 2005		Ensure draft-ietf-v6ops-v6onbydefault keeps going forward for RFC publication
Apr 2005		Submit IPv6 deployment using VLANs to IESG for Info
Apr 2005		Submit document describing issues with NAT-PT to IESG for Info
May 2005		Submit document on IPsec w/ draft-ietf-v6ops-mech-v2 to IESG for Info
Done		Adopt IPv6 deployment using VLANs to IESG for Info
Done		Adopt ISP IPv6 Deployment Scenarios in Broadband Access Networks as WG item
Jun 2005		Submit IPv6 Network Architecture Protection to IESG for Info
Jun 2005		Submit Enterprise Deployment Analysis to IESG for Info
Jul 2005		Submit IPv6 Security Overview to IESG for Info
Jul 2005		Submit ISP IPv6 Deployment Scenarios in Broadband Access Networks to IESG for Info

Internet-Drafts:

IPv6 Neighbor Discovery On-Link Assumption Considered Harmful (21835 bytes)
IPv6 Enterprise Network Analysis - IP Layer 3 Focus (77402 bytes)
Local Network Protection for IPv6 (122368 bytes)
IPv6 Transition/Co-existence Security Considerations (104432 bytes)
Using IPsec to Secure IPv6-in-IPv4 Tunnels (47647 bytes)
Recommendations for Filtering ICMPv6 Messages in Firewalls (83948 bytes)
IPv6 Deployment Scenarios in 802.16 Networks (37278 bytes)
IPv6 Unicast Address Assignment Considerations (77014 bytes)
IPv6 Routing Policies Guidelines (14986 bytes)
IPv6 Implications for Network Scanning (30620 bytes)
IPv6 Campus Transition Scenario Description and Analysis (57672 bytes)
Requirements for the address selection mechanisms (28561 bytes)
Problem Statement of Default Address Selection in Multi-prefix Environment: Operational Issues of RFC3484 Default Rules (31207 bytes)
Reasons to Move NAT-PT to Historic Status (61742 bytes)

Request For Comments:

IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.

Return to working group directory.

Return to IETF home page.