11. Mobile IP Data Flow Binding Update Physical Movement Mobile IP Tunnel Foreign Network Home Network Mobile Node Mobile Node Correspondent Node Home Agent
12.
13.
14. Adoption: Where are we really? E-Business Mobile Telephony Laggards Bowling Alley Tornado Main Street Early Market Internet Wireless Data IPv6 Mobile Applications US DoD Mandate 2008 Innovators Early Adopters Late Majority Early Majority
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
40.
41.
42.
Hinweis der Redaktion
This session is aimed at IT managers and architects who have a basic familiarity with networking and need to assess the impact of IPv6 and/or plan for its eventual adoption. Recent reports of IPv4 address exhaustion have made many IT managers take notice. IPv6 may be technically better than IPv4 but until now most corporations have been slow to even consider a major network overhaul. They are waiting for a business case before investing in a new technology. Unfortunately, this has put them in a very precarious situation. The case for IPv6 is not an immediate return on financial investment. Rather it is a necessary step to reduce risk. Poor preparation leaves enterprises exposed to significant procurement and redesign costs when IPv6 crosses a critical threshold of adoption and displaces IPv4 in any critical points or interfaces of the enterprise. A single important customer or supplier can force a degree of IPv6 implementation. That point in time is visibly approaching. A more urgent risk already leaves critical enterprise resources vulnerable today: the default enablement of IPv6 in the most popular platforms on the market. Vista, Windows Server 2008 and most Linux distributions use IPv6 internally and automatically establish connectivity which can subvert the most powerful IPv4-based enterprise protection. Corporate networks can only be protected with a comprehensive security approach that includes IPv6. Implementing IPv6 is not a trivial exercise. It requires a complete audit of all network components, an analysis of all networked applications, a thorough dual-stack transition plan and an opportunity assessment of new protocol benefits. Fortunately, there is no urgent need for most organizations to fully embrace IPv6 at this time. The cost and effort of minimal preparation is almost negligible. On the other hand, the impact of a critical security incident, the need to write off a major equipment purchase or to fundamentally redesign a network can be devastating. The business case for widespread corporate IPv6 adoption may not yet be compelling. But we have certainly reached the time for all enterprises to consider IPv6 and assess its impact. Ignoring it any longer is alarmingly irresponsible.
The IPv6 family of protocols were designed to support a range of new functionally, examples of which are listed below. All the designs were optimized for use on 64-bit hardware and software. · Addressing: The size of an IP address increases from 32 bits in IPv4 to 128 bits in IPv6. This provides enough IP addresses such that for the foreseeable future, all nodes can have their own global unique address, enabling true peer-to-peer communication. The IPv6 addressing scheme uses hierarchically assigned addresses. This structure provides a logical separation of "who you are" (interface ID) from "where you are connected to" (prefix) thus allowing a more efficient routing. · Support for Renumbering: IPv6 brings network level support for renumbering (changing IP addresses across a network). IPv6 addresses can have lifetimes associated with them. As the lifetime of the old address expires, a new address can be automatically configured. Renumbering IPv6 Hosts is easy, just add a new Prefix to the Router and reduce the Lifetime of the old prefix. As nodes depreciate the old prefix the new Prefix will start to be used for new connections. Renumbering is designed to happen! Thus providing an end of ISP “lock in” and improved competition. · Management: IPv6 makes getting on the network is as simple as plugging a cable into your computer. IPv6 nodes automatically configure themselves using IPv6 stateless auto-configuration or a version of the dynamic host configuration protocol (DHCPv6), all without human intervention. These features make for true plug-&-play network access, putting the IT director in control and r e-focus network operation staff on running the network. · Mandated Security: Security is an add-on in IPv4 – clearly unacceptable for today’s e-commerce. IPv6 brings mandated standard security, at the network level, boosting the prospects for e-commerce. All traffic running over IP can be secured. · Efficient Mobility-support: Built-in mobility support. Every network is mobile ready . Very little infrastructure is required. Each IPv6 node can act as a correspondent and redirect packets to the new address of the mobile node. · QoS: The IPv6 packet format contains a new 20-bit traffic-flow identification field that lays the foundation for quality-of-service (QoS) functions, such as bandwidth reservation, in an open, interoperable manner. This is practically impossible in using standard Ipv4 technologies.
http://www.btgtm.com/BTGlobalTelecomNewsGTMA/Article.asp?ArticleCode=40065132&EditionCode=91632210 Critical for Comcast to be able to manage its cable modems and set top boxes after all of the IPv4 addresses are used up. 25% plan to have IPv6 in production within 2 years 10% of respondents are currently deploying or have deployed IPv6. An additional 15% of respondents plan to deploy IPv6 within the next two years. 50% do not have a clear strategy
massively scalable internet architecture underneath the compute cloud platform (since cloud platforms are completely internet based and assume sound internet infrastructure) use of mobile ipv6 to migrate or transition virtual machines across geographical boundaries / affinities inherent security between compute elements by way of IPSec in v6 aid dynamic allocation of capacity by autoconfiguring virtual machines based on demand fluctuation use of extension headers for new capabilities for cloud services However: Extension headers are problematic for hardware-based packet-forwarding/-classification engines, FYI. Also, in keeping with the end-to-end principle as expressed by Salter, et. al., the utility and desirability of extension headers in the underlying transport is contraindicated. Overencryption is actually a serious and growing security problem, as it degrades the ability to classify and detect undesirable network traffic. Autoconfiguration of computing/networking/application/service resources is orthogonal to the underlying layer-3 transport. Workload mobility <> VM mobility. Where IPv6 comes into play is that it is the solution, such as it is, for IPv4 address exhaustion. IPv6 plus LISP is probably the best solution we currently have on the table to both address exhaustion and routing-table bloat in the DFZ (which is only going to increase as more and more entities are multi-homed, not to mention the additional memory/ASIC requirements for carrying 128-bit IPv6 addresses in the RIB and mapping them into the FIB). Mobility, the rise of spimes, and M2M all require copious and flexible addressing, and a world of NAT isn’t going to the the optimal solution. Renumbering, autoconfiguration?
Sun ’s socket scrubber https://sdlc4e.sun.com/ECom/EComActionServlet;jsessionid=B39AB3694679C27E9F99934A8F86CA16
Procurement Follow lead of DoD ROI - Begin to consider. Will be hard to quantify in the initial stages but as product availability shifts the numbers are going to change The challenge is to be ready. The deadline is 2000 but we do not know if it is 1994 or November 1999. Timeline mainly influenced by stubbornness and influence of DoD et al on the industry. Cisco close to ready. Microsoft will probably be 2005/2006 timeframe with apps. Others will follow lead. Don’t invest heavily. Take precautions so that you are not caught off-guard.