[PDB-tech] Automated IX customer import

[Ren Provo]

Removing the stale info from a departing IX Member is key for the new IX
Member assigned to the IP in peeringdb.

Not to mention how many times Peering leads write to defunct networks
without knowing it...

On Mon, Jun 22, 2015 at 6:52 AM, Matt Griswold <grizz at 20c.com> wrote:

> * Will Hargrave <will at harg.net> [150622 11:03 +0100]:
> > > The current plan is we'll use the schema at
> > > https://github.com/euro-ix/json-schemas to import IX members as they
> > > change, but will keep it internal until a peer either sets a global
> > > "allow IXes to publish my membership" flag, or approves them
> > > individually. This will definitely be phase two after the rollout.
> > >
> > > Comments?
> >
> > +1 - This is something we’ve wanted for a while. I expect most
> >   networks would just tick this box and get on with life. Our biggest
> >   problem with pdb from an ixp perspective is the trash people put in
> >   the ‘IP address’ field.
> That's the plan, we'll also be putting in validation for IPs entered so
> they're within the public IX blocks, which should eliminate most of the
> garbage.
> _______________________________________________
> Pdb-tech mailing list
> Pdb-tech at lists.peeringdb.com
> http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-tech
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.peeringdb.com/pipermail/pdb-tech/attachments/20150622/27c5acda/attachment.html>