[PDB Data Ownership-TF] IXP assignment IP address (netixlan) ownership
filiz at peeringdb.com
Fri Jan 24 06:24:18 PST 2020
Bringing this to your attention again:
There seems to be support from Product Com as well as some of the TF members for it.
> ---------- Forwarded message ----------
> Date: Thu, 9 Jan 2020 19:18:13 +0000 (UTC)
> From: Chris Caputo <ccaputo at alt.net>
> Reply-To: Chris Caputo <ccaputo-dated-1588965493.0ca23d at alt.net>
> To: DTF PeeringDB <dataownership-tf at lists.peeringdb.com>
> Subject: Re: [PDB Data Ownership-TF] IXP assignment IP address (netixlan)
> ownership (was: conditions for being listed in a facility)
> On Thu, 9 Jan 2020, Arnold Nipper wrote:
>> On 09.01.2020 19:02, Chris Caputo wrote:
>>> I believe the importer needs to perform an additional task:
>>> - populate/update a new database table, potentially known as
>>> netixlan_ixp, which represents the IXP viewpoint.
>>> and once that is implemented, it can cease removing conflicted assignments
>>> unless a network has opted for IX-F JSON automatic updates.
>> There is no reason to do so. See #585  which is ready for implementation.
>>  https://github.com/peeringdb/peeringdb/issues/585
> Arnold, #585 has the word "Interim" in its very title. I am proposing a
> longer term solution that does not put the repeated burden of resolution
> of ownership issues on the Admin Committee. I shared my proposal with the
> PC and got positive feedback, so I have now created an issue for it:
> DataOwnership-TF mailing list
> DataOwnership-TF at lists.peeringdb.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the DataOwnership-TF