7. SAITM - RSEA 2012
How to identify these users ?
How do we name them?
7
8. That is where the Internet Protocol
SAITM - RSEA 2012
(IP) comes in !
8
9. Internet Protocol - Definition
The principal set of procedures used for
transferring data packets between
SAITM - RSEA 2012
devices on a network-of-networks using
the Internet Protocol Suite.
9
10. IP
• An IP is used to ,
• Address each device connected to
SAITM - RSEA 2012
internet
• Regulate data transfer between devices
10
11. There are two commonly used IP versions at
the moment.
IPv4 – Internet
Protocol version 4
SAITM - RSEA 2012
IPv6 – Internet
Protocol version 6 11
12. IPv4
• Uses 32bit addresses
• Which limits the address in to
4,294,967,296 (4.3 billion) addresses
SAITM - RSEA 2012
• Limited security
• No authentication or encryption at IP
level
• Most commonly used version 12
13. However, By 2014, expected number of
devices that are connected to the internet
is estimated as 50 Billion.[1]
SAITM - RSEA 2012
That is 12 times more than current IPv4 can
support.
13
[1] Internet Corporation for Assigned Names and Numbers (ICANN)
14. So what will happen ?
Do we find ourselves unable to connect to
SAITM - RSEA 2012
the internet via new devices ?
The answer – NO! 14
15. Reason for developing IPv6 is to address
the IPv4 address exhaustion.
SAITM - RSEA 2012
15
16. IPv6
Designed to overcome limitations of
IPv4
SAITM - RSEA 2012
• Uses 128bit addresses
• 340 Undecilion (3.4x1038) addresses
• High security
• Data encryption and authentication 16
17. Features of IPv6
Reduced
Increased
management
address space
requirement
SAITM - RSEA 2012
Better
mobility Security
support 17
18. How do we start using IPv6 ?
SAITM - RSEA 2012
18
19. Methods of IPv6 implementation
There are three main methods ,
• Dual-Stack
SAITM - RSEA 2012
• Translation
• Tunneling 19
20. Dual-Stack
• It operates both IPv4 and IPv6
simultaneously on the same
SAITM - RSEA 2012
infrastructure
20
21. Dual-Stack
Simple, Some
SAITM - RSEA 2012
Uses network
minimum vendors and
resources servers do not
support IPv6
21
22. Translation
• Converting IPv6 traffic into IPv4 traffic for
transportation and vice versa
SAITM - RSEA 2012
• Traffic is not encapsulated, it is directly
converted to the destination type
• Two main methods are used in translate
method 22
23. Translation Methods
• Network Address Translation - Protocol
Translation (NAT-PT)
SAITM - RSEA 2012
• NAT-PT method configure a translation
of an IPv4 address into an IPv6 address
and vise versa either statically or
dynamically
23
24. Translation Methods
• NAT64
• NAT64 mechanism allows IPv6 hosts to
communicate with IPv4 servers
SAITM - RSEA 2012
• The IPv6 client embeds the IPv4 address
it wishes to communicate with and
sends its packets to the resulting address
24
25. Translation
Can deal Not a good
SAITM - RSEA 2012
with option when
different IPv4 uses
types of NAT
protocols 25
26. Tunneling
• Transporting IPv6 traffic through an
IPv4 network transparently
SAITM - RSEA 2012
• Few different tunneling methods
exists for IPv6
26
27. Tunneling Methods
• Manual IPv6 Tunnels
• Manually created IPv6 tunnel is configured
between two routers, that each must support
both IPv4 and IPv6
SAITM - RSEA 2012
• 6to4 Tunnels
• It is IPv6 to be tunneled via IPv4
• 6to4 allows for automatic IPv6-to-IPv4 address
translation, and treats the underlying IPv4
network as one big Non-Broadcast Multi- 27
Access network
28. Tunneling
Used on top Hardware
SAITM - RSEA 2012
of an existing must
IPv4 network support both
IPv4 & IPv6
28
30. IPv6 Readiness
• Compatibility with IPv6 networking is a
software or firmware issue
SAITM - RSEA 2012
• The American Registry for Internet
Numbers (ARIN) has suggested that all
Internet servers to be prepared to serve
IPv6-only clients by 2012
30
31. IPv6 Readiness - Software
• Most personal computers running
recent operating system versions are IPv6-
ready
• Most popular applications with network
SAITM - RSEA 2012
capabilities are ready, and most others
could be easily upgraded with support
from the developers
• Java applications adhering to Java 1.4
(February 2002) standards have support
31
for IPv6
32. IPv6 Readiness - Hardware
• Low-level equipment like network
adapters and network switches may not
be affected by the change
SAITM - RSEA 2012
• since they transmit link-layer frames
without inspecting the contents
• Networking devices that obtain IP
addresses or perform routing based on IP 32
address do need IPv6 support
33. SAITM - RSEA 2012
Finally what should we do ?
33
34. Now, as available IPv4 addresses are almost
over it is the time for ISPs, large and small
companies and universities to start migrating
to IPv6.
SAITM - RSEA 2012
Based on the results of this analysis of the
available technologies it is rewarding to
migrate from IPv4 to IPv6 based on user
requirements. 34
