IPv6 Operations (v6ops)
-----------------------

 Charter
 Last Modified: 2006-02-18

 Current Status: Active Working Group

 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:

Posted Revised         I-D Title   <Filename>
------ ------- --------------------------------------------
Oct 2003 Jan 2006   <draft-ietf-v6ops-onlinkassumption-04.txt>
                IPv6 Neighbor Discovery On-Link Assumption Considered Harmful 

Sep 2004 Jun 2006   <draft-ietf-v6ops-ent-analysis-06.txt>
                IPv6 Enterprise Network Analysis 

Feb 2005 Oct 2005   <draft-ietf-v6ops-natpt-to-exprmntl-03.txt>
                Reasons to Move NAT-PT to Experimental 

Feb 2005 Jun 2006   <draft-ietf-v6ops-bb-deployment-scenarios-05.txt>
                ISP IPv6 Deployment Scenarios in Broadband Access Networks 

Mar 2005 Oct 2006   <draft-ietf-v6ops-nap-04.txt>
                Network Architecture Protection for IPv6 

May 2005 Oct 2006   <draft-ietf-v6ops-security-overview-06.txt>
                IPv6 Transition/Co-existence Security Considerations 

Jul 2005 Oct 2006   <draft-ietf-v6ops-ipsec-tunnels-03.txt>
                Using IPsec to Secure IPv6-in-IPv4 Tunnels 

Apr 2006 Jul 2006   <draft-ietf-v6ops-icmpv6-filtering-recs-02.txt>
                Recommendations for Filtering ICMPv6 Messages in Firewalls 

May 2006 Oct 2006   <draft-ietf-v6ops-802-16-deployment-scenarios-01.txt>
                IPv6 Deployment Scenarios in 802.16(e) Networks 

Jun 2006 Oct 2006   <draft-ietf-v6ops-addcon-02.txt>
                IPv6 Unicast Address Assignment Considerations 

Jun 2006 Jun 2006   <draft-ietf-v6ops-routing-guidelines-00.txt>
                IPv6 Routing Policies Guidelines 

Jun 2006 Oct 2006   <draft-ietf-v6ops-scanning-implications-01.txt>
                IPv6 Implications for Network Scanning 

Oct 2006 Oct 2006   <draft-ietf-v6ops-campus-transition-00.txt>
                IPv6 Campus Transition Scenario Description and Analysis 

 Request For Comments:

  RFC   Stat Published     Title
------- -- ----------- ------------------------------------
RFC3574 I    Aug 2003    Transition Scenarios for 3GPP Networks 

RFC3750 I    Apr 2004    Unmanaged Networks IPv6 Transition Scenarios 

RFC3793 I    Jun 2004    Survey of IPv4 Addresses in Currently Deployed IETF 
                       Sub-IP Area Standards 

RFC3789 I    Jun 2004    Introduction to the Survey of IPv4 Addresses in 
                       Currently Deployed IETF Standards 

RFC3790 I    Jun 2004    Survey of IPv4 Addresses in Currently Deployed IETF 
                       Internet Area Standards 

RFC3791 I    Jun 2004    Survey of IPv4 Addresses in Currently Deployed IETF 
                       Routing Area Standards 

RFC3792 I    Jun 2004    Survey of IPv4 Addresses in Currently Deployed IETF 
                       Security Area Standards 

RFC3794 I    Jun 2004    Survey of IPv4 Addresses in Currently Deployed IETF 
                       Transport Area Standards 

RFC3795 I    Jun 2004    Survey of IPv4 Addresses in Currently Deployed IETF 
                       Application Area Standards 

RFC3796 I    Jun 2004    Survey of IPv4 Addresses in Currently Deployed IETF 
                       Operations & Management Area Standards 

RFC3904 I    Sep 2004    Evaluation of Transition Mechanisms for Unmanaged 
                       Networks 

RFC3964 I    Dec 2004    Security Considerations for 6to4 

RFC4038 I    Mar 2005    Application Aspects of IPv6 Transition 

RFC4029 I    Mar 2005    Scenarios and Analysis for Introducing IPv6 into ISP 
                       Networks 

RFC4057 I    Jun 2005    IPv6 Enterprise Network Scenarios 

RFC4192 I    Sep 2005    Procedures for Renumbering an IPv6 Network without a 
                       Flag Day 

RFC4215 I    Oct 2005    Analysis on IPv6 Transition in Third Generation 
                       Partnership Project (3GPP) Networks 

RFC4213Standard  Oct 2005    Basic Transition Mechanisms for IPv6 Hosts and Routers 

RFC4554 I    Jun 2006    Use of VLANs for IPv4-IPv6 Coexistence in Enterprise 
                       Networks