Download The Java and Jini Technologies for Distance Education in

INTERNET PROTOCOL IPv6 NEXT GENERATION
CHARACTERISTICS, MODELING AND TRANSITION
The architectural simplicity by Antoine de Saint-Exupery
In each thing, you reach the perfection, not when there is nothing left to add,
but when there is nothing left to take off.
WHY IPV6?
“The Internet is becoming a victim of its own success.”
IP protocol by RFC (Request For Comments) 7911 in 1981
IP allows to use different technologies in different parts of the
network: LANs (Ethernet, Token Ring, FDDI), electronic mail,
navigation on www servers enriched with Java applets, FTP or
Telnet, frame relay or ATM public services
IPv4 achieves this result by providing a service with the
following main characteristics:
–
Universal addressing: Each IP network interface has a unique
worldwide address with 32 bits.
–
Best effort: IP performs its best effort to deliver packets, but it
doesn’t guarantee anything at the upper layer, neither in terms
of percentage of delivered packets nor in terms of time used to
execute the delivery. In short, IPv4 doesn’t have a built-in
concept of Quality of Service (QoS).
Overview of IPv6
Why a new ip scheme?
IPv4 vs IPv6 solutions
Ipv6 addressing
IPv6 Autoconfiguration
IPv6 over Ethernet
IPv6 Security and QoS
Routing protocols
Transition strategies
Tunnels for IPv6
Address Translation
How to connect to IPv6
IPv6 deployment
IPv6 Adoption
IPv6 evaluation
Still a lot to do
Applications
Data exchange tech.
Jini connection
Jini programming model
Jini applications
VIR approaches
VIR systems
Semantics in VIR
Proposed VIR method
CORPAI algorithm
IRONS System
GUI of IRONS
WHY A NEW IP SCHEME?
IPv4 addresses take up 32 bits (about 4 billion addresses are available)
but 4 billion computers don’t exist in the world but...
Growth in time of total sites across all domains (August 95- Sept.2006)
IPV4 ADDRESS ARCHITECTURE
Class A: 128 networks x 16M hosts (50% of all address space)
A (7 bits)
Host address (24 bits)
0
Class B: 16K networks x 64K hosts (25%)
B (14 bits)
Host (16 bits)
10
Class C: 2M networks x 256 hosts (12.5%)
C (21 bits)
Host (8 bits)
110
It is a fact:
China requested addresses to connect 60,000 schools and got one class B
Several countries in Europe, Africa and Asia are using one class C for a
whole country
IPV6 ADDRESS SPACE REQUIREMENTS
IPv6 needs a new addressing scheme with the following
characteristics:
–
–
–
–
A higher number of bits without further exhaustion
A more flexible hierarchical organization of addresses (Aggregationbased address hierarchy) that doesn’t use the concept of classes, but the
CIDR (Classless Inter Domain Routing) mechanism
A scheme for address assignment aimed to minimize the size of routing
tables on routers and to increase the CIDR performance
Global addresses for the Internet and local addresses for Intranets
All software vendors officially support IPv6 in their latest O.S.
releases Apple MAC OS X, HP (HP-UX, Tru64 & OpenVMS), IBM
zSeries & AIX, Microsoft Windows XP, .NET, CE; Sun
Solaris,…*BSD, Linux,…
SHORT HISTORY REMARKS
TUBA (1992)
– TCP and UDP over Bigger Addresses
– Uses ISO CLNP (Connection-Less Network Protocol)
– Dropped
SIPP (1993)
– Simple IP Plus
– Merge of Sip and Pip
– 64 bits addresses
IPng (next generation) or IPv6 developed by IETF
(Internet Engineering Task Force) and adopted as SIPP in 1994
–
–
–
–
–
–
–
–
–
–
Changed address size to 128 bits
Changed to Number of addresses
Efficiency in routers low and very high
Bandwidth (100G/bytes++)
Security
Mobility
Autoconfiguration
Seamless transition
Don’t require a day X for switching to IPv6
No need to change hardware
NEW REQUIREMENTS FOR IPV6
IPv6 addresses provides the addressing each atom in the universe (one atom
needs for computer)
Unify Intranets and the Internet global addresses
Using LANs Better simplifying the relationship between an IPv4 address and a
MAC address by using a “neighbor discovery” method on LAN more efficient than
ARP (Address Resolution Protocol)
Security is defined by series of encryption and authentication procedures for IPv6
Routing minimizes tables on routers, autoconfiguration mechanisms, networks
dynamically assign addresses to stations, provide good support for mobility
Improve the support of ATM (Non-Broadcast Multiple Access protocol) in IPv6.
(virtual circuits vs datagram)
Priorities will be introduced in the IPv6 header (4-bit “priority” field) to differentiate
16 potential traffic priorities.
Plug and Play on DHCPv6 (Dynamic Host Configuration Protocol) protocol:
automatic configuration of hosts and subnetworks, the learning of default routers
through the DNS, also a automatic configuration of host names.
Support for mobility: use two addresses - the first “permanent” on organization’s
network and the second “dynamic” depending on the point from which they are
Transition from IPv4 to IPv6, migration strategy based on a “dualstack”,
implemented through a series of tunnels called 6-Bone.
IPv4 vs IPv6 SOLUTIONS
Expanded address space
Header format simplification with fixed length
IPv6 header is twice as long (40 bytes) as IPv4 header
No checksum at the IP network layer
Autoconfiguration, authentication and privacy capabilities
No more broadcast
IPv6 STATUS AND STANDARDS
Several key components on standards track…
Specification (RFC2460)
ICMPv6 (RFC2463)
RIP (RFC2080)
IGMPv6 (RFC2710)
Router Alert (RFC2711)
Autoconfiguration (RFC2462)
DHCPv6 (RFC3315)
IPv6 Mobility (RFC3775)
Neighbor Discovery (RFC2461)
IPv6 Addresse(RFC3513/3587)
BGP (RFC2545)
OSPF (RFC2740)
Jumbograms (RFC2675)
Radius (RFC3162)
Flow Label (RFC3697)
GRE Tunneling (RFC2473)
IPv6 available over:
PPP (RFC2023)
Ethernet (RFC2464)
FDDI (RFC2467)
Token Ring (RFC2470)
NBMA (RFC2491)
ATM (RFC2492)
Frame Relay (RFC2590)
ARCnet (RFC2497)
IEEE1394 (RFC3146)
FiberChannel (RFC3831)
IPv4 vs IPV6 HEADER
Version: 4 bits for IPv4 – 6 bits for IPv6
TOS in IPv4 substituted by Traffic Class 8 bits for IPv6
Flow Label (20 bits-experimental, used by a source
node to label sequences of packets)
Payload Length in IPv6 instead Total length in IPv4
Next Header (8 bits, used for extension headers like Protocol field in IPv4)
Routing, Fragment, Destination options, Authentication
Hop Limit similar to TTL in IPv4
MTU must be at least 1280 bytes (1500+ recommended).
UDP (User Datagram Protocol) checksum required
EXTENSION HEADERS
Order of the headers should be the following:
• IPv6 header
• Hop-by-Hop Options header
• Destination Options header
• Routing header
• Fragment header
• Authentication header
• Encapsulating Security Payload header
• Destination Options header
• Upper-layer header
• Source node should follow this order, but destination nodes should be
prepared to receive them in
any order
LARGER ADDRESS SPACE REPRESENTATION
IPv4 - 32 bits = 4,294,967,296 possible addressable devices
IPv6 - 128 bits: 4 times the size in bits = 3.4 x 1038 possible addressable
devices = 340,282,366,920,938,463,463,374,607,431,768,211,456
(5 x 1028 addresses per person on the planet)
16 bit fields in case insensitive colon hexadecimal representation
2031:0000:130F:0000:0000:09C0:876A:130B
Leading zeros in a field are optional: 2031:0:130F:0:0:9C0:876A:130B
Successive fields of 0 represented as ::, but only once in an address:
2031:0:130F::9C0:876A:130B is ok, but 2031::130F::9C0:876A:130B is NOT ok
0:0:0:0:0:0:0:1 → ::1 (loopback adr.), 0:0:0:0:0:0:0:0 → :: (unspecified adr.)
IPv4-compatible: 192.168.30.1= 0:0:0:0:0:0:192.168.30.1= ::C0A8:1E01
In a URL, it is enclosed in brackets
http://[2001:1:4F3A::206:AE14]:8080/index.html
ADDRESS TYPES
Unicast : One to One (Global, Link local)
Unicast is a communication between a single host and a single receiver
Anycast : One to Nearest (Allocated from Unicast)
Anycast is a communication between a single sender and a list of addresses
Multicast : One to Many
Multicast is communication between a single host and multiple receivers.
Broadcasts in IPv4 interrupts all devices on the LAN even if the intent of
the request was for a subset. Can completely swamp the network
(“broadcast storm”)
Broadcasts in IPv6 are not used and replaced by multicast
RFC2373 IPv6 ADDRESSING ARCHITECTURE
In general Required Node Addresses includes:
Link-Local Address for each interface
Assigned Unicast Addresses
Loopback Address
All-Nodes Multicast Addresses
Solicited-Node Multicast Address for each of its assigned unicast and anycast addresses
Multicast Addresses of all other groups to which the host belongs
The allocation process is:
The Internet Assigned Numbers Authority IANA has allocated 2001::/16 for initial IPv6
unicast use
Each registry gets /23 prefixes from the IANA
Registry allocates a /32 prefix to an IPv6 ISP
Policy is that an ISP allocates a /48 prefix to each end customer
UNICAST ADDRESSES
Unspecified
example - in IPv4 like 0.0.0.0, in IPv6: 0:0:0:0:0:0:0:0 or ::
Used as a placeholder when no address available, for Initial DHCP request and
Duplicate Address Detection (DAD)
Loopback
example - in IPv4 like 127.0.0.1, in IPv6: 0:0:0:0:0:0:0:1 or ::1
Identifies self, detect Local host, to find if your IPv6 stack works
Scoped addresses new in IPv6 (Link-local and Site-local)
Link-local, Scope = local link (scope limited to local network)
Can only be used between nodes of the same link, cannot be routed
Automatically configured on all nodes using the interface identifier
(based on MAC address), gives every node an IPv6 address to start communications
Format: FE80:0:0:0:<interface identifier>
Site-local, Scope = site (a network of links)
Can only be used between nodes of the same site, cannot be routed outside the site
(i.e. the Internet), Very similar to IPv4 private addresses, not configured by default
Format: FEC0:0:0:<subnet id>:<interface id>
Subnet id = 16 bits = 64K subnets
UNICAST ADDRESSES
Aggregatable Global (addresses for generic use of IPv6)
Structured as a hierarchy to keep the aggregation:
First 3 bits 001 (2000::/3) is first allocation to IANA for use for IPv6 Unicast,
called Top-level Aggregator (TLA) - Primary providers
Then allocation to Intermediate Providers, called Next-level Aggregator (NLA)
Then to sites Site Level Aggregator - Your site (16 bits)
Then to subnets
MULTICAST ADDRESSES
Multicast Addresses 1111 1111 1/256
– FF00::/8
– FF02::1 all nodes on the local network
– FF02::2 all routers on the local network
Solicited-Node multicast address
– FF02:0:0:0:0:1:FF00::/104
address formed by appending the lower 24 bits of the IPv6 address
ANYCAST
One-to-nearest: great for discovery functions
(Packet sent to anycast address is routed to “closest” interface)
Anycast addresses are indistinguishable from unicast addresses
– Allocated from the unicast addresses space
– Some anycast addresses are reserved for specific uses
Few uses:
– Router-subnet
– MobileIPv6 home-agent discovery
– DNS discovery anycast
AUTOCONFIGURATION PROCESS
Host configured for autoconfiguration
• Host boots. Sends a Router Solicitation
• Host receives the Router Advertisement RA, specifying subnet prefix, lifetimes,
default router …
• Host generates its IP address by appending:
Received subnet prefix (64 bits)
Interface address modified for Extended Unique Identifier EUI-64 format
• Host verifies usability of the address by doing the Duplicate Address Detection
process
Stateless autoconfiguration (RFC2462)
Stateful autoconfiguration
– Manual IP configuration
– DHCP (Dynamic Host Configuration Protocol) configuration
Renumbering (RFC 2894)
– Domain-interior routers learn of prefix introduction / withdrawal
IPV6 AUTOCONFIGURATION
Stateless (RFC2462).
Host autonomously configures its own Link-Local address
Router solicitation are sent by booting nodes to request RAs
for configuring the interfaces.
– Applies to hosts only (not to routers)
– No manual configuration required
• Specifies the prefix, default route and lifetime
• But does not specify the DNS servers
– Assumes interface has unique identifier
– Assumes multicast capable link by doing Duplicate Address Detection
• Join all-nodes multicast address (FF02::1)
• Join solicited-node multicast address of
the tentative address FF02:0:0:0:0:1:FF00: ...
• Send Neighbor Solicitation on solicited-node
multicast address
• If no Neighbor Advertisement is received,
address is ok
IPV6 AUTOCONFIGURATION
Stateful autoconfiguration
– Manual IP configuration
– –DHCP configuration
Larger address space enables:
The use of link-layer addresses inside
the address space
Auto-configuration with "no collisions“
Offers "Plug and play"
Renumbering
Hosts renumbering is done by modifying
the RA to announce the old prefix
with a short lifetime and the new
prefix
Router renumbering protocol (RFC
2894), to allow domain-interior
routers to learn of prefix introduction /
withdrawal
HOW TO GET AN IPv6 ADDRESS?
IPv6 address space is allocated by the 4 Regional Internet Registries RIPs:
– APNIC (Asia Pacific Network Information Centre)
– ARIN (American Registry for Internet Numbers)
– LACNIC (Latin American and Caribbean Internet Addresses Registry)
– RIPE NCC (Réseaux IP Européens Network Coordination Centre)
– Internet Service Providers ISPs get address space from the RIRs
– Enterprises get their IPv6 address space from their ISP
6to4 tunnels 2002::/16
6Bone
– IPv6 experimental network, now being actively retired, with end of service
on 6th June 2006 (RFC3701)
IPv6 OVER ETHERNET (RFC2464)
Lowest order 64-bit field of unicast address may be assigned in several
different ways:
– auto-configured from a 64-bit EUI-64, or expanded from a IEEE 802
48-bit MAC
address (e.g., Ethernet address).
– auto-generated pseudo-random number (to address privacy concerns)
– assigned via DHCP
– manually configured
EUI-64 address is formed by inserting FFFE and OR’ing a bit identifying the
uniqueness of the MAC address
WHAT DOES IPv6 DO FOR SECURITY?
Nothing IPv4 doesn’t do – standardized framework for securing Internet
Protocol IPSec runs in both but IPv6 mandates IPSec
IPv6 Security
IPsec standards apply to both IPv4 and IPv6
All implementations required to support authentication and encryption
headers
Authentication separate from encryption for use in situations where
encryption is prohibited or prohibitively expensive
Key distribution protocols are not yet defined (independent of IP v4/v6)
Support for manual key configuration required
WHAT DOES IPv6 DO FOR IP QUALITY OF SERVICE?
Nothing IPv4 doesn’t do – Differentiated and Integrated Services run in both
Two basic approaches developed by IETF for IPv6:
“Integrated Service” (int-serv)
–
fine-grain (per-flow), quantitative promises (e.g., x bits per second), uses
Resource Reservation Protocol RSVP signaling
–
IPv6 supports Int-Serv by 20-bit Flow Label field to identify specific flows
needing special QoS
“Differentiated Service” (diff-serv)
–
coarse-grain (per-class), qualitative promises (e.g., higher priority), no explicit
signaling
–
IPv6 supports Diff-Serv by 8-bit Traffic Class field to identify specific classes
of packets needing special QoS
Signaled diff-serv (RFC 2998)
–
uses RSVP for signaling allows for policy control without requiring per-router
state overhead
ROUTING IN IPv6
Routing in IPv6 is unchanged from IPv4 and still uses the longest-prefix
match routing algorithm
IPv6 has 2 types of routing protocols: IGP and EGP
Interior Gateway Protocol IGP
– Routing Information Protocol RIPng (RFC 2080)
– Cisco Enhanced Interior Gateway Routing Protocol EIGRP for IPv6
– Open Shortest Path First version 3 OSPFv3 (RFC 2740)
– Integrated Intermediate System-to-Intermediate System IS-ISv6
Exterior Gateway Protocol EGP :
– Multi Protocol - Border Gateway Protocol MP-BGP4 (RFC 2858
and RFC 2545)
IPv6 ROUTING PROTOCOL
RIP in IPv6
– Based on RIP-2: same design, distance-vector, 15 hops diameter…
– IPv6 prefix, next-hop IPv6 address
– Uses multicast (FF02::9 = all-rip-routers as the destination address for RIP updates)
– Uses IPv6 for transport
– Most (if not all) IPv6 router implementations support RIP IPv6
– Implementations: GateD, Mrtd, Kame route6d, Zebra, Cisco, etc.
EIGRP for IPv6
– Cisco EIGRP has had IPv6 protocol support added
– Uses similar command-line interface (CLI) to change the IP address in IPv4 protocol support
– Easy deployment path for existing IPv4 EIGRP users
– In Emotional Freedom Techniques EFT images, coming soon to 12.3T
OSPF (Open Shortest Path First) for IPv6 Also known as OSPFv3
– Important rewrite to remove IPv4 dependencies
– Link-local addresses are used
– Uses IPv6 for transport
– Implementations: Telebit, IBM*, Zebra*, Gated*, MRTd*, Cisco*
IPv6 ROUTING PROTOCOL
IS-IS is the OSI IGP protocol
– IETF ISIS for Internets Working Group
– Compared to OSPF, IS-IS for IPv6 is easier to implement and modify
– 2 new type-length-values (TLV) were defined:
• IPv6 Reachability (with 128 bits prefix)
• IPv6 Interface Address (with 128 bits)
– As result, new TLVs attributes for Multi-Topology extensions
BGP4
– Includes multiprotocol extensions for BGP, for new address families (IPv6, Virtual
Private Networks VPN, …)
– IPv6 address family:
– Use scoped addresses in the NEXT_HOP
– NEXT_HOP and Network Layer Reachability Information NLRI are expressed as IPv6
addresses and prefix
– Most IPv6 router vendors support IPv6 BGP. It used on the 6Bone since 1996
– Implementations: GateD, Mrtd, Kame BGPd, Zebra, Cisco, etc.
IPv6 INTEGRATION & TRANSITION
IPV6 Integration & Transition Strategies
For end-systems, there is:
– Dual stack approach
For network integration, there is:
– Tunnels
– IPv6-only to IPv4-only: some sort of translation
Transition Recommendations
Define the processes by which networks can be transitioned from IPv4 to IPv6
Define and specify the mandatory and optional mechanism that vendors are to implement in
Hosts, Routers and other components of the Internet in order for the
Transition
IPv4-IPv6 Co-existence/Transition
A wide range of techniques have been identified and implemented of three categories:
– Dual-stack techniques, to allow IPv4 and IPv6 to co-exist in the same devices and networks
– Tunneling techniques, to avoid order dependencies when upgrading hosts, routers, or
regions
– Translation techniques, to allow IPv6-only devices to communicate with IPv4-only devices
Expect all of these to be used, in combination
DUAL STACK APPROACH
Node has both IPv4 and IPv6 stacks and addresses
IPv6-aware application asks for both IPv4 and IPv6 addresses of destination
IPv6 application can use IPv4 mapped addresses to communicate with IPv4 nodes
DNS resolver returns IPv6, IPv4 or both addresses to application
IPv6/IPv4 applications choose the address and then can communicate with IPv4
nodes using IPv4 or with IPv6 nodes using IPv6
DUAL STACK APPROACH & DNS
In a dual stack case:
– IPv4 and IPv6-enabled
– Asks the DNS for all types of addresses
– Chooses one address and, for example, connects to the IPv6 address
IOS IPv6 DNS CLIENT SUPPORT
Internetwork Operating System IOS supports IPv6 DNS
Queries DNS servers for IPv6/IPv4:
– First tries queries for an IPv6 address (AAAA record) if no IPv6 address exists,
then query for an IPv4 address (A record)
– When both IPv6 and IPv4 records exists, the IPv6 address is picked first
Static hostname to IPv6 address can also be configured
• Note: IPv6 stacks on Windows XP, Linux, FreeBSD- Berkeley Software Distribution OS
A DUAL STACK CONFIGURATION
DNS commands for IPv6
Define static name for IPv6 addresses
ipv6 host <name> [<port>] <ipv6addr> [<ipv6addr> ...]
Example: ipv6 host router1 3ffe:b00:ffff:b::1
Configuring DNS servers to query
ip name-server <address>
Example: ip name-server 3ffe:b00:ffff:1::10
IPv6-enable router
If IPv4 and IPv6 are configured on one interface, the router is dual-stacked
Telnet, Ping, Traceroute, SSH, DNS client, TFTP,…
TUNNELS FOR IPv6 DEPLOYMENT
Techniques are available to establish a tunnel:
Manually configured
– Manual Tunnel (RFC 2893)
– Generic Routing Encapsulation GRE (RFC 2473)
Semi-automated
– Tunnel broker
Automatic
– Compatible IPv4 (RFC 2893)
– 6to4 (RFC 3056)
– 6over4: Deprecated
– Intra-Site Automatic Tunnel
Addressing Protocol ISATAP
• Tunneling is encapsulating the IPv6 packet in the IPv4 packet
• Tunneling can be used by routers and hosts where routing table chooses which tunnel to take
EXAMPLE, TUNNELING IPv6 IN IPv4
IPv6 encapsulated in IPv4
Many topologies possible
– Router to router
– Host to router
– Host to host
The tunnel endpoints take care of the encapsulation. This process is
“transparent” for the intermediate nodes
Tunneling is used by most transition mechanisms
MANUALLY CONFIGURED TUNNEL (RFC2893)
Manually Configured tunnels require:
Tunnel endpoints must be dual stack nodes Dual stack end points
Both IPv4 and IPv6 addresses are explicitly configured at each end
Tunnel configuration implies manual configuration of:
– Source and destination IPv4 address
– Source and destination IPv6 address
Between:
– Two hosts
– One host and one router
– Two routers (for two networks)
6to4 TUNNEL (RFC 3056)
Applicability: interconnection of isolated IPv6 domains over an IPv4 network
Automatic establishment of the tunnel
– No explicit tunnels by embedding the IPv4 destination address in the IPv6 address
– Under the 2002::/16 reserved prefix. (2002::/16 = 6to4)
Gives a full /48 to a site based on its external IPv4 address
IPv4 external address embedded: 2002:<ipv4 ext address>::/48
Format: 2002:<ipv4add>:<subnet>::/64
6to4 Network to Network
6to4 Host to Network
6to4 TUNNEL (RFC 3056)
6to4 Tunnel is an automatic tunnel method
Gives a prefix to the attached IPv6 network
2002::/16 assigned to 6to4
Requires one global IPv4 address on each Ingress/Egress site
6to4 RELAY
6to4 relay (Current Work):
Is a gateway to the rest of the IPv6 Internet
Discovery of the 6to4 relay (or IPv6 default route)
Uses anycast reserved address (RFC 3068) for multiple 6to4 Relay
Integration with Dual Stack IPv6 Dominant Transition Mechanism DSTM
TUNNEL BROKER
A free net concept for IPv6
Semi-automated tunnel configuration
Automates the manual configuration of tunnels (with explicit IPv4 source and destination addresses,
and IPv6 source and destination addresses)
Plug-and-play IPv6 using the current IPv4 Internet as the transport
Provides IPv6 connectivity on demand
Assigns an IPv6 address to the host
Connects the host to the IPv6 Internet
Tunnel Broker Creation
- User has a username/password
- Receives the users request by the Web
- Sends a “create-tunnel” command to one of the tunnel servers
- Tunnel server creates the tunnel end point
- Client receives the script to create its tunnel end point
- User can come back to delete his tunnel by using his username/password to authentify
TUNNEL SERVER: NEW GENERATION
Currently supported clients: NT, FreeBSD/Kame, FreeBSD/Inria,
Cisco, Linux, Solaris8
Very easy to add new clients
Add support for more host implementations
Add support for IPv6 routers
Tunnel Broker idea by Alain Durand
IPv6 Tunnel Broker: Installation instructions
User interface
Fill-out a Web form
- Choose your OS
- Verify your IPv4 address
- Enter a nickname and your country (for DNS)
Server creates its tunnel end point
Client receives a script that should be executed:
This script creates the tunnel on the client side
You are connected
IPv6 TO IPv4 TRANSLATION MECHANISMS
Translation
NAT-PT (RFC 2766 & RFC 3152)
(Network Address Translation – Protocol Translation).
- Allows native IPv6 hosts and applications to communicate with native
IPv4 hosts and applications, and vice versa
- Allows easy-to-use transition and co-existence solution
IPv6 DEPLOYMENT SCENARIOS
Many ways to deliver IPv6 services to End Users
• End-to-end IPv6 traffic forwarding is the Key feature
• Minimize operational upgrade costs
Incremental Upgrade/Deployment
ISP’s differentiate Core and Edge infrastructures upgrade
Service Providers and Enterprises may have different deployment needs
• Incremental Upgrade/Deployment
• ISP’s differentiate Core and Edge infrastructures upgrade
• Enterprise Campus and WAN may have separate upgrade paths
IPv6 over IPv4 tunnels
Dedicated Data Link layers for native IPv6
Dual stack Networks
• IPv6 over Multiprotocol Label Switching MPLS or IPv4-IPv6 Dual Stack
Routers
IPv6 ADOPTION
ISP scenario
Configured Tunnels or Native IPv6 between IPv6 Core Routers
Configured Tunnels or Native IPv6 to IPv6 Enterprise’s Customers
Tunnels for specific access technologies
6to4 relay service and configured tunnels between sites or to 6Bone users
Enterprise/Home scenario
6to4 tunnels between sites, use 6to4 Relay to connect to the IPv6 Internet
Tunnels or Native IPv6 on a Campus
IPv6 DEPLOYMENT PHASES
MOVING IPv6 TO PRODUCTION
EXAMPLE, IPv6 CONFIGURATION ON WINDOWS XP
Service Pack 2 and later versions support Tunneling of IPv6
WIRELESS IP CONFIGURATION
Interface shows wireless IPv4 and IPv6 addresses configuration on PC
with Service pack 2, Windows XP
IPv6 EVALUATION
Ping IPv4 vs IPv6
ms
Speed of response:
ms
v6 min
v6 max
v6 media
v4 min
v4 max
80
70
60
50
40
30
20
10
0
Packets transfer
25 paquetes
50 paquetes
v4 media
90
80
70
Time for packet transfer for each IP
60
(min-max time for packet and average for all packets) 50
40
30
20
10
0
Variations for 25 packets transfer
ping v6 25
ping v4 25
# of packets
1
3
5
7
9 11 13 15 17 19 21 23 25
STILL A LOT TO DO…
Though IPv6 has all the functional capability of IPv4 today:
Implementations are not as advanced (e.g., with respect to performance,
multicast support, compactness, instrumentation, etc.)
Deployment has only just begun
Much work to be done moving application, middleware, and management
software to IPv6
Much training work to be done (application developers, network
administrators, sales staff,…)
Some of the advanced features of IPv6 still need specification,
implementation, and deployment work
Most Operating Systems now deliver an IPv6 stack
Internetworking vendors are committed on IPv6 support
Evaluate IPv6 products and services, as available
Plan for IPv6 integration and IPv4-IPv6 co-existence
Training, applications inventory, and IPv6 deployment planning
Upgrade your router with IPv6 ready software
APPENDIX A, IPv6 ON SOLARIS 8
IPv6 is supported by Solaris 8:
http://www.sun.com/software/solaris/ipv6/
Manuals available on-line:
http://docs.sun.com
• Enabling IPv6 for a node
• For each network interface
– Create empty file /etc/hostname6.<interface>
– After reboot, autoconfiguration will assign address
• Enabling IPv6 on a router /etc/inet/ndpd.conf
– Router advertisement configuration
• RIPng (or install full-featured routing daemon and
tools MRTd)
Configured tunnel on Solaris 8
• /etc/hostname6.ip.tun0
– tsrc 206.123.31.101 tdst 198.166.1.133 up
– addif 3ffe:b00:c18::a/127 3ffe:b00:c18::b up
• Run “/etc/init.d/inetinit start” to enable
Automatic tunnel on Solaris 8
• /etc/hostname6.ip.atun0
– tsrc 206.123.31.101 ::206.123.31.101/96 up
• Run “/etc/init.d/inetinit start” to enable
IPv6 on Solaris 8
• /etc/inet/ipnodes
– static list of IPv6 and IPv4 nodes
• /etc/nsswitch.conf
– ipnodes: files dns
• Network Information Service NIS and Network
File System NIS+ extensions for IPv6
• NFS and RPC IPv6 support
APPENDIX B, WINDOWS NT IPv6
Available on-line
http://www.research.microsoft.com/msripv6/
• Runs on NT 4 and Windows 2000
• Has host and router functionality
• Supports IPv6 tunneling
• Supports 6to4 transition mechanism
• Implemented as a separate protocol stack
Microsoft Research IPv6 applications and utilities
• ping6, tracert6, ttcp6, ftp6/ftpd6
• IPv6 version of wininet.dll
– Can use Internet Explorer on IPv6
• Fnord! Web server
• session directory tool SDR, Robust Audio Tool
RAT conferencing tool
• Network Monitor parser for IPv6
MSR IPv6 configuration
• Install
• If there is an IPv6 router in your network,
you’re configured (router solicitation)
• If not, configure a tunnel with an IPv6
MSR IPv6 tunnel configuration
• ipv6.exe rtu ::/0 2/::206.123.31.102 pub
– Creates a tunnel with ::206.123.31.102
– Creates a default IPv6 route to
::206.123.31.102
• ipv6.exe adu 2/3ffe:b00:c18:1fff:0:0:0:3
– Assigns 3ffe:b00:c18:1fff:0:0:0:3
to tunnel endpoint