IPv6 First Steps
So#a
Silva
Berenguer
soa@[Link]
Internet and the TCP/IP protocols
1969 Start of ARPANET
1981 IPv4 definitions and the RFC 791
1983 ARPANET adopts TCP/IP
1990 First studies about IPv4 address exhaustion
1993 Internet begins to be commercially exploited
- Increased discussion about a possible address
depletion and the increase of the addess routing
tables
IPv4 Address exhaustion
IPv4 = [Link] addresses
Initial distribution policy directions
Class A
o
IBM
o
HP
o
AT&T
o
MIT
o
o
o
o
DoD
US Army
USPS
........
Class B
Class C
Reserved Addresses
IPv4 Address Exhaustion
Proposed solutions
Palliative Solutions
1992 - IETF started ROAD working group (ROuting and
ADdressing).
CIDR (RFC 4632)
End use of classes = appropriately sized blocks
Network addresses = prefix/length
Routing aggregation = the growth in the size of the routing
tables
DHCP
Dynamic address assignment
NAT + RFC 1918 (Address Allocation for Private Internets)
Enable to connect an entire network with only one public
address
Solutions
NAT
Advantages
Reduces the need of public internet addresses
Facilitates the internal network address numbering
Hides the network topology
Only allows the packet entry to our network as a response to a
request from the network
Disadvantages
Breaks the internet point-to-point model
Hinder the functioning of a number of applications
Not scalable
Increase the process load in the traduction device
False sense of security
Unable to trace the path of the packet
Prevents the use of security mechanisms such as IPSec
Solutions
Palliative Solutions: Fall of only 14%
Solutions
The measures discussed above generate more time to develop a
new version of the IP protocol
1992 - IETF make the IPng working group (IP Next Generation)
Main questions:
Escalability
Security
Network configuration and management
QoS support
Movility
Routing policies
Transition
Solutions
Definitive solution
IPv6
1998 Defined in RFC 2460
128 bits for addressing
Base header simplified
Extension headers
Flow identification data (QoS).
IPSEC mechanisms built into the protocol
Performs packet fragmentation/reassembly on the
source and destination
NAT is not necessary, allowing point-to-point
mechanisms that facilitate network configuration
....
Why start deploying IPv6 today?
Number of internet hosts
Why start deploying IPv6 today?
Internet continues to grow
~2.000 millions Internet Users
~30% of world population
400% growth in the last 10 years
In 2014 cell phones, Smartphones, Notebooks and 3G devices should
reach 2.25 billion devices
IPv6 deploy in LATAM
Risks of not implementing IPv6
The non-implementation of IPv6 will:
Hinder the deployment of new networks
Slow the process of digital inclussion and reduces the
amount of new Internet users
Slows the emergence of new applications
Increase the use of techniques such as NAT
The cost of not-deploy IPv6 could be greater than that of
not doing it
Internet providers need to innovate and offer new services
to their customers
Related IPv6 RFCs
RFC 1287 - Towards the Future Internet Architecture.
RFC 3330 - Special-Use IPv4 Addresses
RFC 1380 - IESG deliberations on routing and addressing
RFC 1918 Address allocation for Private Networks
RFC 2131 Dynamic host configuration protocol
RFC 2775 - Internet Transparency
RFC 2993 - Architectural Implications of NAT
RFC 3022 - Traditional IP Network Address Translator (Traditional NAT)
RFC 3027 - Protocol Complications with the IP Network Address
Translator
RFC 4632 - Classless Inter-domain Routing (CIDR): The Internet Address
Assignment and Aggregation Plan
RFC 1550 - IP: Next Generation (IPng) White Paper Solicitation
RFC 1752 - The Recommendation for the IP Next Generation Protocol
RFC 2460 - Internet Protocol, Version 6 (IPv6) Specification
Links
[Link]
[Link]
agenda/10_Lees_Google_IPv6_User_Measurement.pdf
[Link]
[Link]
[Link]
[Link]
[Link]