[as112-ops] Yahoo Peering Invite at Phoenix IX

[Aleksi Suhonen]

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."