Both service providers and enterprises understand the importance of transforming their approach to networking from opportunistic to strategic and forward-looking. The essential element in this shift is a singular, secure, future-proof IP infrastructure over which all services and applications can be delivered -- an approach that Juniper Networks and other technology leaders have defined as "infranets." While the long-term benefits of IPv6 are widely understood, deployment demands that any IPv6 implementation meet several immediate criteria. Recognized by IPv6 technology leaders such as Japan Gigabit Network (JGN) and Internet 2/Abilene, Juniper Networks IPv6 solution delivers on these requirements by executing on its MINT (Model for InfraNet Transformation) framework.

IP version 6 (IPv6) is the newest version of the Internet Protocol, designed as the successor to IP version 4. Ixia's IPv6 Emulation Software Suite provides a complete set of verification tools designed to facilitate the migration from IPv4 to IPv6. The IPv6 Emulation Software Suite provides both protocol conformance and performance solutions for IPv6 in conjunction with Ixia's dedicated hardware test platform. The IPv6 Emulation Software Suite is supported on all of Ixia's Ethernet, Packet Over SONET (POS), and ATM Load Modules supporting a CPU per port. Users can validate ICMPv6 as per RFC 2463, Neighbor Discovery Protocol as per RFC 2461, Address Auto-configuration as per RFC 2462, and Path MTU Discovery protocols. Tcl support is available on Windows and UNIX platforms.

Supply chain is much bigger than simple inventory systems! Special thanks to Mark Stevens, Materials Manager Extraordinaire! · Mobility model facilitates movement of workforce/B2B vendors while allowing constant access to ERP, MRP, CRM, Engineering, CAD, etc systems and each other. Move to scanable chip technology where reader is mobile (PDA or laptop attachable) or low cost for widespread usage Medical devices use v6 to easily integrate with hospital WLAN or LAN for tracking. · DoD Net Centric Vision one data point is that all software, platforms, and operations become interconnected using the Internet Protocol (IP) technology and network software infrastructure, based on commercial off-the-shelf products, across the DoD Global Information Grid (GIG).

Support for IPv6 on user layer was fully introduced in 3GPP Release 99. · IMS (IP Multimedia Core Network Subsystem) introduced in Release 5. · "IPv6 for Some Second and Third Generation Cellular Hosts" (IETF Informational RFC 3316) is IPv6 implementation guideline for GPRS and UMTS mobile terminals supporting IPv6. · IPsec: securing host-to-host or firewall-to-firewall communication. The terminal utilizes WLAN for the wireless access, Mobile IPv6 for mobility management, IPsec for encryption ad RFID for user identification. · The external security key, an RF tag, gives easy & secure login to the network, simply by touching the terminal with the tag.

Internet Protocol version 6 or IPv6 is the next-generation technology developed to accommodate the Internet's need for more addresses and a more robust platform to support new applications, such as wireless data. Moving from IPv4's 32 bits address length to IPv6's 128 bits length will create literally billions of billions addresses---plenty to support growth of the Internet in years to come, particularly Internet connections from phones, hand-helds and other devices. GEANT, the multi-gigabit pan-European Research Network, will provide IPv6 services to the research and education networks in Europe. InterOperability Lab with support from Spirent and dozens of other vendors.

IPv6 Forum creates first published IPv6 acceptance standard with 'IPv6 Ready' logo The IPv6 forum plays a major role in bringing together industrial players to help in the design, development and deployment of next generation Internet Protocols. Unlike IPv4 that started with a small closed group of implementers, the universality of IPv6 leads to a huge number of implementations on a global scale. To this end, an international task force has been at work defining the IPv6 Logo Program, chaired by Hiroshi Esaki, technically supported by Cesar Viho at Irisia in France and Ben Schultz at UNH-IOL in the US and Hiroshi Miyata (TAHI/Japan).

To deal with the addressing issues of the widely used IP protocol, the IETF has proposed a new routing protocol called IPv6. Development of the IPv6 standard has been on-going for several years, with a number of large networks fully operational, and several PC applications implemented. Although the technical issues are well understood, large-scale deployment is dependent on a seamless transition from IPv4. 3Com has been an early supporter of the IPv6 initiative and is a founding member of the IPv6 forum. The information contained in this document represents the current view of 3Com Corporation on the issues discussed as of the date of publication.

After completing the "Implementing IPv6 Networks" course, you will be able to: Describe the features, benefits, and operation of the IPv6 protocol. Network professionals with a good working knowledge of all routing protocols. To fully benefit from this training, you must have routing, switching, and access product knowledge and skills equivalent to the Cisco Certified Network Professional (CCNP) certification or better. The hands-on lab exercises in this course provide critical training to enable network professionals to install, configure, an maintain IPv6 networks and make the integration and coexistence of IPv6 and IPv4 networks successful. This course covers the configuration of routing protocols such as RIP, integrated IS-IS, BGP4+, IPv6 deployment strategies including overlay tunnels, IPv6 Provider Edge Router over MPLS (6PE), and NAT-PT, and other IPv6 features supported on Cisco IOS routers.

The transition between today's IPv4 Internet and a future IPv6-based one will be a long process during which both protocol versions will coexist. IPv6 packets are encapsulated by a border router before transportation across an IPv4 network and decapsulated at the border of the receiving IPv6 network. The TB (Tunnel Broker) approach has been proposed to automatically manage tunnel requests coming from the users and ease the confi guration process. Translation is necessary when an IPv6 only host has to communicate with an IPv4 host. ALGs (Application-Level Gateways) are required to translate embedded IP addresses, recompute checksums, etc. SIIT (Stateless IP/ICMP Translation) and NAT-PT (Network Address Translation - Protocol Translation) are the associated translation techniques.

The good news is that a number of fields in the IPv4 header have been removed from the IPv6 header (primarily because they are unused or no longer needed today). For review, an IPv6 address is written as eight 16-bit hexidecimal integers separated by colons. Address Resolution in IPv6 land is different than IPv4 because we now rely on a neighbor discovery and router discovery algorithm rather than the simple ARP of IPv4. When media addresses of the destinations are unknown, multicast is used to transmit the messages. While the data plane is responsible for processing and forwarding IPv6 packets, it is up to the control plane to provide support for the interior and exterior routing protocols.

scores of documents, on IPv6 address formats and routing protocols (unicast & multicast), L2 encapsulations, autoconfiguration, DNS changes, header compression, security extensions, IPv4/IPv6 co-existence & transition, MIBS, loss of peer-to-peer communication model loss of application independence but at least the email & web Internet kept growing! What's Happening in the IETF IPv6 Working Group? WG chairs propose to prioritize current and future work; to be discussed on WG mailing list and at meeting in Yokohama next week Prioritizing IPv6 WG Work (Rough Draft; Feedback Solicited!) if I knew it was going to take so long, I would have let one of the other IPng candidates "win"!

The header structure of an IPv6 packet is specified in RFC 2460. The Identification field, the Flags field, and the Fragment Offset field han-dlefragmentationofapacketintheIPv4header.Fragmentationhappensifa large packet has to be sent over a network that only supports smaller packet sizes. IPv6 routers along the path ofapacketdonotprovidefragmentation,astheydidwithIPv4.SotheIden-tification, Flags, and Fragment Offset fields were removed from the IPv6 header and will be inserted as an Extension header, if needed. · Value 10: discard the packet and send ICMP Parameter Problem, Code 2 message to the packet's source address, pointing to the unrecognized option type. The Routing header is used to give a list of one or more intermediate nodes that should be visited on the packet's path to its destination.

The driving force of the new standard is the rapid growth of the Internet and IPv6 is being introduced to overcome the address space restrictions of the old one. At first glance the implications for the network administrator seem negligible, because many of us already have our allocated addresses. The result of this simplification, and improved flexibility, is that the simplest IPv6 header is still only 40 bytes long -- or double the size of the IPv4 header without options -- despite the fact that the two addresses it incorporates are four times the size of the IPv4 header. The aim of the designers of this aspect of IPv6 was that a host should be able to discover automatically all the information it needs to connect to the Internet, without human intervention.

· Do your address plan using site locals and use the renumbering functions when connecting to the IPv6 Internet -- Private addresses (e.g. local printers) · Which one to use as source and destination address for a given communication? -- Destination: multicast address of all nodes on the link (FF02::1) -- Data: prefix, lifetimes, default router, options -- ICMP type 134 Router Advertisement (cont.) · The tunnel endpoints take care of the encapsulation. · Server can respond: -- I'm full, cannot give you a new tunnel, please go to this other tunnel server (referer) -- I can give you a host tunnel, but not a network tunnel -- Here is the prefix, here is my bgp info (as number)