draft-ietf-v6ops-ent-scenarios-01.txt   draft-ietf-v6ops-ent-scenarios-02.txt 
IPv6 Operations Working Group IPv6 Operations Working Group
Internet Draft Jim Bound (Editor) Internet Draft Jim Bound (Editor)
Document: draft-ietf-v6ops-ent-scenarios-01.txt Hewlett Packard Document: draft-ietf-v6ops-ent-scenarios-02.txt Hewlett Packard
Obsoletes: draft-ietf-v6ops-ent-scenarios-00.txt Obsoletes: draft-ietf-v6ops-ent-scenarios-01.txt
Expires: July 2004 Expires: November 2004
IPv6 Enterprise Network Scenarios IPv6 Enterprise Network Scenarios
<draft-ietf-v6ops-ent-scenarios-01.txt> <draft-ietf-v6ops-ent-scenarios-02.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
This document is a submission by the Internet Protocol IPv6 Working This document is a submission by the Internet Protocol IPv6 Working
Group of the Internet Engineering Task Force (IETF). Comments should Group of the Internet Engineering Task Force (IETF). Comments should
be submitted to the ipng@sunroof.eng.sun.com mailing list. be submitted to the ipng@sunroof.eng.sun.com mailing list.
skipping to change at page 5, line 8 skipping to change at page 5, line 8
requirements. Understanding the legacy functions and network requirements. Understanding the legacy functions and network
infrastructure components required, the enterprise can determine the infrastructure components required, the enterprise can determine the
network operations required to deploy IPv6. The tools and mechanisms network operations required to deploy IPv6. The tools and mechanisms
to support IPv6 deployment operations will require enterprise to support IPv6 deployment operations will require enterprise
analysis. The analysis to determine the tools and mechanisms to analysis. The analysis to determine the tools and mechanisms to
support the scenarios will be presented in subsequent document(s). support the scenarios will be presented in subsequent 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 or more router connections, to one or more one or more router connections, to one or
Providers and is actively managed by a network more
Providers and is actively managed by a
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 external networks for the other private 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.
skipping to change at page 6, line 27 skipping to change at page 6, line 27
Scenario 1: Enterprise with an existing IPv4 network wants to deploy Scenario 1: Enterprise with an existing IPv4 network wants to deploy
IPv6 in conjunction with their IPv4 network. IPv6 in conjunction with their IPv4 network.
Assumptions: The IPv4 network infrastructure used has an equivalent Assumptions: The IPv4 network infrastructure used has an equivalent
capability in IPv6. capability in IPv6.
Requirements: Do not disrupt existing IPv4 network infrastructure Requirements: Do not disrupt existing IPv4 network infrastructure
assumptions with IPv6. IPv6 should be equivalent or assumptions with IPv6. IPv6 should be equivalent or
"better" than the network infrastructure in IPv4, "better" than the network infrastructure in IPv4,
however, it is understood that IPv6 is not required to however, it is understood that IPv6 is not required
to
solve current network infrastructure problems, solve current network infrastructure problems,
not solved by IPv4. It may also not be feasible to not solved by IPv4. It may also not be feasible to
deploy IPv6 on all parts of the network immediately. deploy IPv6 on all parts of the network immediately.
Scenario 2: Enterprise with an existing IPv4 network wants to deploy a Scenario 2: Enterprise with an existing IPv4 network wants to deploy
a
set of particular IPv6 "applications" (application is set of particular IPv6 "applications" (application is
voluntarily loosely defined here, e.g. peer to peer). voluntarily loosely defined here, e.g. peer to peer).
The IPv6 deployment is limited to the minimum required to The IPv6 deployment is limited to the minimum required
to
operate this set of applications. operate this set of applications.
Assumptions: IPv6 software/hardware components for the application Assumptions: IPv6 software/hardware components for the application
are available, and platforms for the application are available, and platforms for the application
are IPv6 capable. are IPv6 capable.
Requirements: Don't disrupt IPv4 network infrastructure. Requirements: Do not disrupt IPv4 infrastructure.
Scenario 3: Enterprise deploying a new network or re-structuring an Scenario 3: Enterprise deploying a new network or re-structuring an
existing network, decides IPv6 is the basis for existing network, decides IPv6 is the basis for
most network communication, to coexist with IPv4. most network communication, to coexist with IPv4.
Assumptions: Required IPv6 network infrastructure is available, or Assumptions: Required IPv6 network infrastructure is available, or
available over some defined timeline, supporting the available over some defined timeline, 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 required for network infrastructure and applications are required
for
communications. communications.
3.2 Scenarios Network Infrastructure Components 3.2 Scenarios Network Infrastructure Components
This section defines the network infrastructure that exist for the This section defines the network infrastructure that exist 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? - One site vs. multiple sites?
- Leased lines or VPN? - Leased lines or VPN?
- How many global IPv4 addresses are available to the - How many global IPv4 addresses are available to the
enterprise? enterprise?
- What is the IPv6 address ownership plan available - What is the IPv6 address assignment plan available
from the provider? from the provider?
- Will clients be Multihomed? - Will clients be Multihomed?
- Does the provider offer any IPv6 services? - Does the provider offer any IPv6 services?
- What site external IPv6 routing protocols are required? - What site external IPv6 routing protocols are required?
- Is there an external data-center? - Is there an external data-center?
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 NAT v4-v6? - Do the applications have issues with NAT v4-v4 and NAT v4-v6?
- Do the applications need stable IP addresses? - Do the applications need globally routable IP addresses?
- Do the applications care about dependency between IPv4 and IPv6 - Do the applications care about dependency between IPv4 and IPv6
addresses? addresses?
Network Infrastructure Component 3 Network Infrastructure Component 3
Enterprise IT Department Requirements Enterprise IT Department Requirements
- Who "owns"/"operates" the network: in house, or outsourced? - Who "owns"/"operates" the network: in house, or outsourced?
- Is a Tele-commuter work force supported? - Is a Tele-commuter work force supported?
- Is 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?
skipping to change at page 9, line 28 skipping to change at page 9, line 28
- 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 static address - DHCP (v4) is used for all desktops, servers use static address
configuration. configuration.
- The DHCP server to update naming records for dynamic desktops uses - The DHCP server to update naming records for dynamic desktops
uses
dynamic DNS. dynamic DNS.
- A web based tool is used to enter name to address mappings for - A web based tool is used to enter name to address 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 rules. - Existing firewalls can be upgraded to support IPv6 rules.
- Load balancers do not support IPv6, upgrade path unclear. - Load balancers do not support IPv6, upgrade path unclear.
- Peer-2-Peer Application and Security supported. - Peer-2-Peer Application and Security supported.
- IPv4 Private address space is used within the enterprise. - IPv4 Private address space is used within the enterprise.
Example Network B: Example Network B:
A bank running a large network supporting online transaction A bank running a large network supporting online transaction
processing (OLTP) across a distributed multi-sited network, with access processing (OLTP) across a distributed multi-sited network, with
access
to a central database on an external network from the OLTP network: to a central database on an external 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.
skipping to change at page 11, line 11 skipping to change at page 11, line 11
An IPv6 capable node, on an IPv6 link within an IPv6 routing domain, An IPv6 capable node, on an IPv6 link within an IPv6 routing domain,
wants to communicate with a legacy IPv4 application. wants to communicate with a legacy IPv4 application.
4.3 IPv6 only communicating with IPv4 4.3 IPv6 only communicating with IPv4
An IPv6 capable node wants to communicate with an IPv4 service, but An IPv6 capable node wants to communicate with an IPv4 service, but
the node is operating as IPv6 only. In order to continue support for the node is operating as IPv6 only. In order to continue support for
communications with IPv4 services an IPv6 to IPv4 translator or IPv6 communications with IPv4 services an IPv6 to IPv4 translator or IPv6
proxy is required. Introduction of such software may prevent usage proxy is required. Introduction of such software may prevent usage
of end-to-end security and applications carrying embedded IP of end-to-end security trust models and applications carrying
addressing information. Bi-directional establishment of connections embedded IP addressing information. Bi-directional establishment of
might be difficult to achieve. connections might be difficult to achieve.
5. Network Infrastructure Component Requirements 5. Network Infrastructure Component Requirements
The enterprise will need to determine what network infrastructure The enterprise will need to determine what network infrastructure
components require enhancements or to be added for deployment of components require enhancements or to be added for deployment of
IPv6. This infrastructure will need to be analyzed and understood as IPv6. This infrastructure will need to be analyzed and understood as
a critical resource to manage. a critical resource to manage.
5.1 DNS 5.1 DNS
skipping to change at page 11, line 46 skipping to change at page 11, line 46
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 over and IPv6 routing protocols, and the coexistence of IPv4 and IPv6 over
the enterprise network. The enterprise will need to define the IPv6 the enterprise network. The enterprise will need to define the IPv6
routing topology, any ingress and egress points to provider networks, routing topology, any ingress and egress points to provider networks,
and transition mechanisms they wish to use for IPv6 adoption. The and transition mechanisms they wish to use for IPv6 adoption. The
enterprise will also need to determine what IPv6 transition enterprise will also need to determine what IPv6 transition
mechanisms are supported by their upstream providers. mechanisms are supported by their upstream providers.
The choice of interior routing protocols have an impact on how the The choice of interior routing protocols have an impact on how the
routing tables will be handled: some such as OSPF will have the routing tables will be handled: some such as OSPF will have the
ships-in-the-night, others such as ISIS are integrated. This has an ships-in-the-night paradigm, others such as ISIS are integrated. This
impact on the topology and the management of the network. has an impact on the topology and the management of the network.
IPv6 capable routers should be monitored to ensure the router has IPv6 capable routers should be monitored to ensure the router has
sufficient storage for both IPv6 and IPv4 route tables. Existing sufficient storage for both IPv6 and IPv4 route tables. Existing
network design principles to limit the number of routes in the network design principles to limit the number of routes in the
network, such as prefix aggregation, become more critical with the network, such as prefix aggregation, become more critical with the
addition of IPv6 to an existing IPv4 network. addition of IPv6 to an existing IPv4 network.
5.3 Autoconfiguration 5.3 Autoconfiguration
IPv6 introduces the concept of stateless autoconfiguration in IPv6 introduces the concept of stateless autoconfiguration in
skipping to change at page 13, line 13 skipping to change at page 13, line 13
coordinated with the routing topology of the enterprise network. It coordinated with the routing topology of the enterprise network. 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.
5.8 Multicast 5.8 Multicast
Enterprises utilising IPv4 Multicast services will need to consider Enterprises utilising IPv4 Multicast services will need to consider
how these services may be presented in an IPv6-enabled environment. how these services may be presented in an IPv6-enabled environment.
First, the Multicast routing protocols will need to be considered; First, the Multicast routing protocols will need to be considered;
those such as PIM-SM may operate similarly under either protocol, but those such as PIM-SM may operate similarly under either protocol, but
in IPv6 will need to support the Multicast Listener Discovery in IPv6 nodes will need to support the Multicast Listener Discovery
protocol. protocol.
Nodes wishing to utilise Source Specific Multicast (SSM) will need to Nodes wishing to utilise Source Specific Multicast (SSM) will need to
support Multicast Listener Discovery protocol v2 (MLDv2). In support Multicast Listener Discovery protocol v2 (MLDv2). In
addition, applications written for PIM-SM may need to be modified to addition, applications written for PIM-SM may need to be modified to
use SSM. use SSM.
For inter-domain multicast, IPv6 has no equivalent of Multicast For inter-domain multicast, IPv6 has no equivalent of Multicast
Source Discovery Protocol (MSDP); alternative methods are being Source Discovery Protocol (MSDP); alternative methods are being
designed within the IETF, e.g. by embedding the Rendezvous Point designed within the IETF, e.g. by embedding the Rendezvous Point
skipping to change at page 15, line 7 skipping to change at page 15, line 7
None at this time. None at this time.
Document Acknowledgments Document Acknowledgments
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, and Bob Hinden. Alain Durand, and Bob Hinden.
Authors-Design Team Contact Information Authors-Design Team Contact Information
Send email to ent-v6net@viagenie.qc.ca to contact the design team and send comments on the draft to v6ops@ops.ietf.org. Send email to ent-v6net@viagenie.qc.ca to contact the design team and
send comments on the draft to v6ops@ops.ietf.org.
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 Phone: 603.884.0062
Email: jim.bound@hp.co Email: jim.bound@hp.co
Marc Blanchet Marc Blanchet
Hexago Viagenie inc.
2875 boul. Laurier, bur. 300 2875 boul. Laurier, bur. 300
Ste-Foy, Quebec, Canada, G1V 2M2 Ste-Foy, Quebec, Canada, G1V 2M2
EMail: Marc.Blanchet@hexago.com 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 Email: alh-ietf@tndh.net
Paul Gilbert Paul Gilbert
Cisco Systems Cisco Systems
1 Penn Plaza, 5th floor, 1 Penn Plaza, 5th floor,
 End of changes. 

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