This report has been generated at Fri Oct 9 21:14:52 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Oct 2 21:14:51 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Sep 25 21:15:27 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Sep 18 21:14:54 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Sep 11 21:14:56 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Sep 4 21:14:47 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Aug 28 21:14:41 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Aug 21 21:14:46 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Aug 14 21:14:47 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Aug 7 21:14:53 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Jul 31 21:14:46 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Jul 24 21:16:32 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Jul 17 21:14:51 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Jul 10 21:14:43 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Jul 3 21:18:39 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Jun 26 21:17:55 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Jun 19 21:14:38 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Jun 12 21:14:37 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Jun 5 21:14:36 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri May 29 21:14:38 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri May 22 21:14:36 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri May 15 21:14:39 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri May 8 21:14:42 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri May 1 21:14:34 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Apr 24 21:14:34 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Apr 17 21:14:32 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Apr 10 21:14:35 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Mar 27 21:14:39 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Mar 20 21:14:21 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Mar 13 21:14:30 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Mar 6 21:14:23 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Feb 27 21:14:26 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Feb 20 21:14:25 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Feb 13 21:14:25 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Feb 6 21:14:23 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Jan 30 21:14:23 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Jan 23 21:14:26 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Jan 16 21:14:25 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Jan 9 21:14:22 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Jan 2 21:14:20 2015 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Dec 26 21:14:48 2014 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Dec 19 21:14:21 2014 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Dec 12 21:14:23 2014 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Dec 5 21:14:20 2014 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Nov 28 21:14:20 2014 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Nov 21 21:14:20 2014 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Nov 14 21:14:18 2014 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Nov 7 21:14:21 2014 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Oct 31 21:14:13 2014 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
Has anyone noticed any issues resulting from the increase?
No
http://www.cidr-report.org/as2.0/#General_Status
But quite interestingly seems like something went wrong with AS13184 around
12:00 UTC.
https://stat.ripe.net/AS13184#tabId=routing
Regards,
Aftab A. Siddiqui
On Wed, Oct 29, 2014 at 10:39 AM, Aftab Siddiqui
aftab.siddi...@gmail.com wrote:
AS13184
http://www.cidr-report.org/cgi-bin/as-report?as=AS13184view=2.0
shows they deaggregated all of their aggregates and leaked that space
to the world (mostly as /23 or /24 subnets of their larger prefixes)
This report has been generated at Fri Oct 24 21:14:12 2014 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Oct 17 21:14:14 2014 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Oct 10 21:14:14 2014 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Oct 3 21:14:05 2014 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Sep 26 21:14:14 2014 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Sep 19 21:14:16 2014 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Sep 12 21:14:14 2014 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Sep 5 21:14:08 2014 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Aug 29 21:14:09 2014 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
This report has been generated at Fri Aug 22 21:14:52 2014 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
It looks great though I would not want to troubleshoot the RIB to FIB
programing errors unless there's a note somewhere saying what abbreviation to
search for in FIB.
The other think that comes to mind is that the more specifics could have
different backup next-hops programed.
adam
From:
This report has been generated at Fri Aug 15 21:14:03 2014 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/2.0 for a current version of this report.
Recent Table History
you mean your vendor won't give you the knobs to do it smartly ([j]tac
tickets open for five years)? wonder why.
Might be useful if you mentioned what you considered a smart way to
trim the fib. But then you couldn't bitch and moan about people not
understanding you, which is the real
On Thu, Aug 14, 2014 at 01:47:20AM -0400, Dorian Kim wrote:
On Thu, Aug 14, 2014 at 12:15:36AM -0400, Patrick W. Gilmore wrote:
Composed on a virtual keyboard, please forgive typos.
On Aug 13, 2014, at 22:59, Suresh Ramasubramanian ops.li...@gmail.com
wrote:
Swisscom or some
It was kindly pointed out to me in private that my phrasing could be
misleading here.
When ACL112 came into being, there were old equipment that were being
protected by the /19 filters. However, the filters were in place long
after those equipment were replaced.
but by then it had driven
Subject: Re: So Philip Smith / Geoff Huston's CIDR report becomes worth a good
hard look today Date: Wed, Aug 13, 2014 at 11:27:46AM -0700 Quoting Merike Kaeo
(mer...@doubleshotsecurity.com):
B: they *did* know about the issue, but convincing management to spend
the cash to buy hardware
I believe at one point, SPRINT had in the RADB (and actively advertised)
0.0.0.0/2, 64.0.0.0/2, 128.0.0.0/2, and 192.0.0.0/2 under something called
“Quarter Default Route, see Rational Default Project” or words to that effect.
I could be wrong. It was a long time ago and I barely remember
On Aug 14, 2014, at 02:36 , Randy Bush ra...@psg.com wrote:
It was kindly pointed out to me in private that my phrasing could be
misleading here.
When ACL112 came into being, there were old equipment that were being
protected by the /19 filters. However, the filters were in place long
When ACL112 came into being, there were old equipment that were being
protected by the /19 filters. However, the filters were in place long
after those equipment were replaced.
This was done for commercial reasons, not to protect the Internet.
You know it, I know it, and I'm pretty sure the
On Wed, Aug 13, 2014 at 8:20 PM, Chris Woodfield rek...@semihuman.com wrote:
Hence the “when programming the TCAM” part of my original statement :)
Hi Chris,
My point was that Randy's BGP RIB pruning knobs are missing for a
different reason than your router FIB pruning knobs. Neither the
: Re: So Philip Smith / Geoff Huston's CIDR report becomes worth a good
hard look today
half the routing table is deagg crap. filter it.
you mean your vendor won't give you the knobs to do it smartly ([j]tac tickets
open for five years)? wonder why.
randy
My point was that Randy's BGP RIB pruning knobs are missing for a
different reason than your router FIB pruning knobs. Neither the
science nor the technology exists to create Randy's BGP pruning knobs.
ahhh, you dug out the [j]tac tickets, or are you just conjecturbating?
if the former, ticket
On Thu, Aug 14, 2014 at 4:57 PM, Randy Bush ra...@psg.com wrote:
My point was that Randy's BGP RIB pruning knobs are missing for a
different reason than your router FIB pruning knobs. Neither the
science nor the technology exists to create Randy's BGP pruning knobs.
ahhh, you dug out the
ahhh, you dug out the [j]tac tickets, or are you just conjecturbating?
Neither.
ROFL. so just ad hominem. smart.
plonk
randy
On Thu, Aug 14, 2014 at 6:07 PM, Randy Bush ra...@psg.com wrote:
ahhh, you dug out the [j]tac tickets, or are you just conjecturbating?
Neither. I'm reporting the state of the science.
ROFL. so just ad hominem. smart.
That phrase ad hominem, I don't think it means what you think it means.
Sent from my Verizon Wireless 4GLTE sm
- Reply message -
From: William Herrin b...@herrin.us
To: Randy Bush ra...@psg.com
Cc: North American Network Operators' Group nanog@nanog.org
Subject: So Philip Smith / Geoff Huston's CIDR report becomes worth a good hard
look today
Date: Thu
I think you mean what is best described here:
http://www.swinog.ch/meetings/swinog7/BGP_filtering-swinog.ppt
--Aris
Suresh Ramasubramanian mailto:ops.li...@gmail.com
Thursday, August 14, 2014 04:59
Swisscom or some other European SP has / used to have a limit where they
would not accept more
Subject: So Philip Smith / Geoff Huston's CIDR report becomes worth a good hard
look today Date: Tue, Aug 12, 2014 at 09:40:55PM +0530 Quoting Suresh
Ramasubramanian (ops.li...@gmail.com):
512K routes, here we come. Lots of TCAM based routers suddenly become
really expensive doorstops.
We
... and then you'll
come back in a few years and buy another one.. mwahahahah.
Yup, folk purchasing these *should* have known (not like there was no
discussions of this), but, well, not everyone spends all day reading
NANOG / RIPE / CIDR report...
W
Hank, you gotta learn to wear respiratory apparatus when
been (and was) easily predicted... Here, buy my widget... and then
you'll come back in a few years and buy another one..
mwahahahah. Yup, folk purchasing these *should* have known (not
like there was no discussions of this), but, well, not everyone
spends all day reading NANOG / RIPE / CIDR
there was no discussions of this), but,
well, not everyone spends all day reading NANOG / RIPE / CIDR
report...
I am not an operator, but I used to be a *really* active routing
engineer once upon a time in the stone age :-) and what really
bothers me is the serious lack of general awareness
On 8/13/14 8:55 AM, Paul Ferguson wrote:
Apologies for replying to my own post, but... below:
On 8/13/2014 7:05 AM, Paul Ferguson wrote:
p.s. I recall some IPv6 prefix growth routing projections by Vince
Fuller and Tony Li from several years ago which illustrated this,
but cannot find
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 8/13/2014 11:09 AM, joel jaeggli wrote:
On 8/13/14 8:55 AM, Paul Ferguson wrote:
Apologies for replying to my own post, but... below:
On 8/13/2014 7:05 AM, Paul Ferguson wrote:
p.s. I recall some IPv6 prefix growth routing projections
there was no
discussions of this), but, well, not everyone spends all day reading
NANOG / RIPE / CIDR report...
W
Hank, you gotta learn to wear respiratory apparatus when working near
open containers of magic router pixie dust - that stuff can screw you up
if you inhale
half the routing table is deagg crap. filter it.
you mean your vendor won't give you the knobs to do it smartly ([j]tac
tickets open for five years)? wonder why.
randy
Same reason no vendor has bothered to prune redundant RIB entries (i.e.
more-specific pointing to the same NH as a covering route) when programming the
TCAM...
-C
On Aug 13, 2014, at 1:42 PM, Randy Bush ra...@psg.com wrote:
half the routing table is deagg crap. filter it.
you mean your
On 14 Aug 2014, at 4:14 am, Paul Ferguson fergdawgs...@mykolab.com wrote:
On 8/13/14 8:55 AM, Paul Ferguson wrote:
Apologies for replying to my own post, but... below:
On 8/13/2014 7:05 AM, Paul Ferguson wrote:
p.s. I recall some IPv6 prefix growth routing projections by
Vince
On Aug 13, 2014, at 16:42 , Randy Bush ra...@psg.com wrote:
half the routing table is deagg crap. filter it.
We disagree.
Just because you don't like all more specifics doesn't mean they are useless.
Not everything is about minimizing FIB size. (And RIB size hasn't been relevant
for
On Wed, Aug 13, 2014 at 6:47 PM, Chris Woodfield rek...@semihuman.com wrote:
On Aug 13, 2014, at 1:42 PM, Randy Bush ra...@psg.com wrote:
half the routing table is deagg crap. filter it.
you mean your vendor won't give you the knobs to do it smartly ([j]tac
tickets open for five years)?
Pruning FIB entries, on the other hand, can be done quite safely as
long as you're willing to accept the conversion of null route to
don't care. Some experiments were done on this in the IETF a couple
years back. Draft-zhang-fibaggregation maybe? Savings of 30% in
typical backbone nodes
On Wed, Aug 13, 2014 at 07:53:45PM -0400, Patrick W. Gilmore wrote:
you mean your vendor won't give you the knobs to do it smartly ([j]tac
tickets open for five years)? wonder why.
Might be useful if you mentioned what you considered a smart way to
trim the fib. But then you couldn't
Swisscom or some other European SP has / used to have a limit where they
would not accept more specific routes than say a /22 from provider x, so if
you wanted to take a /24 and announce it you were SOL sending packets to
them from that /24 over provider y.
Still, for elderly and capacity limited
Once upon a time, Brett Frankenberger rbf+na...@panix.com said:
-- This isn't that hard to implement. Once you have a FIB and
primitives for manipulating it, it's not especially difficult to extend
them to also maintain a minimal-size-FIB.
I would say it is hard to implement, or at least
Composed on a virtual keyboard, please forgive typos.
On Aug 13, 2014, at 22:59, Suresh Ramasubramanian ops.li...@gmail.com wrote:
Swisscom or some other European SP has / used to have a limit where they
would not accept more specific routes than say a /22 from provider x, so if
you
Sprint used to proxy aggregate… I remember 128.0.0.0/3
the real question, imho, is if folks are going to look into their crystal balls
and roadmap where the default offered is a /32 (either v4 or v6)
and plan accordingly, or just slap another bandaid on the oozing wound...
/bill
PO Box
Sprint also had 192/2 in the RADB :)
manning bill wrote:
Sprint used to proxy aggregate… I remember 128.0.0.0/3
the real question, imho, is if folks are going to look into their
crystal balls and roadmap where the default offered is a /32 (either
v4 or v6)
and plan accordingly, or just
On Thu, Aug 14, 2014 at 12:15:36AM -0400, Patrick W. Gilmore wrote:
Composed on a virtual keyboard, please forgive typos.
On Aug 13, 2014, at 22:59, Suresh Ramasubramanian ops.li...@gmail.com
wrote:
Swisscom or some other European SP has / used to have a limit where they
would not
512K routes, here we come. Lots of TCAM based routers suddenly become
really expensive doorstops.
Maybe time to revisit this old 2007 nanog thread?
http://www.gossamer-threads.com/lists/engine?do=post_view_flat;post=99870;page=1;sb=post_latest_reply;so=ASC;mh=25;list=nanog
FYI nanog -
On Tue, 12 Aug 2014, Suresh Ramasubramanian wrote:
Many don't need to buy anything new. Just follow the instructions here:
http://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-switche$
We did this in the 1st week of June. Problem solved.
-Hank
512K routes, here we come.
1 - 100 of 535 matches
Mail list logo
