IPv6 BGP table size comparisons

A week or more ago someone posted in NANOG or elsewhere a site that had made
a comparison of the IPv6 BGP table sizes of different operators (i.e. HE,
Cogent, Sprint, etc), making the point that a full view might take multiple
feeds. I think that website also had text files with the comparisons.

But I can't find that e-mail or website anywhere!

Does anyone know where that listserv posting or website is?

Frank

Maybe this is a good place to start..

http://www.sixxs.net/tools/grh/compare/

- Jared

Jared Mauch wrote:

Maybe this is a good place to start..

http://www.sixxs.net/tools/grh/compare/

- Jared

A week or more ago someone posted in NANOG or elsewhere a site that had made
a comparison of the IPv6 BGP table sizes of different operators (i.e. HE,
Cogent, Sprint, etc), making the point that a full view might take multiple
feeds. I think that website also had text files with the comparisons.

But I can't find that e-mail or website anywhere!

Does anyone know where that listserv posting or website is?

Also route-views6.routeviews.org has several feeds.

- Kevin

Thanks. I think the DFP might be a better fit, but right now it's timing
out.

Frank

Whip yours out and lets have an on list comparison of table sizes

:smiley:

Size doesn't matter. It's how well you use it.
   Route it, baby...
   ;)

There are 4,035 routes in the global IPv6 routing table. This is what one
provider passed on to me for routes (/48 or larger prefixes), extracted from
public route-view servers.
  AT&T AS7018: 2,851 (70.7%)
  Cogent AS174: 2,864 (71.0%)
  GLBX AS3549: 3,706 (91.8%)
  Hurricane Electric AS6939: 3,790 (93.9%)
  Qwest AS209: 3,918 (97.1%)
  TINET (formerly Tiscali) AS3257: 3,825 (94.8%)
  Verizon AS701: 3,938 (97.6%)

Frank

Not sure what route-server you are speaking of, but a quick peek at what we send on a customer session I see:

NTT (2914) sends 3868 prefixes.

If the route server contacts me in private, we can likely set up a view from 2914 or 2914-customer perspective.

- Jared

The provider who gave me the information didn't tell me what public route
server they used. They didn't analyze all ASNs, just the handful I listed.

It would be interesting if someone set up a daily report that documented all
the IPv6 routes an ASN carried, and then tracked both the absolute numbers
and percentages over time.

Frank

Here's what I see:

Level 3: 2949
HE: 3775
NTT: 3867
Init7: 3665

Mike

TATA (AS6453) out of Toronto, Canada 3,747.

For my v4 transit, I only see 0.3% difference from my largest and
smallest view. Where as with ipv6, the difference is almost 25%. For
/48 and shorter, I see 757 paths missing from AS174 that I see on my
other 2 v6 transit providers.

  ---Mike

While looking at whats missing, I found this interesting /48.

+2607:fed0::/32
+2607:fed8::/32
+2607:ff08:cafe::/48
+2607:ff20::/32

The 2607:ff08::/32 is visible on Cogent. But I guess they are not
serving coffee there, only on TATA and HE.

  ---Mike

Does this mean Verizon is carrying PI /48s now?

~Seth

HE routes missing on Cogents side?

Yes they are.

Mike

Looks like AS13722 (Default Route, Inc), is advertising both
2607:ff08:cafe::/48 and 2607:ff08::/32.

Frank

I could not find this information on any Wikis, but this is the sort
of thing that would be nice to be able to find out without posting on
the list or asking around (obviously.) I have quickly made a couple
of entries with simple enough formatting that anyone can go onto
Wikipedia, click Edit, and add what they know. This is sure to become
a frequently asked question before the answer is always "yes" given
that some major transit-free networks have no functional IPv6
capability of any kind.

http://en.wikipedia.org/wiki/Comparison_of_IPv6_support_by_major_transit_providers

HE routes missing on Cogents side?

I would guess HE routes missing at Cogent and Cogent routes missing at HE.
Remember the cake?

http://www.datacenterknowledge.com/wp-content/uploads/2009/10/Hurricane-Cake
.jpg

Or was that rectified? Mahtan?

Randy

Actually it depends on the # of route injects and withdrawls.

Sorry, couldn't help myself.

-Hank

'Maximum Prefix Length' may be an over-simplifying metric. FWIW, we're certainly not a major transit provider, but we do allow /48 in the designated PI ranges but not in the PA ranges. So the question is not necessarily just about the prefix length used because it might vary by the prefix.