draft-ietf-v6ops-ent-scenarios-05.txt   rfc4057.txt 
IPv6 Operations Working Group Network Working Group J. Bound, Ed.
Internet Draft Jim Bound (Editor) Request for Comments: 4057 Hewlett Packard
Document: draft-ietf-v6ops-ent-scenarios-05.txt Hewlett Packard Category: Informational June 2005
Obsoletes: draft-ietf-v6ops-ent-scenarios-04.txt
Expires: January 2005
IPv6 Enterprise Network Scenarios IPv6 Enterprise Network Scenarios
<draft-ietf-v6ops-ent-scenarios-05.txt> Status of This Memo
Status of this Memo
By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been
disclosed, and any of which I become aware will be disclosed, in
accordance with RFC 3668.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet-
Drafts as reference material or to cite them other than as "work
in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 10, 2005. This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2005).
Abstract Abstract
This document describes the scenarios for IPv6 deployment within This document describes the scenarios for IPv6 deployment within
enterprise networks. It defines a small set of basic enterprise enterprise networks. It defines a small set of basic enterprise
scenarios and includes pertinent questions to allow enterprise scenarios and includes pertinent questions to allow enterprise
administrators to further refine their deployment scenarios. administrators to further refine their deployment scenarios.
Enterprise deployment requirements are discussed in terms of Enterprise deployment requirements are discussed in terms of
coexistence with IPv4 nodes, networks and applications, and in coexistence with IPv4 nodes, networks and applications, and in terms
terms of basic network infrastructure requirements for IPv6 of basic network infrastructure requirements for IPv6 deployment.
deployment. The scenarios and requirements described in this The scenarios and requirements described in this document will be the
document will be the basis for further analysis to determine what basis for further analysis to determine what coexistence techniques
coexistence techniques and mechanisms are needed for enterprise and mechanisms are needed for enterprise IPv6 deployment. The
IPv6 deployment. The results of that analysis will be published in results of that analysis will be published in a separate document.
a separate document.
Table of Contents: Table of Contents
1. Introduction................................................3 1. Introduction................................................... 2
2. Terminology.................................................5 2. Terminology.................................................... 3
3. Base Scenarios..............................................6 3. Base Scenarios................................................. 4
3.1 Base Scenarios Defined.....................................7 3.1. Base Scenarios Defined................................... 4
3.2 Scenarios Network Infrastructure Components................8 3.2. Scenarios Network Infrastructure Components.............. 5
3.3 Specific Scenario Examples................................10 3.3. Specific Scenario Examples............................... 8
3.4 Applicability Statement...................................12 3.4. Applicability Statement..................................10
4. Network Infrastructure Component Requirements..............12 4. Network Infrastructure Component Requirements..................10
4.1 DNS.......................................................12 4.1. DNS......................................................11
4.2 Routing...................................................13 4.2. Routing..................................................11
4.3 Configuration of Hosts....................................13 4.3. Configuration of Hosts...................................11
4.4 Security..................................................13 4.4. Security.................................................11
4.5 Applications..............................................13 4.5. Applications.............................................12
4.6 Network Management........................................14 4.6. Network Management.......................................12
4.7 Address Planning..........................................14 4.7. Address Planning.........................................12
4.8 Multicast..................................................14 4.8. Multicast................................................12
4.9 Multihoming................................................14 4.9. Multihoming..............................................12
5. Security Considerations....................................14 5. Security Considerations........................................12
6. References.................................................14 6. Normative References...........................................13
6.1 Normative References......................................15 Acknowledgements...................................................13
6.2 Non-Normative References..................................15
Document Acknowledgments.......................................15
Author's Address...............................................16
Intellectual Property and Copyright Statements.................17
1. Introduction 1. Introduction
This document describes the scenarios for IPv6 deployment within This document describes the scenarios for IPv6 deployment within
enterprise networks. It defines a small set of basic enterprise enterprise networks. It defines a small set of basic enterprise
scenarios and includes pertinent questions to allow enterprise scenarios and includes pertinent questions to allow enterprise
administrators to further refine their deployment scenarios. administrators to further refine their deployment scenarios.
Enterprise deployment requirements are discussed in terms of Enterprise deployment requirements are discussed in terms of
coexistence with IPv4 nodes, networks and applications, and in coexistence with IPv4 nodes, networks and applications, and in terms
terms of basic network infrastructure requirements for IPv6 of basic network infrastructure requirements for IPv6 deployment.
deployment. The scenarios and requirements described in this The scenarios and requirements described in this document will be the
document will be the basis for further analysis to determine what basis for further analysis to determine what coexistence techniques
coexistence techniques and mechanisms are needed for enterprise and mechanisms are needed for enterprise IPv6 deployment. The
IPv6 deployment. The results of that analysis will be published in results of that analysis will be published in a separate document.
a separate document.
The audience for this document is the enterprise network team The audience for this document is the enterprise network team
considering deployment of IPv6. The document will be useful for considering deployment of IPv6. The document will be useful for
enterprise teams that will have to determine the IPv6 transition enterprise teams that will have to determine the IPv6 transition
strategy for their enterprise. It is expected those teams include strategy for their enterprise. It is expected those teams include
members from management, network operations, and engineering. The members from management, network operations, and engineering. The
scenarios presented provide an example set of cases the enterprise scenarios presented provide an example set of cases the enterprise
can use to build an IPv6 network scenario. can use to build an IPv6 network scenario.
To frame the discussion, the document will describe a set of To frame the discussion, this document will describe a set of
scenarios and network infrastructure for each scenario. It is scenarios each with a network infrastructure. It is impossible to
impossible to define every possible enterprise scenario that will define every possible enterprise scenario that will apply to IPv6
apply to IPv6 adoption and transition. adoption and transition.
Each enterprise will select the transition that best supports their Each enterprise will select the transition that best supports their
business requirements. Any attempt to define a default or one- business requirements. Any attempt to define a default or one-size-
size-fits-all transition scenario, will simply not work. This fits-all transition scenario, simply will not work. This document
document does not try to depict the drivers for adoption of IPv6 by does not try to depict the drivers for adoption of IPv6 by an
an enterprise. enterprise.
While it is difficult to quantify all the scenarios for an While it is difficult to quantify all the scenarios for an enterprise
enterprise network team to plan for IPv6, it is possible to depict network team to plan for IPv6, it is possible to depict a set of
a set of abstract scenarios that will assist with planning. The abstract scenarios that will assist with planning. This document
document presents three base scenarios as a general use case to be presents three base scenarios to be used as models by enterprises
used as a model as input for the enterprise to define specific defining specific scenarios.
scenarios.
The first scenario assumes the enterprise decides to deploy IPv6 in The first scenario assumes the enterprise decides to deploy IPv6 in
conjunction with IPv4. The second scenario assumes the enterprise conjunction with IPv4. The second scenario assumes the enterprise
decides to deploy IPv6 because of a specific set of applications decides to deploy IPv6 because of a specific set of applications that
the enterprise wants to use over an IPv6 network. The third it wants to use over an IPv6 network. The third scenario assumes an
scenario assumes an enterprise is building a new network or re- enterprise is building a new network or restructuring an existing
structuring an existing network and decides to deploy IPv6 as the network and decides to deploy IPv6 as the predominant protocol within
predominant protocol within the enterprise coexisting with IPv4. the enterprise coexisting with IPv4. This document then briefly
The document then briefly reviews a set of network infrastructure reviews a set of network infrastructure components that must be
components that must be analyzed, which are common to most analyzed, which are common to most enterprises.
enterprises.
The document then provides three specific scenario examples using This document then provides three specific scenario examples using
the network infrastructure components to depict the requirements. the network infrastructure components to depict the requirements.
These are common enterprise deployment cases to depict the These are common enterprise deployment cases to depict the challenges
challenges for the enterprise to transition a network to IPv6. for the enterprise to transition a network to IPv6.
The document then discusses the issues of supporting legacy Next, supporting legacy functions on the network (while the
functions on the network, while the transition is in process, and transition is in process), and the network infrastructure components
the network infrastructure components required to be analyzed by requiring analysis by the enterprise are discussed. The
the enterprise. The interoperation with legacy functions within interoperation with legacy functions within the enterprise will be
the enterprise will be required for all transition except possibly required for all transition except possibly by a new network that
by a new network that will be IPv6 from inception. The network will be IPv6 from inception. The network infrastructure components
infrastructure components will depict functions in their networks will depict functions in their networks that require consideration
that require consideration for IPv6 deployment and transition. for IPv6 deployment and transition.
Using the scenarios, network infrastructure components, and Using the scenarios, network infrastructure components, and examples
examples in the document an enterprise can define its specific in this document, an enterprise can define its specific scenario
scenario requirements. Understanding the legacy functions and requirements. Understanding the legacy functions and network
network infrastructure components required, the enterprise can infrastructure components required, the enterprise can determine the
determine the network operations required to deploy IPv6. The tools network operations required to deploy IPv6. The tools and mechanisms
and mechanisms to support IPv6 deployment operations will require to support IPv6 deployment operations will require enterprise
enterprise analysis. The analysis to determine the tools and analysis. The analysis to determine the tools and mechanisms to
mechanisms to support the scenarios will be presented in subsequent support the scenarios will be presented in subsequent document(s).
document(s).
2. Terminology 2. Terminology
Enterprise Network - A network that has multiple internal links, Enterprise Network - A network that has multiple internal links, one
one or more router connections, to one or or more router connections to one or more
more Providers and is actively managed by a Providers, and is actively managed by a network
network operations entity. operations entity.
Provider - An entity that provides services and Provider - An entity that provides services and
connectivity to the Internet or connectivity to the Internet or other private
other private external networks for the external networks for the enterprise network.
enterprise network.
IPv6 Capable - A node or network capable of supporting both IPv6 Capable - A node or network capable of supporting both
IPv6 and IPv4. IPv6 and IPv4.
IPv4 only - A node or network capable of supporting only IPv4 only - A node or network capable of supporting only
IPv4. IPv4.
IPv6 only - A node or network capable of supporting only IPv6 only - A node or network capable of supporting only
IPv6. This does not imply an IPv6 only IPv6. This does not imply an IPv6 only stack in
stack, in this document. this document.
3. Base Scenarios 3. Base Scenarios
Three base scenarios are defined to capture the essential Three base scenarios are defined to capture the essential abstraction
abstraction set for the enterprise. Each scenario has assumptions set for the enterprise. Each scenario has assumptions and
and requirements. This is not an exhaustive set of scenarios, but a requirements. This is not an exhaustive set of scenarios, but a base
base set of general cases. set of general cases.
Below we use the term network infrastructure to mean the software, Below we use the term network infrastructure to mean the software,
network operations and configuration, and the methods used to network operations and configuration, and methods used to operate a
operate a network in an enterprise. network in an enterprise.
At this time it is assumed for the base scenarios that any IPv6 For the base scenarios it is assumed that any IPv6 node is IPv6
node is IPv6 capable. capable.
3.1 Base Scenarios Defined 3.1. Base Scenarios Defined
Scenario 1: Wide-scale/total dual-stack deployment of IPv4 Scenario 1: Wide-scale/total dual-stack deployment of IPv4 and IPv6
and IPv6 capable hosts and network infrastructure. capable hosts and network infrastructure. Enterprise
Enterprise with an existing IPv4 network wants to with an existing IPv4 network wants to deploy IPv6 in
deploy IPv6 in conjunction with their IPv4 network. conjunction with their IPv4 network.
Assumptions: The IPv4 network infrastructure used has an Assumptions: The IPv4 network infrastructure used has an equivalent
equivalent capability in IPv6. capability in IPv6.
Requirements: Do not disrupt existing IPv4 network Requirements: Do not disrupt existing IPv4 network infrastructure
infrastructure assumptions with IPv6. IPv6 assumptions with IPv6. IPv6 should be equivalent or
should be equivalent or "better" than the "better" than the network infrastructure in IPv4.
network infrastructure in IPv4, however, it However, it is understood that IPv6 is not required to
is understood that IPv6 is not required to solve current network infrastructure problems, not
solve current network infrastructure problems, solved by IPv4. It may also not be feasible to deploy
not solved by IPv4. It may also not be feasible IPv6 on all parts of the network immediately.
to deploy IPv6 on all parts of the network
immediately.
Scenario 2: Sparse IPv6 dual-stack deployment in IPv4 network Scenario 2: Sparse IPv6 dual-stack deployment in IPv4 network
infrastructure. Enterprise with an existing IPv4 infrastructure. Enterprise with an existing IPv4
network wants to deploy a set of particular IPv6 network wants to deploy a set of particular IPv6
"applications" (application is voluntarily loosely "applications" (application is voluntarily loosely
defined here, e.g. peer to peer). The IPv6 defined here, e.g., peer to peer). The IPv6 deployment
deployment is limited to the minimum required to is limited to the minimum required to operate this set
operate this set of applications. of applications.
Assumptions: IPv6 software/hardware components for the Assumptions: IPv6 software/hardware components for the application
application are available, and platforms for the are available, and platforms for the application are
application are IPv6 capable. IPv6 capable.
Requirements: Do not disrupt IPv4 infrastructure. Requirements: Do not disrupt IPv4 infrastructure.
Scenario 3: IPv6-only network infrastructure with some Scenario 3: IPv6-only network infrastructure with some IPv4-capable
IPv4-capable nodes/applications needing to nodes/applications needing to communicate over the IPv6
communicate over the IPv6 infrastructure. infrastructure. Enterprise deploying a new network or
Enterprise deploying a new network or restructuring an existing network, decides IPv6 is the
re-structuring an existing network, decides IPv6 basis for most network communication. Some IPv4
is the basis for most network communication. capable nodes/applications will need to communicate
Some IPv4 capable nodes/applications will need over that infrastructure.
to communicate over that infrastructure.
Assumptions: Required IPv6 network infrastructure is available, Assumptions: Required IPv6 network infrastructure is available, or
or available over some defined timeline, available over some defined timeline, supporting the
supporting the enterprise plan. enterprise plan.
Requirements: Interoperation and Coexistence with IPv4 network Requirements: Interoperation and Coexistence with IPv4 network
network infrastructure and applications are infrastructure and applications are required for
required for communications. communications.
3.2 Scenarios Network Infrastructure Components 3.2. Scenarios Network Infrastructure Components
This section defines the network infrastructure that exists for the This section defines the network infrastructure that exists for the
above enterprise scenarios. This is not an exhaustive list, but a above enterprise scenarios. This is not an exhaustive list, but a
base list that can be expanded by the enterprise for specific base list that can be expanded by the enterprise for specific
deployment scenarios. The network infrastructure components are deployment scenarios. The network infrastructure components are
presented as functions that the enterprise must analyze as part of presented as functions that the enterprise must analyze as part of
defining their specific scenario. The analysis of these functions defining their specific scenario. The analysis of these functions
will identify actions that are required to deploy IPv6. will identify actions that are required to deploy IPv6.
Network Infrastructure Component 1 Network Infrastructure Component 1
Enterprise Provider Requirements Enterprise Provider Requirements
- Is external connectivity required? - Is external connectivity required?
- One site vs. multiple sites and are they within - One site vs. multiple sites and are they within different
different geographies? geographies?
- Leased lines or VPNs? - Leased lines or VPNs?
- If multiple sites, how is the traffic exchanged - If multiple sites, how is the traffic exchanged securely?
securely? - How many global IPv4 addresses are available to the enterprise?
- How many global IPv4 addresses are available to the - What is the IPv6 address assignment plan available from the
enterprise? provider?
- What is the IPv6 address assignment plan available
from the provider?
- What prefix delegation is required by the Enterprise? - What prefix delegation is required by the Enterprise?
- Will the enterprise be multihomed? - Will the enterprise be multihomed?
- What multihoming techniques are available from the - What multihoming techniques are available from the provider?
provider?
- Will clients within the enterprise be multihomed? - Will clients within the enterprise be multihomed?
- Does the provider offer any IPv6 services? - Does the provider offer any IPv6 services?
- What site external IPv6 routing protocols are required? - Which site-external IPv6 routing protocols are required?
- Is there an external data-center to the enterprise, - Is there an external data center to the enterprise, such as
such as servers located at the Provider? servers located at the Provider?
- Is IPv6 available using the same access links as IPv4, - Is IPv6 available using the same access links as IPv4, or
or different ones? different ones?
Network Infrastructure Component 2 Network Infrastructure Component 2
Enterprise Application Requirements Enterprise Application Requirements
- List of applications in use? - List of applications in use?
- Which applications must be moved to support IPv6 first? - Which applications must be moved to support IPv6 first?
- Can the application be upgraded to IPv6? - Can the application be upgraded to IPv6?
- Will the application have to support both IPv4 and IPv6? - Will the application have to support both IPv4 and IPv6?
- Do the enterprise platforms support both IPv4 and IPv6? - Do the enterprise platforms support both IPv4 and IPv6?
- Do the applications have issues with NAT v4-v4 and - Do the applications have issues with NAT v4-v4 and NAT v4-v6?
NAT v4-v6?
- Do the applications need globally routable IP addresses? - Do the applications need globally routable IP addresses?
- Do the applications care about dependency between IPv4 - Do the applications care about dependency between IPv4 and IPv6
and IPv6 addresses? addresses?
- Are applications run only on the internal enterprise - Are applications run only on the internal enterprise network?
network?
Network Infrastructure Component 3 Network Infrastructure Component 3
Enterprise IT Department Requirements Enterprise IT Department Requirements
- Who "owns"/"operates" the network: in house, or - Who "owns"/"operates" the network: in house or outsourced?
outsourced? - Is working remotely (i.e., through VPNs) supported?
- Is working remotely (e.g., through VPNs) supported? - Are inter-site communications required?
- Is inter-site communications required?
- Is network mobility used or required for IPv6? - Is network mobility used or required for IPv6?
- What are the requirements of the IPv6 address plan? - What are the requirements of the IPv6 address plan?
- Is there a detailed asset management database, including - Is there a detailed asset management database, including hosts,
hosts, IP/MAC addresses, etc.? IP/MAC addresses, etc.?
- What is the enterprise' approach to numbering - What is the enterprise's approach to numbering geographically
geographically separate sites which have their own separate sites that have their own Service Providers?
Service Providers? - What will be the internal IPv6 address assignment procedure?
- What will be the internal IPv6 address assignment
procedure?
- What site internal IPv6 routing protocols are required? - What site internal IPv6 routing protocols are required?
- What will be the IPv6 Network Management - What will be the IPv6 Network Management policy/procedure?
policy/procedure?
- What will be the IPv6 QOS policy/procedure? - What will be the IPv6 QOS policy/procedure?
- What will be the IPv6 Security policy/procedure? - What will be the IPv6 Security policy/procedure?
- What is the IPv6 training plan to educate the enterprise? - What is the IPv6 training plan to educate the enterprise?
- What network operations software will be impacted by IPv6? - What network operations software will be impacted by IPv6?
- DNS - DNS
- Management (SNMP & ad-hoc tools) - Management (SNMP & ad-hoc tools)
- Enterprise Network Servers Applications - Enterprise Network Servers Applications
- Mail Servers - Mail Servers
- High Availability Software for Nodes - High Availability Software for Nodes
- Directory Services - Directory Services
- Are all these software functions upgradeable to IPv6? - Are all these software functions upgradeable to IPv6?
- If not upgradeable, then what are the workarounds? - If not upgradeable, then what are the workarounds?
- Do any of the software functions store, display, or - Do any of the software functions store, display, or allow input
allow input of IP addresses? of IP addresses?
- Other services (e.g. NTP, etc.........) - Other services (e.g., NTP, etc.)
- What network hardware will be impacted by IPv6? - What network hardware will be impacted by IPv6?
- Routers/switches - Routers/switches
- Printers/Faxes - Printers/Faxes
- Firewalls - Firewalls
- Intrusion Detection - Intrusion Detection
- Load balancers - Load balancers
- VPN Points of Entry/Exit - VPN Points of Entry/Exit
- Security Servers and Services - Security Servers and Services
- Network Interconnect for Platforms - Network Interconnect for Platforms
- Intelligent Network Interface Cards - Intelligent Network Interface Cards
- Network Storage Devices - Network Storage Devices
- Are all these hardware functions upgradeable to IPv6? - Are all these hardware functions upgradeable to IPv6?
- If not, what are the workarounds? - If not, what are the workarounds?
- Do any of the hardware functions store, display, or - Do any of the hardware functions store, display, or allow input
allow input of IP addresses? of IP addresses?
- Are the nodes moving within the enterprise network? - Are the nodes moving within the enterprise network?
- Are the nodes moving outside and inside the enterprise - Are the nodes moving outside and inside the enterprise
network? network?
Network Infrastructure Component 4 Network Infrastructure Component 4
Enterprise Network Management System Enterprise Network Management System
- Performance Management Required? - Performance Management required?
- Network Management Applications Required? - Network Management applications required?
- Configuration Management Required? - Configuration Management required?
- Policy Management and Enforcement Required? - Policy Management and Enforcement required?
- Security Management Required? - Security Management required?
- Management of Transition Tools and Mechanisms? - Management of Transition Tools and Mechanisms?
- What new considerations does IPv6 create for Network - What new considerations does IPv6 create for Network Management?
Management?
Network Infrastructure Component 5 Network Infrastructure Component 5
Enterprise Network Interoperation and Coexistence Enterprise Network Interoperation and Coexistence
- What platforms are required to be IPv6 capable? - What platforms are required to be IPv6 capable?
- What network ingress and egress points to the site - What network ingress and egress points to the site are required
are required to be IPv6 capable? to be IPv6 capable?
- What transition mechanisms are needed to support - What transition mechanisms are needed to support IPv6 network
IPv6 network operations? operations?
- What policy/procedures are required to support the - What policy/procedures are required to support the transition to
transition to IPv6? IPv6?
- What policy/procedures are required to support - What policy/procedures are required to support interoperation
interoperation with legacy nodes and applications? with legacy nodes and applications?
3.3 Specific Scenario Examples 3.3. Specific Scenario Examples
This section presents a set of base scenario examples and is not an This section presents a set of base scenario examples and is not an
exhaustive list of examples. These examples were selected to exhaustive list of examples. These examples were selected to provide
provide further clarity for base scenarios within an enterprise of further clarity for base scenarios within an enterprise of a less
a less abstract nature. The example networks may use the scenarios abstract nature. The example networks may use the scenarios depicted
depicted in 3.1 and the infrastructure components in 3.2, but there in 3.1 and the infrastructure components in 3.2, but there are no
is no direct implications specifically within these example direct implications specifically within these example networks.
networks. Section 3.1, 3.2, and 3.3 should be used in unison for Section 3.1, 3.2, and 3.3 should be used in unison for enterprise
enterprise IPv6 deployment planning and analysis. IPv6 deployment planning and analysis.
Example Network A: Example Network A:
A distributed network across a number of geographically A distributed network across a number of geographically
separated campuses. separated campuses.
- External network operation. - External network operation.
- External connectivity required. - External connectivity required.
- Multiple sites connected by leased lines. - Multiple sites connected by leased lines.
- Provider independent IPv4 addresses. - Provider independent IPv4 addresses.
- ISP does not offer IPv6 service. - ISP does not offer IPv6 service.
- Private Leased Lines no Service Provider Used - Private Leased Lines no Service Provider used.
Applications run by the enterprise: Applications run by the enterprise:
- Internal Web/Mail. - Internal Web/Mail.
- File servers. - File servers.
- Java applications. - Java applications.
- Collaborative development tools. - Collaborative development tools.
- Enterprise Resource Applications. - Enterprise Resource applications.
- Multimedia Applications. - Multimedia applications.
- Financial Enterprise Applications. - Financial Enterprise applications.
- Data Warehousing Applications. - Data Warehousing applications.
Internal network operation: Internal network operation:
- In house operation of the network. - In house operation of the network.
- DHCP (v4) is used for all desktops, servers use - DHCP (v4) is used for all desktops; servers use static address
static address configuration. configuration.
- The DHCP server updates naming records for dynamic - The DHCP server that updates naming records for dynamic desktops
desktops uses dynamic DNS. uses dynamic DNS.
- A web based tool is used to enter name to address - A web based tool is used to enter name to address mappings for
mappings for statically addressed servers. statically addressed servers.
- Network management is done using SNMP. - Network management is done using SNMP.
- All routers and switches are upgradeable to IPv6. - All routers and switches are upgradeable to IPv6.
- Existing firewalls can be upgraded to support IPv6 - Existing firewalls can be upgraded to support IPv6 rules.
rules.
- Load balancers do not support IPv6, upgrade path - Load balancers do not support IPv6, upgrade path unclear.
unclear.
- Peer-2-Peer Application and Security supported. - Peer-2-Peer Application and Security supported.
- IPv4 Private address space is used within the - IPv4 Private address space is used within the enterprise.
enterprise.
Example Network B: Example Network B:
A bank running a large network supporting online A bank running a large network supporting online
transaction processing (OLTP) across a distributed transaction processing (OLTP) across a distributed
multi-sited network, with access to a central database multi-sited network, with access to a central database
on an external network from the OLTP network. on a remote network from the OLTP network.
- External connectivity not required. - External connectivity not required.
- Multiple sites connected by VPN. - Multiple sites connected by VPN.
- Multiple sites connected by Native IP protocol. - Multiple sites connected by Native IP protocol.
- Private address space used with NAT. - Private address space used with NAT.
- Connections to private exchanges. - Connections to private exchanges.
Applications in the enterprise: Applications in the enterprise:
- ATM transaction application. - ATM transaction application.
- ATM management application. - ATM management application.
- Financial Software and Database. - Financial Software and Database.
- Part of the workforce is mobile and requires - Part of the workforce is mobile and requires access to the
access to the enterprise from outside networks. enterprise from outside networks.
Internal Network Operation: Internal Network Operation:
- Existing firewalls can be upgraded to support
IPv6 rules. - Existing firewalls can be upgraded to support IPv6 rules.
- Load balancers do not support IPv6, upgrade - Load balancers do not support IPv6, upgrade path unclear.
path unclear.
- Identifying and managing each node's IP address. - Identifying and managing each node's IP address.
Example Network C: Example Network C:
A Security Defense, Emergency, or other Mission A Security Defense, Emergency, or other Mission Critical network
Critical network operation: operation:
- External network required at secure specific points. - External network required at secure specific points.
- Network is its own Internet. - Network is its own Internet.
- Network must be able to absorb ad-hoc creation of - Network must be able to absorb ad-hoc creation of sub-networks.
sub-networks.
- Entire parts of the network are completely mobile. - Entire parts of the network are completely mobile.
- All nodes on the network can be mobile - All nodes on the network can be mobile (including routers).
(including routers)
- Network high-availability is mandatory. - Network high-availability is mandatory.
- Network must be able to be managed from ad-hoc - Network must be able to be managed from ad-hoc location.
location. - All nodes must be able to be configured from stateless mode.
- All nodes must be able to be configured from stateless
mode.
Applications run by the Enterprise: Applications run by the Enterprise:
- Multimedia streaming of audio, video, and data for - Multimedia streaming of audio, video, and data for all nodes.
all nodes. - Data computation and analysis on stored and created data.
- Data computation and analysis on stored and created
data.
- Transfer of data coordinate points to sensor devices. - Transfer of data coordinate points to sensor devices.
- Data and Intelligence gathering applications from all - Data and Intelligence gathering applications from all nodes.
nodes.
Internal Network Operations: Internal Network Operations:
- All packets must be secured end-2-end with encryption. - All packets must be secured end-2-end with encryption.
- Intrusion Detection exists on all network entry points. - Intrusion Detection exists on all network entry points.
- Network must be able to bolt on to the Internet to share - Network must be able to bolt on to the Internet to share
bandwidth as required from Providers. bandwidth as required from Providers.
- VPNs can be used but NAT can never be used. - VPNs can be used, but NAT can never be used.
- Nodes must be able to access IPv4 legacy applications - Nodes must be able to access IPv4 legacy applications over IPv6
over IPv6 network. network.
3.4 Applicability Statement 3.4. Applicability Statement
The specific network scenarios selected are chosen to depict a base The specific network scenarios selected are chosen to depict a base
set of examples, and to support further analysis of enterprise set of examples, and to support further analysis of enterprise
networks. This is not a complete set of network scenarios. networks. This is not a complete set of network scenarios. Though
Regarding Example Network C, though this is a verifiable use case, Example Network C is a verifiable use case, currently the scenario
at this time the scenario defines an early adopter of enterprise defines an early adopter of enterprise networks transitioning to IPv6
networks transitioning to IPv6 as a predominant protocol strategy as a predominant protocol strategy (i.e., IPv6 Routing, Applications,
(e.g. IPv6 Routing, Applications, Security, and Operations), Security, and Operations), viewing IPv4 as legacy operations
viewing IPv4 as legacy operations immediately in the transition immediately in the transition strategy, and at this time may not be
strategy, and at this time may not be representative of many representative of many initial enterprise IPv6 deployments. Each
initial enterprise IPv6 deployments. Each enterprise planning team enterprise planning team will need to make that determination as IPv6
will need to make that determination as IPv6 deployment evolves. deployment evolves.
4. Network Infrastructure Component Requirements 4. Network Infrastructure Component Requirements
The enterprise will need to determine what network infrastructure The enterprise will need to determine which network infrastructure
components require enhancements or to be added for deployment of components require enhancements or need to be added for deployment of
IPv6. This infrastructure will need to be analyzed and understood IPv6. This infrastructure will need to be analyzed and understood as
as a critical resource to manage. The list in this section is not a critical resource to manage. The list in this section is not
exhaustive but are the essential network infrastructure components exhaustive, but contains the essential network infrastructure
to consider for the enterprise before they begin to define more components for the enterprise to consider before beginning to define
fine tuned requirements such as QOS, PKI, or Bandwidth requirements more fine-tuned requirements such as QOS, PKI, or Bandwidth
for IPv6 as examples. The components are only identified here and requirements for IPv6. The components are only identified here and
the details of the components will be discussed in the analysis their details will be discussed in the analysis document for
document for enterprise scenarios. Where there are references at enterprise scenarios. References currently available for components
this time for a component they are provided. are provided.
4.1 DNS 4.1. DNS
DNS will now have to support both IPv4 and IPv6 DNS records and the DNS will now have to support both IPv4 and IPv6 DNS records and the
enterprise will need to determine how the DNS is to be managed and enterprise will need to determine how the DNS is to be managed and
accessed, and secured. The range of DNS operational issues are out accessed, and secured. The range of DNS operational issues is beyond
of scope for this work. Users need to consider all current DNS the scope of this document. However, DNS resolution and transport
IPv4 operations and determine if those operations are supported for solutions for both IP protocols are influenced by the chosen IPv6
IPv6. However, DNS resolution and transport solutions for both IP deployment scenario. Users need to consider all current DNS IPv4
protocols are influenced by the chosen IPv6 deployment scenario. operations and determine if those operations are supported for IPv6
Users need to consider all current DNS IPv4 operations and [DNSV6].
determine if those operations are supported for IPv6 [DNSV6].
4.2 Routing 4.2. Routing
Interior and Exterior routing will be required to support both IPv4 Interior and Exterior routing will be required to support both IPv4
and IPv6 routing protocols, and the coexistence of IPv4 and IPv6 and IPv6 routing protocols, and the coexistence of IPv4 and IPv6 over
over the enterprise network. The enterprise will need to define the enterprise network. The enterprise will need to define the IPv6
the IPv6 routing topology, any ingress and egress points to routing topology, any ingress and egress points to provider networks,
provider networks, and transition mechanisms they wish to use for and transition mechanisms that they wish to use for IPv6 adoption.
IPv6 adoption. The enterprise will also need to determine what IPv6 The enterprise will also need to determine what IPv6 transition
transition mechanisms are supported by their upstream providers. mechanisms are supported by their upstream providers.
4.3 Configuration of Hosts 4.3. Configuration of Hosts
IPv6 introduces the concept of stateless autoconfiguration in IPv6 introduces the concept of stateless autoconfiguration in
addition to stateful autoconfiguration, for the configuration of addition to stateful autoconfiguration, for the configuration of
hosts within the enterprise. The enterprise will have to determine hosts within the enterprise. The enterprise will have to determine
the best method of host configuration, for their network. The the best method of host configuration for its network, if it will use
enterprise will need to determine if they are to use stateless or stateless or stateful autoconfiguration, and how autoconfiguration
stateful autoconfiguration, and how autoconfiguration is to operate will operate for DNS updates. It will also need to determine how
for DNS updates. The enterprise will need to determine how prefix prefix delegation will be done from their upstream provider and how
delegation is done from their upstream provider and how those those prefixes will be cascaded down to the enterprise IPv6 network.
prefixes are cascaded down to the enterprise IPv6 network. The The policy for DNS or choice of autoconfiguration is out of scope for
policy for DNS or choice of autoconfiguration is out of scope for this document [CONF, DHCPF, DHCPL].
this document. [CONF, DHCPF, DHCPL]
4.4 Security 4.4. Security
Current existing mechanisms used for IPv4 to provide security need Current existing mechanisms used for IPv4 to provide security need to
to be supported for IPv6 within the enterprise. IPv6 should create be supported for IPv6 within the enterprise. IPv6 should create no
no new security concerns for IPv4. The entire security new security concerns for IPv4. The entire security infrastructure
infrastructure currently used in the enterprise needs to be currently used in the enterprise needs to be analyzed against IPv6
analyzed against IPv6 deployment effect and determine what is deployment effect to determine what is supported in IPv6. Users
supported in IPv6. Users should review other security IPv6 network should review other current security IPv6 network infrastructure work
infrastructure work in the IETF and within the industry on going at in the IETF and within the industry. Users will have to work with
this time. Users will have to work with their platform and their platform and software providers to determine which IPv6
software providers to determine what IPv6 security network security network infrastructure components are supported. The
infrastructure components are supported. The security filters and security filters and firewall requirements for IPv6 need to be
firewall requirements for IPv6 need to be determined by the determined by the enterprise. The policy choice of users for
enterprise. The policy choice of users for security is out of scope security is beyond the scope of this document.
for this document.
4.5 Applications 4.5. Applications
Existing applications will need to be ported or provide proxies to Existing applications will need to be ported or provide proxies to
support both IPv4 and IPv6 [APPS]. support both IPv4 and IPv6 [APPS].
4.6 Network Management 4.6. Network Management
The addition of IPv6 network infrastructure components will need to The addition of IPv6 network infrastructure components will need to
be managed by the enterprise network operations center. Users will be managed by the enterprise network operations center. Users will
need to work with their network management platform providers to need to work with their network management platform providers to
determine what for IPv6 is supported during their planning for IPv6 determine what is supported for IPv6 while planning IPv6 adoption,
adoption, and what tools are available in the market to monitor the and which tools are available to monitor the network. Network
network. Network management will not need to support both IPv4 and management will not need to support both IPv4 and IPv6 and view nodes
IPv6 and view nodes as dual stacks. as dual stacks.
4.7 Address Planning 4.7. Address Planning
The address space within the enterprise will need to be defined and The address space within the enterprise will need to be defined and
coordinated with the routing topology of the enterprise network. coordinated with the routing topology of the enterprise network. It
It is also important to identify the pool of IPv4 address space is also important to identify the pool of IPv4 address space
available to the enterprise to assist with IPv6 transition methods. available to the enterprise to assist with IPv6 transition methods.
4.8 Multicast 4.8. Multicast
Enterprises utilizing IPv4 Multicast services will need to consider Enterprises utilizing IPv4 Multicast services will need to consider
how these services may be implemented operationally in an IPv6- how these services may be implemented operationally in an IPv6-
enabled environment. enabled environment.
4.9 Multihoming 4.9. Multihoming
At this time, current IPv6 allocation policies are mandating the At this time, current IPv6 allocation policies are mandating the
allocation of IPv6 address space from the upstream provider. If an allocation of IPv6 address space from the upstream provider. If an
enterprise is multihomed, the enterprise will have to determine how enterprise is multihomed, the enterprise will have to determine how
they wish to support multihoming. This also is an area of study it wishes to support multihoming. This also is an area of study
within the IETF and work in progress. within the IETF and work in progress.
5. Security Considerations 5. Security Considerations
This document lists scenarios for the deployment of IPv6 in This document lists scenarios for the deployment of IPv6 in
enterprise networks, and there are no security considerations enterprise networks, and there are no security considerations
associated with making such a list. associated with making such a list.
There will be security considerations for the deployment of IPv6 in There will be security considerations for the deployment of IPv6 in
each of these scenarios, but they will be addressed in the document each of these scenarios, but they will be addressed in the document
that includes the analysis of each scenario. that includes the analysis of each scenario.
6. References 6. Normative References
6.1 Normative References
[DNSV6] Durand, A., Ihren, J. and P. Savola, "Operational
Considerations and Issues with IPv6 DNS", Work in
Progress.
[CONF] Thomson, S., Narten, T., "IPv6 Stateless Autoconfiguration"
RFC 2462 December 1998.
[DHCPF] Droms, R., Bound, J., Volz, B., Lemon, T., et al. "Dynamic [DNSV6] Durand, A., Ihren, J., and P. Savola, "Operational
Host Configuration Protocol for IPv6 (DHCPv6)" RFC 3315 July Considerations and Issues with IPv6 DNS", Work in Progress.
2003.
[DHCPL] Droms, R., "Stateless Dynamic Host Configuration Protocol [CONF] Thomson, S. and T. Narten, "IPv6 Stateless Address
(DHCP) Service for IPv6" RFC 3756 April 2004. Autoconfiguration", RFC 2462, December 1998.
[APPS] Shin, M-K., Hong, Y-G., Haigino, J., Savola, P., Castro, E., [DHCPF] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and
"Application Aspects of IPv6 Transition" Work in Progress. M. Carney, "Dynamic Host Configuration Protocol for IPv6
(DHCPv6)", RFC 3315, July 2003
6.2 Non-Normative References [DHCPL] Nikander, P., Kempf, J., and E. Nordmark, "IPv6 Neighbor
Discovery (ND) Trust Models and Threats", RFC 3756, May
2004.
None at this time. [APPS] Shin, M-K., Hong, Y-G., Hagino, J., Savola, P., and E.
Castro, "Application Aspects of IPv6 Transition", RFC 4038,
March 2005.
Document Acknowledgments Acknowledgements
The Authors would like to acknowledge contributions from the The Authors would like to acknowledge contributions from the
following: IETF v6ops Working Group, Alan Beard, Brian Carpenter, following: IETF v6ops Working Group, Alan Beard, Brian Carpenter,
Alain Durand, Bob Hinden, and Pekka Savola. Alain Durand, Bob Hinden, and Pekka Savola.
Author's Address Authors' Addresses
Yanick Pouffary (Chair of Design Team) Yanick Pouffary (Chair of Design Team)
HP Competency Center HP Competency Center
950, Route des Colles, BP027, 950, Route des Colles, BP027,
06901 Sophia Antipolis CEDEX 06901 Sophia Antipolis CEDEX
FRANCE FRANCE
Phone: + 33492956285 Phone: + 33492956285
Email: Yanick.pouffary@hp.com EMail: Yanick.pouffary@hp.com
Jim Bound (Editor) Jim Bound (Editor)
Hewlett Packard Hewlett Packard
110 Spitbrook Road 110 Spitbrook Road
Nashua, NH 03062 Nashua, NH 03062
USA USA
Phone: 603.884.0062
Email: jim.bound@hp.co Phone: (603) 884-0062
EMail: jim.bound@hp.com
Marc Blanchet Marc Blanchet
Viagenie inc. Viagenie inc.
2875 boul. Laurier, bur. 300 2875 boul. Laurier, bur. 300
Ste-Foy, Quebec, Canada, G1V 2M2 Ste-Foy, Quebec, G1V 2M2
Canada
EMail: Marc.Blanchet@viagenie.qc.ca EMail: Marc.Blanchet@viagenie.qc.ca
Tony Hain Tony Hain
Cisco Systems Cisco Systems
500 108th Ave. N.E. Suite 400 500 108th Ave. N.E. Suite 400
Bellevue, Wa. 98004 Bellevue, WA 98004
Email: alh-ietf@tndh.net USA
EMail: alh-ietf@tndh.net
Paul Gilbert Paul Gilbert
Cisco Systems Cisco Systems
1 Penn Plaza, 5th floor, 1 Penn Plaza, 5th floor,
NY, NY 10119 NY, NY 10119
USA USA
Phone: 212.714.4334
Email: pgilbert@cisco.com
Phone: (212) 714-4334
EMail: pgilbert@cisco.com
Margaret Wasserman Margaret Wasserman
ThinkMagic ThingMagic
One Broadway One Broadway
Cambridge, MA 02142 Cambridge, MA 02142
(617) 758-4177 USA
margaret@thingmagic.com
Phone: (617) 758-4177
EMail: margaret@thingmagic.com
Jason Goldschmidt Jason Goldschmidt
Sun Microsystems Sun Microsystems
M/S UMPK17-103 M/S UMPK17-103
17 Network Circle 17 Network Circle
Menlo Park, CA 94025 Menlo Park, CA 94025
USA USA
Phone: (650)-786-3502
Fax: (650)-786-8250 Phone: (650) 786-3502
Email:jason.goldschmidt@sun.com Fax: (650) 786-8250
EMail: jason.goldschmidt@sun.com
Aldrin Isaac Aldrin Isaac
Bloomberg L.P. Bloomberg L.P.
499 Park Avenue 499 Park Avenue
New York, NY 10022 New York, NY 10022
USA USA
Phone: 212.940.1812
Email: aisaac@bloomberg.com Phone: (212) 940-1812
EMail: aisaac@bloomberg.com
Tim Chown Tim Chown
School of Electronics and Computer Science School of Electronics and Computer Science
University of Southampton University of Southampton
Southampton SO17 1BJ Southampton SO17 1BJ
United Kingdom United Kingdom
Email: tjc@ecs.soton.ac.uk
EMail: tjc@ecs.soton.ac.uk
Jordi Palet Martinez Jordi Palet Martinez
Consulintel Consulintel
San Jose Artesano, 1 San Jose Artesano, 1
Madrid, SPAIN Madrid, SPAIN
Phone: +34 91 151 81 99 Phone: +34 91 151 81 99
Fax: +34 91 151 81 98 Fax: +34 91 151 81 98
Email: jordi.palet@consulintel.es EMail: jordi.palet@consulintel.es
Fred Templin Fred Templin
Nokia Nokia
313 Fairchild Drive 313 Fairchild Drive
Mountain View, CA 94043 Mountain View, CA 94043
USA USA
Phone: 650.625.2331
Email: ftemplin@iprg.nokia.com Phone: (650) 625-2331
EMail: ftemplin@iprg.nokia.com
Roy Brabson Roy Brabson
IBM IBM
PO BOX 12195 PO BOX 12195
3039 Cornwallis Road 3039 Cornwallis Road
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
USA USA
Phone: +1 919 254 7332
Email: rbrabson@us.ibm.com
fi
Intellectual Property and Copyright Statements Phone: (919) 254-7332
EMail: rbrabson@us.ibm.com
Intellectual Property Statement Full Copyright Statement
Copyright (C) The Internet Society (2005).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at ietf-
ietf-ipr@ietf.org. ipr@ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgement
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 

This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/