- db-wg - mailman.ripe.net

out of region ROUTE objects
by denis 25 Oct '16

25 Oct '16

HI guys I know this is a NWI, but with only a 10 minute slot in the agenda to review all the NWIs I doubt much will be discussed. I have a question. This issue has generated an almost identical discussion at the last 4 RIPE Meetings, with the same options on the table and the same indecision at the end of the discussion. In between RIPE Meetings it doesn't seem to be a problem (maybe it isn't a problem at all). I see it is not on either agendas at this meeting for DB or Routing WGs. If it is still a (real) problem, can someone actually make a decision on one of the options to fix it and do something? cheers denis

1 0

Re: [db-wg] Query all route objects for a given AS?
by Ronald F. Guilmette 07 Oct '16

07 Oct '16

In message <2099338805.63709.1475822808834(a)mail.yahoo.com>, denis walker <dw100uk(a)yahoo.co.uk> wrote: >If you type it on the command line you need: >whois -rBGi or AS3333 >which basically says do an inverse query (-i or) on objects containing:origin: AS3333 >give the full object details (-B), without any grouping (-G) and don't return related personal data (-r) >If you use the query.html you must also check 'origin' under the 'Inverse lookup' tab. Thank you. I guess that I must have a very old whois client, because it objected to most of the command line options you listed. But I was able to apply what you said and get the information I wanted from RIPE's web-based WHOIS query page, so that's great. Thanks a lot! Regards, rfg

4 4

Query all route objects for a given AS?
by Ronald F. Guilmette 07 Oct '16

07 Oct '16

Greetings, Sorry if this is an FAQ, but I'd like to know if there is a way to formulate a WHOIS query against whois.ripe.net in a way so as to obtain a complete list of the registered route objects that are associated with a given particular AS. If there's a way to do this, and if someone can instruct me on how it is done, I sure would appreciate that. Thanks.

3 3

Re: [db-wg] Query all route objects for a given AS?
by ripedenis＠yahoo.co.uk 07 Oct '16

07 Oct '16

Hi Ronald If you type it on the command line you need: whois -rBGi or AS3333 which basically says do an inverse query (-i or) on objects containing:origin: AS3333 give the full object details (-B), without any grouping (-G) and don't return related personal data (-r) If you use the query.html you must also check 'origin' under the 'Inverse lookup' tab. I also suggest you check the 'Do not retrieve related objects' box other wise you may return lots of personal data objects and get blocked very quickly. cheersdenis From: Ronald F. Guilmette <rfg(a)tristatelogic.com> To: "db-wg(a)ripe.net" <db-wg(a)ripe.net> Sent: Friday, 7 October 2016, 5:02 Subject: Re: [db-wg] Query all route objects for a given AS? In message <1870001011.3703.1475803719463(a)mail.yahoo.com>, <ripedenis(a)yahoo.co.uk> wrote: >-rBGi or as3333 I'm sorry, but your reply is not at all clear to me. Could you perhaps show me a complete example command line? Regards, rfg P.S. I also just now visited the following page: https://apps.db.ripe.net/search/query.html Under "Types" I checked only "route". Then in the search box I entered only the AS number of interest to me. Then I clicked on the "search" button. The result was that I only got the following error: ERROR:115: invalid search key Search key entered is not valid for the specified object type(s) Is it actually not possible to obtain from the RIPE WHOIS data base a list of all route objects currently associated with a particular AS number?

1 0

Progress on Numbered Work Items September 2016
by Tim Bruijnzeels 29 Sep '16

29 Sep '16

Dear working group, Although there is technically one more day in September I have to send this update now for planning reasons. Last month there were no updates to any of the Numbered Work Items. The list of items and their status is therefore unchanged since the last update. Repeating here for your convenience: NWI-1 Staying on top of abuse contact changes State: Problem Definition 3 messages 3 participants last message: 27 June 16 NWI-2 Displaying history for database objects where available State: Problem Definition 10 messages 5 participants last message: 12 July 16 NWI-3 AFRINIC IRR homing State: Solution Definition 18 messages 8 participants last message: 1 August 16 NWI-4 Role of status: field in multivalued status context State: Problem Definition 4 messages 3 participants last message: 27 June 16 NWI-5 Out of region ROUTE(6) / AUT-NUM objects State: Problem Definition 3 messages 3 participants last message: 28 July 16 NWI-6 Applicable data model not clear from contextless objects State: Problem Definition 3 messages 3 participants last message: 28 June 16 The progress on numbered work items (NWIs) is also available on the web site: https://www.ripe.net/manage-ips-and-asns/db/numbered-work-items Kind regards Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC Database Group

2 1

Call for agenda items, DB-WG meeting during RIPE73, Madrid, Spain
by Piotr Strzyzewski 12 Sep '16

12 Sep '16

Dear DB-WG participants We are reaching out to you for agenda items for the Database Working Group session during the RIPE73 meeting in Madrid, Spain, 24-28 October 2016. The DB-WG session is currently scheduled as usual for Thursday (Oct 27th), starting at 15:00 local time, after the lunch break. The length of our timeslot is 90 minutes. ATTENTION: This time the meeting start and end times have been adjusted by one hour to complement the local Spanish working hours and customs. Please submit your items or topic suggestions directly to the WG chairs or to the list for public discussion. The draft agenda will be published soon. Looking forward to see you all in Madrid. All the best, Job, Nigel & Piotr -- gucio -> Piotr Strzyżewski E-mail: Piotr.Strzyzewski(a)polsl.pl

1 0

RIPE NCC whois REST API
by janemba 12 Sep '16

12 Sep '16

Hi, I would like to know if it is possible to perform a full-text search with the Whois REST API ? Cheers, Janemba

2 1

Clean-up of unreferenced objects in the RIPE Database
by Tim Bruijnzeels 06 Sep '16

06 Sep '16

Dear colleagues, In compliance with data protection rules and the desire to maintain a “clean” database, we plan to remove unreferenced objects from the RIPE Database. We have recently been working on an improved implementation, and we are now ready to re-start the process. In order to be eligible for deletion, objects must have no incoming references (or be a person-maintainer or role-maintainer pair) and must have had no incoming references from any aut-num, domain, inet(6)num, route(6), as-set, filter-set, inet-rtr, peering-set, route-set, rtr-set, as-block, key-cert or irt object during the last 90 days. We have identified roughly 500,000 unreferenced objects in the RIPE Database and have prepared a script to remove these objects in several smaller batches. We will run the first batch to clean up roughly 3,600 role objects today at 16:00 CET. We plan to run an additional batch to clean up roughly 31,000 organisation objects tomorrow morning, and a final batch to clean up roughly 460,000 person objects on Thursday morning. After this, we will continue to run the process nightly to help keep the RIPE Database clean. Further details about the cleanup process are available online: https://www.ripe.net/manage-ips-and-asns/db/support/clean-up-of-unreference… Kind regards, Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC Database Group

1 0

all quiet
by ripedenis＠yahoo.co.uk 02 Sep '16

02 Sep '16

Hi guys It has been pretty quiet on this WG for a while. But I hear from 'sources close to the NCC' that they have been doing some amasing improvements to the Webupdates service. In my day at the NCC there was a manager who said she didn't know what I did (which says more about her than me). One of the many, many, many, many things I did was to let the world know what we were doing. So come on guys, don't be shy, let us all know what is cooking so we can all rejoice in your achievements. cheersdenis

5 5

Locking unmaintained PERSON and ROLE objects in the RIPE Database
by Trudy Prins 01 Sep '16

01 Sep '16

Dear colleagues, The RIPE NCC Executive Board (EB) endorsed a proposal on how to deal with a vulnerability for RIPE Database users. Following their advice, the RIPE NCC proactively locked 848,986 unmaintained PERSON objects and 1,206 unmaintained ROLE objects on 6 April 2016. Since reaching the last /8, IPv4 address space has become more susceptible to hijacking. Unmaintained PERSON and ROLE objects are highly at risk of being found and hijacked. In addition, unmaintained PERSON and ROLE objects are an issue with regards to data protection obligations. The potential impact of abuse led us to consult with the EB on this intermediary solution before engaging with the community on the next steps. Exposing this issue without taking adequate measures would have left the RIPE NCC liable to third party damages. The proposed solution we outline below is a starting point, to be discussed by the community. Background: =========== Since 2010 it has been mandatory to protect PERSON and ROLE objects in the RIPE Database using a maintainer on "mnt-by:". A large number of PERSON and ROLE objects dating from before 2010 are still not protected in this way. Objects can be created that reference these unmaintained objects, but doing so will generate a warning. In recent years, given the scarcity of IPv4 address space, there is a higher risk of people searching for unmaintained PERSON or ROLE objects in order to pose as a resource holder to sell IPv4 space. In the case of legacy space, this could take place outside the view of the RIPE NCC if the address space is not registered with the RIPE NCC. Proposal: ========= 1) All unmaintained ROLE and PERSON objects are now locked. As the RIPE NCC will not be able to correctly check all claims on unmaintained database objects, unlocking is not available. Offering to unlock these objects could leave the RIPE NCC liable to third party damages if due diligence is not followed. 2) Furthermore, the RIPE NCC modifies the existing warning about referencing unmaintained persons/roles to a similar warning about referencing locked persons/roles. 3a) The locked objects can remain as they are. In time, all locked PERSON or ROLE objects no longer referenced by other objects could be automatically deleted: the current thinking is a 180-day deletion timeout for these locked, unreferenced objects. 3b) If there is an operational need, new PERSON or ROLE objects should be created by the object owners. This solution puts control back into the hands of the object owners. The user can follow the existing process for creating and referencing new objects. If there is a use case for supporting bulk migrations where a reference to a locked PERSON or ROLE object should be replaced, the RIPE NCC can create a wizard in the RIPE Database webupdates section of www.ripe.net <http://www.ripe.net/>. We look forward to your feedback. Kind regards, Trudy Prins Manager Software Engineering RIPE NCC

13 24