[c-nsp] Next step-up from 7206VXR

Matthew Huff mhuff at ox.com
Wed Feb 20 10:07:25 EST 2013

Once corporate networks decide they need IPv6 and they look at SHIM6, NPTv6, and multihoming and see how many apps break out of the box, they are going to request /48 Provider Independent (PI) spaces  and advertise them via BGP. Many if not most have been burned by PHB signing telco deals without any buy-in, so they aren't going to want to have to renumber every time some contract is signed/broken. Easy IPv6 corporate prefix renumbering is a myth. Too many one-off embedded devices that barely speak IPv6 and monitoring systems that aren't dynamic and other issues (ACL rewrites, etc...)

The explosion in ipv6 prefixes is coming....

Unless you need the hardware switching capabilities of the 7600/6500 (microbursts, etc), why not use the software routers like the ASR 1000/9000 that have no fixed TCAM limits?

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Seth Mattinen
Sent: Wednesday, February 20, 2013 11:20 AM
To: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] Next step-up from 7206VXR

On 2/20/13 6:13 AM, Mikael Abrahamsson wrote:
> On Wed, 20 Feb 2013, Mack McBride wrote:
>> At 768k you are effectively limiting your IPv6 table to 128k (you
>> can't really go more than that if you expect to use IPv6). I recommend
>> a 640k/192k split.
> Well, I believe IPv4 will hit 640k before IPv6 will hit 128k, so I'd
> recommend 768k/128k instead.

That's what I think too, unless there are too many unchecked idiots that
decide to deaggregate their /30-32 into /48s.

cisco-nsp mailing list  cisco-nsp at puck.nether.net
archive at http://puck.nether.net/pipermail/cisco-nsp/

More information about the cisco-nsp mailing list