Re: When IPv4 will exhaust?

Hi,

there is no killer application, IPv4 is running out and you will loose
contact to your customers. As soon as some people have IPv6 only, and
you still stick to IPv4, no communication is possible.

We networkers have to look after the client side of the network (RA adnd
DHCP) and the security side. Firewall rules have to be rewritten, etc.
And taking NAT out of the network is a big change, do not take that easy.

But for certifications like the CCIE it is still not important.

Greetings,

Wilhelm
CCIE #25603 (R&S)

Nadeem Rafi schrieb:
> Thanks a lot ... I appreciate your answer and regarding applications
> your views are correct. Most of the applications at some point use
> "hard coded" ip addresses or simply not aware of IPv6 completely. What
> i can understand, may be "networkers" part will be much simplified
> than OS/Applicaiton Vendor side. OS admins and application vendors may
> be are in different boat than "networkers". For such migration It need
> a lot of effort coupled with huge investments on their part.
> Although IPv6 will exhaust sooner or later, its just a short time but
> can we find out when non-networkers side will be ready to adopt IPv6
> without seeing any monetary benefits? Is there any thing which IPv4
> cannot do and a IPV6 native "killer" application will do? Until a
> "killer" application is in market, there is no compelling reason for
> OS/Application vendors to go with IPv6.
>
> Just my 2 cents..........
>
> Best Regards,
>
> Nadeem Rafi
>
>
> On Sat, Oct 24, 2009 at 8:22 AM, Wilhelm Boeddinghaus
> <wilhelm_at_boeddinghaus.de <mailto:wilhelm_at_boeddinghaus.de>> wrote:
>
> Hi Nadeem,
>
> IPv4 will exhaust, there is no question about this. It does not
> really matter if it happens 2011 or 2012, it is soon.
>
> >From my experience the problem is not turning on IPv6 on an
> interface. Even getting OSPF running is not compliated. But there
> are a few missing parts. On some plattforms OSPF authentication is
> not implemented. There is no IPV6 loadbalancing.
>
> DHCP (address, DNS, etc.) and router advertisements (prefix,
> default gateway) have both to be used to get all needed
> information to a client in your network. So you get two protocols
> for the price of one. The client can change its IPv6 address
> (privacy extensions). Does this affect your firewall and access
> lists? Or the client get 2 IPV6 global unicast addresses, one from
> DHCP, one from RA.
>
> IPv6 works without NAT, so you have public IPv6 addresses on your
> clients in the network. Does this chance anything on the firewall?
>
> All applications need to be checked. For example you web server
> statistics. What do your scripts do with mixed log files? Is there
> GEO ip for IPv6? Have you IPv4 addresse hard coded somewhere in
> your code? Did you use Pv4 addresses as database index?
>
> The company I work for moves to IPv6, slowly, but we see the many
> bigger and smaller tasks that come with IPv6.
>
> I think Cisco should make IPV6 an important part of the CCIE lab.
> It is the protocol we all have to use in the comming years.
>
> Greetings,
>
> Wilhelm
> CCIE #25603 (R&S)
>
> i have come across one interesting counter about IPv4, link
> http://inetcore.com/project/ipv4ec/index_en.html
>
> What experts have views about depletion of IPv4?
>
> Best Regards,
>
> Nadeem Rafi
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Sat Oct 24 2009 - 18:59:59 ART