[as112-ops] Yahoo Peering Invite at Phoenix IX

[Matt Griswold]

* Aleksi Suhonen <as112-ops at trex.fi> [170313 14:19 +0200]:
> This could be attributed to a shortcoming in the peeringdb data model:
> it would be nice to be able to designate different peering contacts
> for different places. I'm sure there are other ASNs as well, that
> have regional peering coordinators. I think Google is one such
> example?
> 
> The challenge of course is to find a way to accommodate different
> granularities of regions (per IXP, per Continent, per Country, ...)
> and I don't think it makes sense to try to fix peeringdb to support
> this.

That's what we decided at PeeringDB as well, at least for the time
being.

* Clement Cavadore <clement at cavadore.net> [170313 20:57 +0100]:
> I am not sure that this could be easily doable: Is this mailing list
> posting open to non subscribed members ?
> 
> In my case, I added to my main ASN page (34019) the AS112 peering
> addresses of the anycast node I run on https://as34019.peeringdb.com
> but by experience, people do not really understand.
> 
> Isn't it possible for peeringDB to have a special case for
> https://as112.peeringdb.com with an explanation about how special
> AS112 is, and to have a per-ixp contact ? This is almost impossible
> to have a complete accurate list of IXP-connected instances, but that
> would still be helpful.

We ended up with a semi-solution of listing each IX that offers as112
under the Public Exchange Points at https://as112.peeringdb.com which
is a method most of the bigger networks handle correctly. I agree that
putting a better explanation in the notes section would be a good
thing, however that's still not going to stop automated emails.