[PDB Data Ownership-TF] IXP assignment IP address (netixlan) ownership

Terry Sweetser Terry.Sweetser at ix.asn.au
Fri Jan 24 15:30:04 PST 2020

Hi Arnold,

I've added those ideas and concerns.

As Chris has hinted, those interventions are also very good opportunities for some automation to prod and poke networks and IXP for better data.

Terry Sweetser
General Manager, IX Australia
Terry.Sweetser at ix.asn.au
Mobile/WhatsApp: +61455067119

-----Original Message-----
From: DataOwnership-TF <dataownership-tf-bounces at lists.peeringdb.com> On Behalf Of Arnold Nipper
Sent: Saturday, 25 January 2020 9:07 AM
To: DTF PeeringDB <dataownership-tf at lists.peeringdb.com>
Subject: Re: [PDB Data Ownership-TF] IXP assignment IP address (netixlan) ownership

On 24.01.2020 23:53, Terry Sweetser wrote:

> Sheet at
> https://docs.google.com/spreadsheets/d/1GJ-TdK5B3LfBpYT-wDwNv86_HKZpi5
> wy5qY4Gipsvno/edit#gid=1606364876

My understanding of "allow_ixp_update: yes" is that the IX-F importer will update data if it differs. Regardless which fields differ. And it will also create an object if there is none. That was the other main intention to have "allow_ixp_update: yes".

Arnold Nipper
email: arnold at nipper.de
mobile: +49 172 2650958

More information about the DataOwnership-TF mailing list