Ú The Internet Engineering Task Force adopted the IPng
model on July 25, 1994.

Ú It is widely expected that IPv4 will be supported

alongside IPv6 for the foreseeable future.
 
 

ځy the beginning of 1992, several proposals appeared

ځy the end of 1992, the IETF announced a call for white
papers and the creation of the IP Next Generation (IPng)
area of working groups.
 Õ

ÚIPv4 provides an addressing capability of 232 or
approximately 4.3 billion addresses

ÚIn the early 1990s, it became clear that this would not
suffice to prevent IPv4 address exhaustion
 Õ

ÚFurther changes to the Internet infrastructure were
needed.

ÚOn February 3, 2011, the last batch of 5 /8 address

blocks were allocated to the Regional Internet Registries.
 
 Õ

1. Larger address space

2. Multicasting
3. Stateless address autoconfiguration (SLAAC)
4. Mandatory support
 Õ

5. Simplified processing
6. Mobility
7. Options extensibility
8. Jumbograms
  
ÿThe most important feature of IPv6 is a much larger
address space than in IPv4

ÿIPv6 addresses are written in eight groups of

four hexadecimal digits separated by colons,
  
¬












 
    


D!"#!$ 
%
&

D!
&  &
'
  
IPv6 addresses are classified by three types of networking
methodologies
Úwnicast addresses identify each network interface.
ÚAny cast addresses identify a group of interfaces.
ÚMulticast addresses are used to deliver one packet to many
interfaces.
ÚThe broadcast method is not implemented in IPv6.
 
  
The 128-bit IPv6 address can be abbreviated with the
following rules:
  
Rule one: Leading zeroes within a 16-bit value may be
omitted.
For example, the
address fe80:0000:0000:0000:0202:b3ff:fe1e:8329 may be
written as fe80:0:0:0:202:b3ff:fe1e:8329
  
Rule two: A single occurrence of consecutive groups of
zeroes within an address may be replaced by a double colon.
For example, fe80:0:0:0:202:b3ff:fe1e:8329 becomes
fe80::202:b3ff:fe1e:8329
  
Õybrid dual-stack IPv6/IPv4 implementations support a
special class of addresses, the IPv4-mapped IPv6
addresses.
  

A number of transition mechanisms are needed to enable
IPv6-only hosts to reach IPv4 services

For the period while IPv6 hosts and routers co-exist with
IPv4 systems various proposals have been made
  

Ú

  
  

 6
 6
 


 6
  

!"



Ú 
 RFC 4214, Intra-Site Automatic Tunnel Addressing
Protocol ISATAP
 RFC 3053, IPv6 Tunnel roker
  

ëual IP stack implementation

Modern hybrid dual-stack implementations of IPv4 and

IPv6 allow programmers to write networking code that
works transparently on IPv4 or IPv6.
 

  

Tunneling

Encapsulating IPv6 packets within IPv4, in effect using

IPv4 as a link layer for IPv6.
 

  

Proxying and translation for IPv6
ÚOne form of address translation is the use of a dual-stack
application layer proxy server.
For example a web proxy.

ÚNAT-like techniques for application-agnostic translation

at the lower layers in routers and gateways have been
proposed.
  

Interfaces
ÚCompatibility with IPv6 networking is mainly a software
issue.
ÚMost personal computers running recent operating system
versions are IPv6-ready.
ÚLow-level equipment like network adapters and network
switches may not be affected by the change.
 
Address Format

Ú##
$
%

Ú& ##'
 (#$)* **)
## 
+##$

$
  
 
wnicast and any cast addresses are typically composed of
two logical parts:

·A 64-bit network prefix used for routing

·A 64-bit interface identifier used to identify a host's

network interface.
 
Special Addresses :

A. wnspecified address
. ëefault Route
C. Local addresses
ë. Pre-ëefined Multicast Addresses
E. Special Purpose Addresses
 
Transition challenges
ÿMany ëNS resolvers in home-networking NAT devices
and routers still handle AAAA records improperly.
ÿSome of these simply drop ëNS requests for such records,
instead of properly returning the appropriate negative
ëNS response
£




  


Efficient, Synchronized uilding Search

Citizens and the Environment

Public Safety