August 2019 - db-wg - mailman.ripe.net

GDPR and the RIPE Database
by Edward Shryane 08 Oct '19

08 Oct '19

Dear Working Group, as mentioned in last week's DB-WG meeting, we will shortly be implementing the following changes: - Do not include personal data in historical queries (notify, e-mail, address attributes). - Do not include person/role references in historical queries (admin-c, tech-c, ping-hdl, zone-c). A legal review found we should not return historical contact details, as they may contain personal data, which is not in line with the purpose of the RIPE database or data protection legislation. For background, Maria Stafyla from RIPE NCC Legal presented on this topic at RIPE 76: https://ripe76.ripe.net/presentations/101-GDPR-Database-WG-RIPE-76.pdf Regards Ed Shryane RIPE NCC

4 8

Whois Release 1.95
by Edward Shryane 18 Sep '19

18 Sep '19

Dear Working Group, RIPE Database release 1.95 has been deployed to the Release Candidate environment. If no issues are found, we plan to deploy to production on Monday, 9th September. This release contains two main changes: - Whois queries are now normalised to the latin-1 character set, in the same way as for Whois updates (any non-latin-1 input is normalised into latin-1, or substituted with a question mark). If any normalisation is performed, an extra comment is added to the response to inform the user. - Attributes which can contain personal data (address, e-mail and notify) are filtered out from historical object versions (i.e. when using the --show-version and --diff-versions flags). For a full list of changes, refer to the release notes: https://www.ripe.net/manage-ips-and-asns/db/release-notes/ripe-database-rel… More information on the Release Candidate environment can be found on our website: https://www.ripe.net/manage-ips-and-asns/db/release-notes/rc-release-candid… Please let us know if you find any issues with this release in the RC environment. Regards Ed Shryane RIPE NCC

1 2

Fw: parms for simple answer
by ripedenis＠yahoo.co.uk 27 Aug '19

27 Aug '19

Hi Randy You can also use the restful API described here:https://www.ripe.net/manage-ips-and-asns/db/support/documentation/ripe… for your specific query it returns this: denis$ curl 'http://rest.db.ripe.net/ripe/inetnum/147.28.0.0/16?unfiltered' <?xml version="1.0" encoding="UTF-8"?> <whois-resources xmlns:xlink="http://www.w3.org/1999/xlink"> <objects> <object type="inetnum"> <link xlink:type="locator" xlink:href="http://rest.db.ripe.net/ripe/inetnum/147.28.0.0 - 147.28.255.255"/> <source id="ripe"/> <primary-key> <attribute name="inetnum" value="147.28.0.0 - 147.28.255.255"/> </primary-key> <attributes> <attribute name="inetnum" value="147.28.0.0 - 147.28.255.255"/> <attribute name="netname" value="RG79-147-28"/> <attribute name="country" value="US"/> <attribute name="org" value="ORG-RO47-RIPE" referenced-type="organisation"> <link xlink:type="locator" xlink:href="http://rest.db.ripe.net/ripe/organisation/ORG-RO47-RIPE"/> </attribute> <attribute name="admin-c" value="RB45695-RIPE" referenced-type="person"> <link xlink:type="locator" xlink:href="http://rest.db.ripe.net/ripe/person/RB45695-RIPE"/> </attribute> <attribute name="tech-c" value="RB45695-RIPE" referenced-type="person"> <link xlink:type="locator" xlink:href="http://rest.db.ripe.net/ripe/person/RB45695-RIPE"/> </attribute> <attribute name="status" value="LEGACY"/> <attribute name="mnt-by" value="MAINT-RGNET" referenced-type="mntner"> <link xlink:type="locator" xlink:href="http://rest.db.ripe.net/ripe/mntner/MAINT-RGNET"/> </attribute> <attribute name="mnt-domains" value="MAINT-RGNET" referenced-type="mntner"> <link xlink:type="locator" xlink:href="http://rest.db.ripe.net/ripe/mntner/MAINT-RGNET"/> </attribute> <attribute name="mnt-routes" value="MAINT-RGNET" referenced-type="mntner"> <link xlink:type="locator" xlink:href="http://rest.db.ripe.net/ripe/mntner/MAINT-RGNET"/> </attribute> <attribute name="mnt-by" value="RIPE-NCC-LEGACY-MNT" referenced-type="mntner"> <link xlink:type="locator" xlink:href="http://rest.db.ripe.net/ripe/mntner/RIPE-NCC-LEGACY-MNT"/> </attribute> <attribute name="created" value="2016-03-16T15:16:35Z"/> <attribute name="last-modified" value="2019-08-08T01:21:04Z"/> <attribute name="source" value="RIPE"/> </attributes> </object> </objects> <terms-and-conditions xlink:type="locator" xlink:href="http://www.ripe.net/db/support/db-terms-conditions.pdf"/> </whois-resources> cheersdenis co-chair DB-WG On Tuesday, 27 August 2019, 14:43:41 CEST, Randy Bush via db-wg <db-wg(a)ripe.net> wrote: hi shane, > The '-r' flag seems to disable related answers and is not > type-specific. ``` ran.psg.com:/home/randy> uname -a Linux ran.psg.com 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ran.psg.com:/home/randy> whois -h whois.ripe.net -r 147.28.0.0/16 % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '147.28.0.0 - 147.28.255.255' % Abuse contact for '147.28.0.0 - 147.28.255.255' is 'blackhole(a)bogus.com' inetnum: 147.28.0.0 - 147.28.255.255 netname: RG79-147-28 country: US org: ORG-RO47-RIPE admin-c: RB45695-RIPE tech-c: RB45695-RIPE status: LEGACY mnt-by: MAINT-RGNET mnt-domains: MAINT-RGNET mnt-routes: MAINT-RGNET mnt-by: RIPE-NCC-LEGACY-MNT created: 2016-03-16T15:16:35Z last-modified: 2019-08-08T01:21:04Z source: RIPE % Information related to '147.28.0.0/16AS3130' route: 147.28.0.0/16 descr: RGnet/PSGnet origin: AS3130 mnt-by: MAINT-RGNET created: 1970-01-01T00:00:00Z last-modified: 2003-12-22T01:59:14Z source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.94.1 (ANGUS) ```

1 0

parms for simple answer
by Randy Bush 27 Aug '19

27 Aug '19

is there no parm to whois which results only in the specific answer, not also the org: person: and grandmother: objects? i want it irrespective of object type i am looking up. ``` whois -h whois.ripe.net -r -T inetnum 147.28.0.0/16 | egrep -v '^($|%)' ``` is opbject-type specific randy

4 5

AUT-NUM authorization on ROUTE(6) objects
by Sander Steffann 27 Aug '19

27 Aug '19

Hi, I was looking at https://www.ripe.net/manage-ips-and-asns/db/support/documentation/ripe-data… That page still documents that "the creation of a route object also needs authorisation from the AS Number that originates the route". I thought that requirement got removed some time ago. Am I confused or does the documentation need updating? Cheers, Sander

4 4

Extending Unreferenced Object Cleanup
by Edward Shryane 21 Aug '19

21 Aug '19

Dear Working Group, as presented at last week's DB-WG meeting, I'd like to extend the current Unreferenced Object Cleanup: https://www.ripe.net/manage-ips-and-asns/db/support/clean-up-of-unreference… which deletes the following unreferenced objects after 90 days: - organisation, mntner, person, role objects - mntner - person/role pairs to also delete the following groups of unreferenced objects after 90 days: - mntner - organisation pairs - organisation - person/role pairs - mntner - person/role - organisation groups This change affects a small number of objects in the database, but is consistent with the goal of removing unnecessary data. Please give me your feedback on this proposal, in particular if there are operational reasons to retain this data. Regards Ed Shryane RIPE NCC

4 4

ORG record vetting ?
by Ronald F. Guilmette 05 Aug '19

05 Aug '19

Just a point of curiosity... For each newly created ORG record that is put into the data base, if the ORG record represents something other than a natural person, does NCC staff make any effort to check to make sure that the alleged non-person entity actually exists, I mean, you know, as a legal entity, somewhere on planet earth? Or is this just another one of those niceties that cannot, in practice, be performed within the RIPE region because the membership has not explicitly approved it? Regards, rfg

10 35

ORG vetting redux
by Ronald F. Guilmette 02 Aug '19

02 Aug '19

I have a trivial little Perl program called "dupcount" that does exactly what its name implies. I ran it on a fresh copy of the database, as part of a command pipeline as follows: % gzcat ripe.db.gz | grep '^org-type:' | dupcount Results were as follows: 99651 org-type: OTHER 24055 org-type: LIR 1131 org-type: Other 1034 org-type: other 3 org-type: OTher 1 org-type: RIR 1 org-type: IANA 1 org-type: WHITEPAGES 1 org-type: OTHEr I gather from this that case should generally be ignored when parsing this field value. Would it also be appropriate to assume that LEGACY number resources have generally been associated with ORG records of type OTHER? Have any or all of those ORGs ever been vetted in any way? And what about number resources that are presently associated with no ORG whatsoever, for example, the following ones? I am having a bit of trouble understanding how a <<void>> organization gets (or got) vetted by NCC. (I should perhaps clarify that of the following 120 ASNs, fully 108 of them are listed as status: LEGACY, however that leaves another 12 wih status: ASSIGNED, and for those, and also the LEGACY ones, the vetting, if any, that has been applied seems to me to be a at least a bit ambiguous.) AS248 AS249 AS250 AS528 AS529 AS544 AS590 AS593 AS697 AS709 AS710 AS712 AS761 AS764 AS777 AS1110 AS1112 AS1114 AS1115 AS1116 AS1118 AS1119 AS1121 AS1122 AS1123 AS1124 AS1126 AS1135 AS1137 AS1203 AS1234 AS1241 AS1253 AS1257 AS1270 AS1271 AS1272 AS1273 AS1274 AS1279 AS1290 AS1304 AS1318 AS1342 AS1352 AS1353 AS1653 AS1654 AS1663 AS1732 AS1739 AS1748 AS1752 AS1774 AS1780 AS1833 AS1835 AS1837 AS1889 AS1893 AS1903 AS1921 AS1922 AS1923 AS1960 AS1961 AS1962 AS1967 AS2004 AS2012 AS2016 AS2017 AS2026 AS2028 AS2029 AS2036 AS2045 AS2049 AS2147 AS2148 AS2481 AS2487 AS2494 AS2529 AS2530 AS2578 AS2609 AS2643 AS2921 AS3151 AS3843 AS3917 AS3918 AS4148 AS4457 AS4458 AS4524 AS4588 AS4589 AS4974 AS6067 AS6168 AS6412 AS8093 AS8346 AS8452 AS11341 AS11660 AS15808 AS18732 AS19376 AS20598 AS21042 AS21174 AS21491 AS22627 AS24691 AS25429 AS29032 AS29039

2 2