[as112-ops] Setting up AS112 peering sessions

[Matthew Pounsett]

A brief public service announcement for AS112 operators setting up direct
peering:


We get a lot of email to the tech contact address for the ASN that is half of
a direct peering setup conversation between some AS112 operator and some other
network.  It seems many operators use the WHOIS data for establishing the
email address to contact about peering, and do not reply directly to whoever
initiated the peering request.

We generally respond to these with a form email talking about the anycast
nature of AS112 and pointing out how they should go about identifying the
operator they want to talk to.  However...

The very large operators (Amazon, Apple, Google, etc.) tend to send these
emails from "noreply" addresses, and request we reply to our peering
coordinator contact at their organization.  We have no way of knowing who that
might be, and so we don't reply.  These emails are usually followed up a few
days to a week later by another email indicating they're removing the peering
session because "we" have taken no action.

This doesn't cause a problem for OARC, but I feel badly that there are people
out there trying to set up peering and not succeeding.

I'd like to suggest to anyone who is setting up direct peering for their AS112
instance that they be VERY clear with the peering coordinator on the other end
about what email address they should contact for technical issues relating to
that specific peering session, and explain the ways in which AS112 is not like
any other, and that other peering sessions with the same AS may have a
different contact.


-- 
Matt Pounsett
DNS-OARC Systems Engineering
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.dns-oarc.net/mailman/private/as112-ops/attachments/20241018/376a8291/attachment.sig>