When I last spoke to them, it sounded like they were using a bunch of LAG groups based on ip address because they _really_ wanted to know how many ip addresses we had and what kind of traffic we would be expecting (eyeball networks, big data transport, etc).
-----Original Message-----
From: "David Hubbard" <dhubbard@dino.hostasaurus.com>
Sent: Wednesday, October 14, 2020 1:46pm
To: "nanog@nanog.org" <nanog@nanog.org>
Subject: Re: Cogent Layer 2
I had a discussion with them about a point to point circuit last year and ran into some weirdness around how burstable it would be for specific IP to IP streams as our use case was cheap circuit / high speed data replication between given endpoints. The sales rep was suggesting to me that I’d see specific source/destination IP pairs capped at 2gbps regardless of circuit speed, which suggested to me it was not actually a point to point wave but some type of encapsulated service. We didn’t get into whether it was usable for non-IP, etc.
From: NANOG <nanog-bounces+dhubbard=dino.hostasaurus.com@nanog.org> on behalf of Mike Hammett <nanog@ics-il.net>
Date: Wednesday, October 14, 2020 at 1:38 PM
To: "nanog@nanog.org" <nanog@nanog.org>
Subject: Cogent Layer 2
Are any legitimate beefs with Cogent limited to their IP policies, BGP session charges, and peering disputes? Meaning, would using them for layer 2 be reasonable?