Enterprise Preparation for IPv6


Published on

HP Technology Forum, June 2009, Las Vegas

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • 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.
  • http://www.ietf.org/html.charters/mip6-charter.html
  • 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?
  • http://seclists.org/lists/honeypots/2002/Oct-Dec/0105.html http://project.honeynet.org/scans/scan25/sol/NCSU/main.html http://pcworld.about.com/od/securit1/Denial-of-Service-Attacks-Inte.htm RP Murphy : DefCon : IPv6 Covert Channels James Hoagland : Blackhat : Teredo/IPv6-related flaw in Vista Joe Klein: 2001 10/1/2001 DOS bot Ipv4.ipv6.tcp.connec*on 2003 9/26/2003 Worm W32/Raleka!worm 2004 7/6/2004 Worm W32/Sdbot‐JW 2005 2/18/2005 Worm W32/Sdbot‐VJ 8/24/2005 Trojan Troj/LegMir‐AT 9/5/2005 Trojan Troj/LegMir‐AX 2006 4/28/2006 Trojan W32/Agent.ABU!tr.dldr 2007 1/2/2007 Trojan Cimuz.CS 4/10/2007 Trojan Cimuz.EL 5/4/2007 Trojan Cimuz.FH 11/5/2007 Worm W32/Nofupat 11/15/2007 Trojan Trojan.Astry 12/1/2007 Rootkit W32/Agent.EZM!tr.dldr 12/16/2007 Trojan W32/Agent.GBU!tr.dldr 12/29/2007 Worm W32/VB‐DYF 2008 4/22/2008 Trojan Troj/PWS‐ARA 5/29/2008 Trojan Generic.dx!1DAEE3B9 http://www.securecomputing.net.au/News/117402,ipv6-insecurity-is-a-clear-and-present-danger.aspx
  • 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.
  • Enterprise Preparation for IPv6

    1. 1. IPv6 for the Enterprise John Rhoton ( [email_address] ) Distinguished Technologist HP EDS CTO Office June 2009
    2. 2. Agenda <ul><li>IPv6 Overview </li></ul><ul><li>IPv6 Adoption </li></ul><ul><li>IPv6 Opportunities </li></ul><ul><li>IPv6 Risks/Threats </li></ul><ul><li>IPv6 Preparation </li></ul>
    3. 3. <ul><li>IPv6 Overview </li></ul><ul><li>IPv6 Adoption </li></ul><ul><li>IPv6 Opportunities </li></ul><ul><li>IPv6 Risks/Threats </li></ul><ul><li>IPv6 Preparation </li></ul>Agenda
    4. 4. Mysteries, Myths and Misconceptions <ul><li>What is IPv6? </li></ul><ul><li>Great solution! What’s the problem? </li></ul><ul><li>Why not just NAT? </li></ul><ul><li>中国 , 日本 , 대한민국 , 臺灣 , 新加坡 , भारत , ร ราชอาณาจักรไทย </li></ul><ul><li>ETA 2020 </li></ul><ul><li>What’s the business case? </li></ul><ul><li>No worries – it will just happen automatically </li></ul>June 19, 2009
    5. 5. What is IPv6? <ul><li>Internet Protocol (IP) is the network protocol that underpins the Internet </li></ul><ul><li>IPv6 is version 6 of the Internet Protocol (IP) </li></ul><ul><li>The current version (IPv4) was designed in the 1970s and standardized in 1981. </li></ul><ul><li>IPv4 address space will eventually &quot;runs out“. This will occur at a global level... </li></ul><ul><li>IPv6 also solves many problems IPv4 such as security, auto-configuration, and extensibility. </li></ul>June 2008
    6. 6. Need for IP address space Aren’t 4’294’967’296 addresses enough? <ul><li>Uneven and inefficient distribution!! </li></ul><ul><li>US-Centric </li></ul><ul><ul><li>India has 3 Class B </li></ul></ul><ul><ul><li>HP has 2 Class A </li></ul></ul><ul><li>Emerging Service Providers </li></ul><ul><ul><li>China Mobile has over 415 million subscribers </li></ul></ul><ul><ul><ul><li>Subscriber growth: 2 million/month </li></ul></ul></ul><ul><ul><li>Several operators have over 16 million </li></ul></ul><ul><ul><li>How can they all be simultaneously data-enabled? </li></ul></ul>ARIN advised IPv6 migration – May 2007 Class IP Address Pool A 2 24 ~16’777’216 B 2 16 ~65’536 C 2 8 ~256
    7. 7. The booming Internet <ul><li>Traditional Internet desktops </li></ul><ul><li>Data-enabled mobile phones </li></ul><ul><li>Consumer appliances </li></ul><ul><li>Embedded systems </li></ul><ul><li>Sensors </li></ul><ul><li>RFID </li></ul>
    8. 8. IANA Pool Exhaustion June 19, 2009
    9. 9. NAT Problems <ul><li>Overhead of unnecessary translation </li></ul><ul><li>Protocol incompatibilities </li></ul><ul><ul><li>E.g. IPsec </li></ul></ul><ul><li>Breaks peer-to-peer applications </li></ul><ul><ul><li>Instant messaging </li></ul></ul><ul><ul><li>Interactive games </li></ul></ul><ul><ul><li>VoIP </li></ul></ul><ul><ul><li>Real-time collaboration and sharing </li></ul></ul><ul><ul><ul><li>Netmeeting, BitTorrent, Groove </li></ul></ul></ul><ul><li>Limits implementation of application servers </li></ul><ul><ul><li>How far can you distribute your web-services? </li></ul></ul><ul><ul><li>Grid computing </li></ul></ul><ul><li>Building work-arounds for everything NAT breaks is an unnecessary and inefficient effort! </li></ul>
    10. 10. Oct 21, 2008 HP CONFIDENTIAL
    11. 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. 12. Additional Benefits <ul><li>Availability </li></ul><ul><ul><li>Anycast reduces single-point-of-failures </li></ul></ul><ul><ul><li>Removal of NAT </li></ul></ul><ul><ul><li>Authenticated access inhibits Denial of Service attacks </li></ul></ul><ul><li>Agility </li></ul><ul><ul><li>Improved Host and Router Discovery </li></ul></ul><ul><ul><li>Flexible Renumbering and Autoconfiguration </li></ul></ul><ul><li>Better Traffic Flow </li></ul><ul><ul><li>Efficient and Extensible IP datagram </li></ul></ul><ul><ul><li>Efficient Route Computation and Aggregation </li></ul></ul><ul><ul><li>Efficient IPv6 Header Compression </li></ul></ul><ul><ul><li>IP Header Flow Label to support quality of service </li></ul></ul><ul><ul><ul><li>Even when all data is encrypted </li></ul></ul></ul>
    13. 13. <ul><li>IPv6 Overview </li></ul><ul><li>IPv6 Adoption </li></ul><ul><li>IPv6 Opportunities </li></ul><ul><li>IPv6 Risks/Threats </li></ul><ul><li>IPv6 Preparation </li></ul>Agenda
    14. 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. 15. IPv6 Adoption Curve <ul><li>2008 Survey by BT: </li></ul><ul><li>2009 Lot of IPv6 planning going on at the corporate level </li></ul><ul><ul><li>http://www.indeed.com/q-ipv6-jobs.html </li></ul></ul>
    16. 16. IPv6 Drivers <ul><li>Customers are driving the requirement </li></ul><ul><ul><li>US Federal Government Procurement Mandate June 2008 Issued by the Office of Management and Budget (OMB) </li></ul></ul><ul><ul><ul><li>IPv6 support required for networked products – new purchases </li></ul></ul></ul><ul><ul><li>Several governments have similar mandates (in Asia (Japan, China CNGI, Korea, EU) </li></ul></ul><ul><ul><li>3GPP has mandated exclusive use of IPv6 for IMS (IP Multimedia Subsystems). Industry sector like Intelligent Transport System, Digital video broadcasting, smart home consortia have all recommended the use (sometime exclusively) of IPv6. </li></ul></ul><ul><ul><li>Convergence to ALL-IP (NGN (Next Generation Networks), FMC (Fixed to Mobile Convergence), Triple Play and Wireless), non computer devices/ embedded devices, sensors, building safety and security all will require IPv6 as network infrastructure. </li></ul></ul><ul><li>HP is taking an aggressive leadership stance on the IPv6 enablement dates </li></ul>June 2008
    17. 17. HP took an early Lead with IPv6 <ul><li>1993 </li></ul><ul><ul><li>HP helped define the IP Next Generation protocol in the IETF </li></ul></ul><ul><li>1995 </li></ul><ul><ul><li>First Public HP IPv6 demos & experiments </li></ul></ul><ul><li>1996 </li></ul><ul><ul><li>HP 6bone connection active </li></ul></ul><ul><li>1999 </li></ul><ul><ul><li>HP Founding member of the IPv6 Forum </li></ul></ul><ul><ul><li>Jim Bound CTO and member of the Board of Directors of IPv6 Forum </li></ul></ul><ul><ul><li>Yanick Pouffary IPv6 Forum Fellow </li></ul></ul><ul><li>2000 </li></ul><ul><ul><li>First HP IPv6-enabled server products </li></ul></ul><ul><li>2001 </li></ul><ul><ul><li>HP launched industry leading IPv6 and Mobile IPv6 solution demos </li></ul></ul><ul><li>2002 </li></ul><ul><ul><li>HP chairs North American IPv6 Task Force and is Technology Director. </li></ul></ul><ul><ul><li>NAv6TF influences Whitehouse U.S. Cyber Security Office to promote IPv6 leading to US DoD mandating the integration of IPv6 to be ready by Oct 2008 (June 2003) </li></ul></ul><ul><ul><li>HP IT launched a world wide IPv6 test bed </li></ul></ul><ul><li>2003 </li></ul><ul><ul><li>Participating in North American IPv6 interoperability Network Pilot - Moonv6 </li></ul></ul><ul><ul><li>HP helped define IPv6 ready logo </li></ul></ul><ul><ul><li>HP OpenView Network Node Manager IPv6 support </li></ul></ul><ul><ul><li>Internal HP IPv6 initiative </li></ul></ul><ul><li>2004 </li></ul><ul><ul><li>NAv6TF works with White House Office of Management (OMB) leading to June 2005 OMB mandate </li></ul></ul><ul><ul><li>HP IPv6 servers acquire IPv6 ready logo </li></ul></ul><ul><ul><li>HP ProCurve IPv6 VLANs support </li></ul></ul><ul><li>2005 </li></ul><ul><ul><li>HP was among the first printer companies to release an IPv6 product </li></ul></ul><ul><ul><li>NAv6TF works with OMB to produce OMB IPv6 transition guidance </li></ul></ul><ul><li>2006 </li></ul><ul><ul><li>HP Printer first vendor on the US DoD IPv6 Approved Product list </li></ul></ul><ul><ul><li>HP StorageWorks Division provides a customer statement of support committing support of IPv6 per the US OMB mandate </li></ul></ul><ul><li>2007 </li></ul><ul><ul><li>HP Network Automation (HPNA) (Opsware Network Automation System software) </li></ul></ul><ul><ul><ul><li>IPv4 and IPv6 devices discovery </li></ul></ul></ul>June 2008
    18. 18. HP IPv6 support <ul><li>HP is implementing IPv6 support in stages with the goal of ensuring a smooth transition and deployment where IPv6-updated products can take advantage of IPv6, without impacting existing functionality. </li></ul><ul><li>HP supports IPv6 across many of its product lines today. </li></ul><ul><li>HP platforms support transition mechanisms and gateways to interoperate with IPv4. </li></ul><ul><li>HP has already delivered IPv6 products across: </li></ul><ul><ul><li>HP Business Critical Server and ProLiant platforms (HP-UX, Tru64 UNIX®, OpenVMS, NonStop Server, Linux, and Microsoft® Windows) </li></ul></ul><ul><ul><li>ProCurve high-end switches through its ProVision ASIC offers full support for IPv6 in hardware; ProCurve Switch series 8200, 6200, 5400 and 3500 </li></ul></ul><ul><ul><li>HP Enterprise JetDirect and LaserJet printers; </li></ul></ul><ul><ul><li>HP Business Technology Optimization Network Management Center platform and Opsware Network Automation System software, now called HP Network Automation (HPNA) </li></ul></ul>June 2008
    19. 19. <ul><li>IPv6 Overview </li></ul><ul><li>IPv6 Adoption </li></ul><ul><li>IPv6 Opportunities </li></ul><ul><li>IPv6 Risks/Threats </li></ul><ul><li>IPv6 Preparation </li></ul>Agenda
    20. 20. The Path to IPv6 in the Enterprise <ul><li>IPv6 Security </li></ul><ul><ul><li>Network Monitoring and Management Infrastructure </li></ul></ul><ul><li>Mobility and Remote Access </li></ul><ul><li>Isolated IPv6-oriented applications </li></ul><ul><li>… </li></ul><ul><li>… </li></ul><ul><li>… </li></ul><ul><li>… </li></ul><ul><li>Mission-critical applications </li></ul>
    21. 21. Remote Access <ul><li>IPsec Tunnel </li></ul><ul><ul><li>Dual-factor authentication </li></ul></ul><ul><ul><li>Full network access </li></ul></ul><ul><li>Reverse Proxies </li></ul><ul><ul><li>Limited Application access </li></ul></ul><ul><ul><li>Application-specific authentication </li></ul></ul><ul><li>SSL/VPN </li></ul><ul><li>IPsec Transport </li></ul>
    22. 22. Dedicated Networks <ul><li>Factory Automation </li></ul><ul><li>Supply Chain Management </li></ul><ul><ul><li>RFID </li></ul></ul><ul><li>Sensor networks (e.g. monitoring systems) </li></ul><ul><ul><li>Require mobility, ad-hoc networking, security and a large number of simple devices </li></ul></ul><ul><li>VoIP/Multimedia services </li></ul><ul><ul><li>Requires global access, multicast, QoS, mobility </li></ul></ul><ul><li>Partner Extranets </li></ul>June 19, 2009
    23. 23. Beijing Olympics 2008 <ul><li>Surveillance </li></ul><ul><li>Sensors </li></ul><ul><li>Lighting </li></ul>June 19, 2009
    24. 24. Synergies between IPv6 and Cloud <ul><li>Massive scalability </li></ul><ul><ul><li>Hierarchical internal address space of provider </li></ul></ul><ul><ul><li>Avoid connection brokers (ALG/NAT) </li></ul></ul><ul><li>No “need” for NAT </li></ul><ul><li>Always connected user experience Mobile IPv6 </li></ul><ul><li>Customer connectivity </li></ul><ul><li>“ Easier” implementation </li></ul><ul><li>Unified Communications </li></ul>June 19, 2009
    25. 25. <ul><li>IPv6 Overview </li></ul><ul><li>IPv6 Adoption </li></ul><ul><li>IPv6 Opportunities </li></ul><ul><li>IPv6 Risks/Threats </li></ul><ul><li>IPv6 Preparation </li></ul>Agenda
    26. 26. Return on Investment? <ul><li>Long-term </li></ul><ul><ul><li>Greater efficiency </li></ul></ul><ul><ul><li>Better resilience </li></ul></ul><ul><ul><li>Facilitates new technologies </li></ul></ul><ul><li>Short-term </li></ul><ul><ul><li>Increased costs </li></ul></ul><ul><ul><li>Little visible benefit </li></ul></ul>June 19, 2009 But there is another perspective …
    27. 27. Risk Management <ul><li>Data Risks </li></ul><ul><ul><li>Valuable corporate resources exposed </li></ul></ul><ul><ul><ul><li>In unmonitored networks </li></ul></ul></ul><ul><li>Application Risks </li></ul><ul><ul><li>Reliability in an IPv6 environment </li></ul></ul><ul><li>Financial Risks </li></ul><ul><ul><li>Costs of gradual deployment versus </li></ul></ul><ul><ul><li>Sudden urgent response to unexpected event </li></ul></ul>June 19, 2009
    28. 28. Rogue Devices / Networks <ul><li>Unauthorized IPv6 devices </li></ul><ul><ul><li>Windows Vista, Linux </li></ul></ul><ul><li>Unauthorized Networks </li></ul><ul><ul><li>Internal tunnels </li></ul></ul><ul><li>Compromised Perimeter </li></ul><ul><ul><li>External tunnels </li></ul></ul><ul><li>Monitoring </li></ul><ul><li>Traffic Inspection </li></ul>What you don’t know will hurt you
    29. 29. Hacker Tools and Attacks <ul><li>IPv6-enhanced versions of old tools </li></ul><ul><ul><li>Halfscan6, netcat6, NMAP, Ethereal, Snort, TCPDump </li></ul></ul><ul><li>6to4DDos </li></ul><ul><li>Relayers (can be misused for tunnels and redirects) </li></ul><ul><ul><li>relay6, 6tunnel, nt6tunnel, asybo </li></ul></ul><ul><li>Attacks </li></ul><ul><ul><li>2003: W32.HLLW.Raleka </li></ul></ul><ul><ul><li>2005: Troj/Legmir-AT </li></ul></ul><ul><ul><li>2007: W32/Agent.EZM!tr.dldr </li></ul></ul>&quot;Last year IPv6 didn't register in scale, but now it's emerging as a concern on the security side. Attackers are going to try it or use it as a transport mechanism for botnets. IPv6 has become a problem on the operational side.“ Arbor Networks CTO Rob Malan
    30. 30. IPv6 Transition Exposure <ul><li>IPv6 is available </li></ul><ul><li>IPv6 is in use </li></ul><ul><li>IPv6 is on many private networks </li></ul><ul><li>Corporate Security </li></ul><ul><ul><li>does not monitor IPv6 </li></ul></ul><ul><li>Corporate IT </li></ul><ul><ul><li>is not familiar with IPv6 </li></ul></ul><ul><li>This is irresponsible! </li></ul>
    31. 31. Application Impact <ul><li>Socket calls (see RFC 3493, RFC 3542) </li></ul><ul><li>Are numeric IP addresses manipulated, stored or cached? </li></ul><ul><li>Colon-separator used between hostnames and port numbers? </li></ul><ul><li>Accept, parse or manipulate user-provided URLs or hostnames? </li></ul><ul><ul><li>Might contain a numeric IPv6 address) (See RFC 2732) </li></ul></ul><ul><li>Sequential enumeration of address space? </li></ul><ul><ul><li>e.g. ping-sweep to scan a subnet </li></ul></ul><ul><li>Assumption that host or interface only has one IP address? </li></ul><ul><li>Direct use of layered networking protocols (e.g. DHCP, ARP, DNS, RIP, OSPF…)? </li></ul><ul><li>SNMP collection of IPv4/IPv6 data? </li></ul>June 19, 2009
    32. 32. Potential Triggers <ul><li>Large-scale security attack </li></ul><ul><li>Technical impasse </li></ul><ul><li>Address space shortage </li></ul><ul><li>Service-provider transition </li></ul><ul><li>New geographical market </li></ul><ul><li>Government mandate </li></ul><ul><li>Supplier/customer/partner requirement </li></ul>June 19, 2009
    33. 33. Financial impact <ul><li>Investment protection </li></ul><ul><ul><li>Write off new purchases? </li></ul></ul><ul><li>Purchasing criteria can include </li></ul><ul><ul><li>Stated IPv6 support </li></ul></ul><ul><ul><li>IPv6 Logo certification </li></ul></ul><ul><ul><li>IPsec, Mobile IP, transition mechanisms … </li></ul></ul><ul><li>Ensure minimal training and awareness </li></ul><ul><li>Accelerated deployment costs more than gradual adoption! </li></ul>June 19, 2009
    34. 34. <ul><li>IPv6 Overview </li></ul><ul><li>IPv6 Adoption </li></ul><ul><li>IPv6 Opportunities </li></ul><ul><li>IPv6 Risks/Threats </li></ul><ul><li>IPv6 Preparation </li></ul>Agenda
    35. 35. Phased Deployment <ul><li>Audit </li></ul><ul><ul><li>Discovery </li></ul></ul><ul><ul><li>Policy Enforcement </li></ul></ul><ul><ul><li>Network Monitoring </li></ul></ul><ul><li>Enablement </li></ul><ul><ul><li>Network Management </li></ul></ul><ul><ul><li>Connectivity </li></ul></ul><ul><ul><ul><li>Internal-Internal </li></ul></ul></ul><ul><ul><ul><li>Internal-External </li></ul></ul></ul><ul><ul><ul><li>External-Internal </li></ul></ul></ul><ul><ul><li>Application Enablement </li></ul></ul><ul><li>Transition </li></ul>June 19, 2009
    36. 36. Discovery <ul><li>Requirements </li></ul><ul><ul><li>Security </li></ul></ul><ul><ul><li>Asset tracking </li></ul></ul><ul><li>Node discovery </li></ul><ul><ul><li>Address space enumeration </li></ul></ul><ul><ul><li>Harvesting </li></ul></ul><ul><ul><li>Sniffing </li></ul></ul><ul><li>Router discovery </li></ul><ul><ul><li>Topology mapping </li></ul></ul>June 19, 2009
    37. 37. Application audit/support <ul><li>Scan custom software </li></ul><ul><ul><li>Checkv4.exe – Microsoft </li></ul></ul><ul><ul><li>IPv6finder </li></ul></ul><ul><ul><ul><li>Open Source software, developed by HP </li></ul></ul></ul><ul><ul><li>Sun ’s socket scrubber </li></ul></ul><ul><li>Check with vendors for IPv6 support in commercial products </li></ul><ul><li>Test in your own environment! </li></ul>
    38. 38. Preparation and Planning <ul><li>IPv6 is inevitable . The key to success is timing . </li></ul><ul><li>Prepare </li></ul><ul><ul><li>Assess Security and Management requirements </li></ul></ul><ul><ul><li>Assess transition mechanisms </li></ul></ul><ul><ul><li>Train staff for roll-out and support </li></ul></ul><ul><ul><li>Procure only IPv6 compliant components </li></ul></ul><ul><li>Plan </li></ul><ul><ul><li>Analyze the ROI </li></ul></ul><ul><ul><li>Identify suitable pilots / early adopters </li></ul></ul><ul><ul><ul><li>Applications </li></ul></ul></ul><ul><ul><ul><li>User communities </li></ul></ul></ul><ul><ul><li>Obtain IPv6 prefixes </li></ul></ul><ul><ul><li>Inventory custom applications </li></ul></ul>
    39. 39. Summary <ul><li>IPv6 is about more than Address Space </li></ul><ul><li>IPv6 adoption is beginning now </li></ul><ul><ul><li>HP is a leader in IPv6 </li></ul></ul><ul><li>IPv6 is still IP </li></ul><ul><ul><li>New Network Security Model </li></ul></ul><ul><ul><li>End-to-end security </li></ul></ul><ul><ul><li>Improved Availability </li></ul></ul><ul><li>The market must begin to plan for IPv6 now </li></ul><ul><ul><li>It is easy to enable IPv6 in a simple environment </li></ul></ul><ul><li>You can ignore IPv6 but that won’t stop it! </li></ul>
    40. 40. HP IPv6 Frequently Asked Questions June 2008 www.hp.com/network/ipv6 <ul><li>What is IPv6? </li></ul><ul><li>Why do I need IPv6 when IPv4 is working fine for me? </li></ul><ul><li>What are the features and benefits of IPv6? </li></ul><ul><li>Are there any alternatives to IPv6? </li></ul><ul><li>What do I need to do to be ready for the future? </li></ul><ul><li>What is the meaning of IP capable? </li></ul><ul><li>How do I transition to IPv6? </li></ul><ul><li>What is the HP history with IPv6? </li></ul>IPv6 FAQs
    41. 41. IPv6 resources <ul><li>www.IPv6forum.com international IPv6 Forum </li></ul><ul><li>www.ipv6ready.org IPv6 Forum IPv6 Ready Logo information </li></ul><ul><ul><li>IPv6 Ready Logo white paper http://www.ipv6forum.com/dl/white/IPv6_Ready_Logo_White_Paper_Final.pdf </li></ul></ul><ul><li>www.nav6tf.org North America IPv6 task force </li></ul><ul><li>www.eu.IPv6tf.org European Task IPv6 Force </li></ul><ul><li>www.v6pc.jp/en/index.phtml Japan IPv6 Promotion council </li></ul><ul><li>IPv6 Security Link: www.seanconvery.com/ipv6.html </li></ul><ul><li>HP IPv6 Link: www.hp.com/network/ipv6 </li></ul>June 2008
    42. 42. More information <ul><li>Presentation will be posted to: </li></ul><ul><ul><li>http://www.slideshare.net/rhoton </li></ul></ul><ul><li>HP Resources </li></ul><ul><ul><li>www.hp.com/network/ipv6 </li></ul></ul><ul><li>Any other questions? </li></ul><ul><ul><li>http://www.linkedin.com/in/rhoton </li></ul></ul>