If you have a security/privacy problem that you want to solve playing wack-a-mole with public IP information, you now have two problems.
-- Eric > On 27 Dec 2016, at 13:46, Tim Kleefass <[email protected]> wrote: > > On 27/12/2016 13:11, Lukas Tribus wrote: >>> Die IXP website list the IP address within the customer portal, so you >>> need to login to the IXP customer portal to see the IP addresses of the >>> peers. >> >> That may be true for some IXP's, but most of them provide the list of >> members including IP addresses in the Euro-IX JSON format. >> >> Like: >> https://my.ams-ix.net/api/v1/members.json >> https://www.ecix.net/content/member-lists/memberlist_FRA.json > > Okay, I wasn't aware of that. > Then it doesn't make sense to hide the IP address in peeringdb. > >> And as mentioned before, scanning the reverse dns zone will also >> very likely lead to the next-hop IP's, as do traceroutes. >> >> >> This is a public information, hiding it at peeringdb does not make it >> private. >> >> >> But if people insist, I guess allowing that particular organisations to >> hide the actual address for unauthenticated pdb users may make sense. >> >> >> But please do not allow empty IP fields in the database. > > +1 > > -Tim > > _______________________________________________ > Pdb-tech mailing list > [email protected] > http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-tech
_______________________________________________ Pdb-tech mailing list [email protected] http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-tech
