[as112-ops] Yahoo Peering Invite at Phoenix IX

Joe Abley jabley at hopcount.ca
Fri May 26 10:11:19 UTC 2017


Hi Aleksi!

(Sorry for any horrible formatting; I'm typing on an iPad.)

If we use the mailing list as a contact, then we need to be prepared for either (a) mail to bounce when non-subscribers send it, or (b) the mailing list to be opened to posts from non-subscribers, which means it's going to start receiving spam.

An alternative would be to ask the nice DNS-OARC people whether they are happy to act as a point of contact (and to own e.g. the PeeringDB record), and to relay requests to the list or to individual operators as necessary. This is in line with the other support they provide to the project, e.g. looking after the as112.net domain, hosting this list, etc.


Joe

> On May 26, 2017, at 13:03, Aleksi Suhonen <as112-ops at trex.fi> wrote:
> 
> Hello,
> 
>> On 05/24/2017 04:18 PM, Nick Hilliard wrote:
>> Joe Abley wrote:
>>> In the second case I'm not sure I precisely understand what is 
>>> needed. Is the problem that the AS112 node at FooIX has NOC/ops 
>>> contact info that is different from the AS112 node at BarIX? Or is 
>>> this more like a PeeringDB schema problem, that it's hard for more 
>>> than one person to administer records related to AS112? Or something 
>>> else?
> 
>> these companies have their own provisioning systems which pull data from
>> peeringdb and other sources.  The problem is that that they usually
>> assume that there is a 1:1 relationship between ASN and organisation,
>> not a 1:n relationship as you would need in the case of as112.  This is
>> further exacerbated by assuming that there is a 1:1 relationship between
>> an organisation and its list of NOC contact points.  BTW, this is
>> usually quite a good optimisation to make because it simplifies data
>> structures and data management.  But it breaks with as112.
> 
> As nobody seemed to oppose it, I suggest we reduce the relationship to
> 1:1 for AS112 as well, as far as PeeringDB is concerned: Let's strip all
> other contacts from PeeringDB, and add this mailing-list as the first
> and only point of contact?
> 
> The bigger problem seems to be that not all IX node operators are on
> this list. At least I've never heard from anyone at Phoenix IX after
> lots of messages on this list...
> 
> My two cents,
> 
> -- 
>    +358 44 9756548 / http://www.trex.fi/
>    Aleksi Suhonen / TREX Regional Exchanges Oy
> 
>    You say "potato", I say "closest-exit."
> _______________________________________________
> as112-ops mailing list
> as112-ops at lists.dns-oarc.net
> https://lists.dns-oarc.net/mailman/listinfo/as112-ops



More information about the as112-ops mailing list