[aklug] Re: Alaska peering

On Tue, 8 Jun 2010, Royce Williams wrote:

> Copy that.
>
> Teach me to fish a little, if you would ...how could Joe Admin, without
> any special inside knowledge (that you and I have, Arthur) determine
> what AT&T space to traceroute to in order to confirm the peering? All
> of the IPs that I could determine for myself (NS, MX, your email
> headers, etc.) all either pointed to something Outside, or something
> 70ms away.

Here's what I see to the public IP you posted:

  2 192.234.141.246 3.860 ms 2.718 ms 3.004 ms
  3 12.12.1.1 1.133 ms 0.966 ms 1.024 ms
  4 12.12.2.22 0.929 ms 0.989 ms 1.013 ms
  5 216.67.90.93 1.232 ms 1.210 ms 1.484 ms
  6 209.193.51.252 1.570 ms 1.219 ms 1.240 ms

Don't know why you saw anything other. I also don't know why ICMP seems to
be blocked from your location. ICMP works fine to my IPs coming from a box
I control off of GCI's network.

I'll look into what's happening on our side (12.12.1.x).

> One or the other of each side of the peering attempts probably also had
> some large legal/contractual/red-tape hoops to jump through.

My impression is that it's more for political and/or commercial animosity.
Let's call it what it is.

> So to summarize, these entities peer in Alaska: (doubled up to make
> patterns more clear):
>
> ACS-MTA
> ACS-GCI
> ACS-ATT
> ATT-ACS
> GCI-ACS
> MTA-ACS
>
> ... and these don't:
>
> ATT-GCI
> ATT-MTA
> GCI-ATT
> MTA-ATT
>
> Is this correct?

That would be my impression.

         --Arthur Corliss
           Live Free or Die
---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.
Received on Tue Jun 8 10:19:16 2010