<div dir="ltr">I find it interesting that they say their clients didn't see it as an issue. Whenever they called and asked if I want transit my answer always was when they had v6 peering to He and Gooogle we could talk.<div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jan 27, 2020 at 12:56 PM Owen DeLong <<a href="mailto:owen@delong.com">owen@delong.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I now longer have a dog in this fight, but “The” peering cake was my project (such as it was)...<br>
<br>
Cogent has, to the best of my knowledge, always had rather large voids in their IPv6 connectivity. To the best of my knowledge, HE and Google are the most significant of these voids, but I believe there are others as well.<br>
<br>
Some quotes I received from Cogent representatives over the years (some may be slightly paraphrased):<br>
<br>
“Hurricane is too small to peer IPv6 with us… They should just buy transit from us.”<br>
“Why should we peer with HE? Our customers aren’t reporting it as a problem.”<br>
“Congested links allow us to pass the savings on to our customers.”<br>
“We see from ARIN whois that you recently registered an ASN. Want to buy transit from us?” (many times over several years)<br>
(This particular violation of the ARIN Whois AUP/TOS eventually resulted in Cogent being suspended from using the service)<br>
<br>
Owen<br>
<br>
<br>
> On Jan 26, 2020, at 22:41 , Large Hadron Collider <<a href="mailto:large.hadron.collider@gmx.com" target="_blank">large.hadron.collider@gmx.com</a>> wrote:<br>
> <br>
> Peering cake? Carbohydrates always entice me to peer... :-)<br>
> <br>
> On Wed, 8 Jan 2020 10:16:12 -0600<br>
> "Aaron Gould" <<a href="mailto:aaron1@gvtc.com" target="_blank">aaron1@gvtc.com</a>> wrote:<br>
> <br>
>> I’m pretty sure cogent has had issues providing full internet connectivity via ipv6 to google and perhaps he (hurricane electric), perhaps others as well, for quite some time now.<br>
>> <br>
>> <br>
>> <br>
>> -Aaron<br>
>> <br>
>> <br>
>> <br>
>> From: NANOG [mailto:<a href="mailto:nanog-bounces@nanog.org" target="_blank">nanog-bounces@nanog.org</a>] On Behalf Of James Breeden<br>
>> Sent: Tuesday, January 7, 2020 7:04 PM<br>
>> To: Rich Kulawiec; North American Network Operators' Group<br>
>> Subject: RE: FYI - Suspension of Cogent access to ARIN Whois<br>
>> <br>
>> <br>
>> <br>
>> Hmm. Wonder if this can be used to cancel some cogent services... I mean, they technically aren't providing access to the full internet now. 🤷♂️🤔<br>
>> <br>
>> <br>
>> <br>
>> <br>
>> <br>
>> <br>
>> <br>
>> Sent via the Samsung Galaxy Note9, an AT&T 5G Evolution capable smartphone<br>
>> <br>
>> <br>
>> <br>
>> <br>
>> <br>
>> <br>
>> <br>
>> -------- Original message --------<br>
>> <br>
>> From: Rich Kulawiec <<a href="mailto:rsk@gsp.org" target="_blank">rsk@gsp.org</a>><br>
>> <br>
>> Date: 1/7/20 7:02 PM (GMT-06:00)<br>
>> <br>
>> To: North American Network Operators' Group <<a href="mailto:nanog@nanog.org" target="_blank">nanog@nanog.org</a>><br>
>> <br>
>> Subject: Re: FYI - Suspension of Cogent access to ARIN Whois<br>
>> <br>
>> <br>
>> <br>
>> On Tue, Jan 07, 2020 at 04:54:22PM -0600, Mike Hammett wrote:<br>
>>> That said, if there's a stern warning about Cogent abusing the system,<br>
>>> maybe their customers finding out is a good thing for the overall<br>
>>> community. ;-)<br>
>> <br>
>> And that is what I would suggest: reply to all queries with a notice<br>
>> that explains what is happening, why it's happening, and provides<br>
>> contact information for Cogent executives: preferably their *personal*<br>
>> email addresses and phone numbers.<br>
>> <br>
>> ---rsk<br>
>> <br>
> <br>
> <br>
> --<br>
> Large Hadron Collider <<a href="mailto:large.hadron.collider@gmx.com" target="_blank">large.hadron.collider@gmx.com</a>><br>
<br>
</blockquote></div>