[141519] in North American Network Operators' Group
RE: Cogent & HE
daemon@ATHENA.MIT.EDU (Paul Stewart)
Wed Jun 8 17:24:23 2011
From: "Paul Stewart" <paul@paulstewart.org>
To: "'Jay Hanke'" <jay.hanke@mankatonetworks.com>
In-Reply-To: <BANLkTimzvQLkvv-8GTgWw-hSQmMFnKZj6Q@mail.gmail.com>
Date: Wed, 8 Jun 2011 17:23:18 -0400
Cc: nanog@nanog.org, 'Ken Chase' <ken@sizone.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
For what it's worth, we have a number of IPv6 peers in place plus IPv6
transit from Level(3), HE, and TiNet.=20
For downstream customers, we are currently exporting them 6250 prefixes =
on
IPv6.
>From TiNet we are getting 6168 prefixes
>From Level(3) we are getting 4933 prefixes
>From HE we are getting 5990 prefixes
Hope this helps a bit ;)=20
-p
-----Original Message-----
From: jayhanke@gmail.com [mailto:jayhanke@gmail.com] On Behalf Of Jay =
Hanke
Sent: June-08-11 4:47 PM
To: Paul Stewart
Cc: Ken Chase; nanog@nanog.org
Subject: Re: Cogent & HE
On Wed, Jun 8, 2011 at 3:19 PM, Paul Stewart <paul@paulstewart.org> =
wrote:
> Or peer with HE and buy transit from Cogent (or someone on Cogent's
friendly
> list) - this is where I think their strategy is going to go after a =
while
> with a lot of folks (if they have the option - that's the key). =A0HE =
will
> peer with anyone I believe - Cogent has much more stringent "tier1" =
rules
on
> peering.
How divided is the table? I see about 98 routes transiting Cogent ASN
via a HE connection. Customer has only has HE as v6 upstream. An
previous post listed about a 1300 prefix difference. That's pretty
significant unless it's due to aggregation or something. I'd also be
interested to see the size of the other major carriers v6 tables so I
can patch a whole until the other upstream is ready.
Jay
