<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: arial,helvetica,sans-serif; font-size: 10pt; color: #000000'>The part that has me uneasy about that action is that the chance that Cogent sales reps are using Cogent IPs is probably low. They're probably doing this work at home. They wouldn't be blocked at all.<div><br></div><div><br></div><div>Also, the chance that there are people that wish to use ARIN Whois services that are not Cogent employees and yet come from Cogent IP space is quite high. They would be blocked and yet, didn't do anything.<br><br><br>That said, if there's a stern warning about Cogent abusing the system, maybe their customers finding out is a good thing for the overall community. ;-)<br><br><div><span name="x"></span><br><br>-----<br>Mike Hammett<br>Intelligent Computing Solutions<br>http://www.ics-il.com<br><br>Midwest-IX<br>http://www.midwest-ix.com<span name="x"></span><br></div><br><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Matt Harris" <matt@netfire.net><br><b>To: </b>"Martin Hannigan" <hannigan@gmail.com><br><b>Cc: </b>"John Curran" <jcurran@arin.net>, "North American Network Operators' Group" <nanog@nanog.org><br><b>Sent: </b>Tuesday, January 7, 2020 4:48:58 PM<br><b>Subject: </b>Re: FYI - Suspension of Cogent access to ARIN Whois<br><br><div dir="ltr"><div dir="ltr">On Tue, Jan 7, 2020 at 4:46 PM Martin Hannigan <<a href="mailto:hannigan@gmail.com" target="_blank">hannigan@gmail.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div><br></div><div><br><div class="gmail_quote"></div></div></div><div><div dir="ltr" class="gmail_attr">On Tue, Jan 7, 2020 at 08:51 John Curran <<a href="mailto:jcurran@arin.net" target="_blank">jcurran@arin.net</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">On 7 Jan 2020, at 5:01 AM, Martijn Schmidt via NANOG <<a href="mailto:nanog@nanog.org" target="_blank">nanog@nanog.org</a>> wrote:<br>
> <br>
> Out of curiosity, since we aren't affected by this ourselves, I know of cases where Cogent has sub-allocated IP space to its customers but which those customers originate from their own ASN and then announce to multiple upstream providers.<br>
> <br>
> So while the IP space is registered to Cogent and allocated to its customer, the AS-path might be something like ^174_456$ but it's entirely possible that ARIN would observe it as ^123_456$ instead. Are such IP address blocks affected by the suspension?<br>
<br>
As noted earlier, ARIN has suspended service for all Cogent-registered IP address blocks - this is being done as a discrete IP block access list applied to relevant ARIN Whois services, so the routing of the blocks are immaterial - a customer using a suballocation of Cogent space could be affected but customers with their own IP blocks blocks that are simply being routed by Cogent are not affected. </blockquote><div dir="auto"></div></div><div><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"></blockquote>
</div><div dir="auto"><br></div><div dir="auto">This is a disproportionate response IMHO. $0.02</div><div dir="auto"><br></div><div dir="auto">YMMV,</div><div dir="auto"><br></div><div dir="auto">-M<</div></blockquote><div><br></div><div>Seems entirely reasonable to me. You break the rules, you lose the privilege. Works the same way with my 7 year old. </div><div><br></div></div></div>
</div><br></div></div></body></html>