On Friday, June 03, 2011 11:04:38 PM arulgobinath emmanuel
wrote:
I thought the memory requirement might high but the total
memory for /48 range routes and couple of static routes
[show memory summary | inc IPv6] summing up only around
~4mb
There's only +/-6,000 IPv6 entries in the BGP
On Friday, June 03, 2011 06:55:38 PM Justin M. Streiner
wrote:
That said, there are some
people who don't filter (much), so it's not unusual to
see smaller prefixes show up in the global v6 view.
I suppose old habits die very hard!
Clearly, v4 hasn't taught some of us anything.
Mark.
On Friday, June 03, 2011 10:25:30 PM arulgobinath emmanuel
wrote:
Hi all,
what is the current industry practices in IPv6 inbound
prefix filter is it /32 or /48 ? or it depends on the
global IPv6 prefix growth vs memory ?
We filter up to a /48.
/48 tends to be the informally agreed limit,
Hi all,
what is the current industry practices in IPv6 inbound prefix filter is it
/32 or /48 ? or it depends on the global IPv6 prefix growth vs memory ?
Regards,
Gobinath.
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
On Fri, 3 Jun 2011, arulgobinath emmanuel wrote:
what is the current industry practices in IPv6 inbound prefix filter is it
/32 or /48 ? or it depends on the global IPv6 prefix growth vs memory ?
As always, your experience may vary, but it seems like many operators are
starting to settle on
I thought the memory requirement might high but the total memory for /48
range routes and couple of static routes [show memory summary | inc IPv6]
summing up only around ~4mb
On Fri, Jun 3, 2011 at 4:25 PM, Justin M. Streiner
strei...@cluebyfour.orgwrote:
On Fri, 3 Jun 2011, arulgobinath
Hi,
On Fri, Jun 03, 2011 at 08:34:38PM +0530, arulgobinath emmanuel wrote:
I thought the memory requirement might high but the total memory for /48
range routes and couple of static routes [show memory summary | inc IPv6]
summing up only around ~4mb
There's only a few thousand IPv6 routes
