- db-wg - mailman.ripe.net

Progress on Number Work Items
by Tim Bruijnzeels 01 Nov '16

01 Nov '16

Dear working group, As usual at the beginning of every month, here is an overview of all open Numbered Work Items. Compared to last month we have seen 6 new messages on NWI-3 - in the RIPE 73 agenda thread. 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 36 messages 11 participants last message: 27 October 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 Regards, Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC Database Group

1 0

Release 1.88 deployed to RC
by Tim Bruijnzeels 31 Oct '16

31 Oct '16

Dear working group, We have released whois version 1.88 to the Release Candidate (RC) environment. We plan to deploy this version to production on Monday 10 October. This release contains a number of small improvements: - Users can now delete syntactically incorrect objects (before you would have to update the object before it could be deleted) - Users are now allowed to change the status if a resource object if it is NOT-SET This release also includes some minor fixes for infrequent bugs, and provides an API that can be used in a future release of the Webupdate User Interface that will allow users to set up rDNS for a prefix and create domain objects in bulk. We are currently working on the latter but expect to have this ready just after the RIPE Meeting. Kind regards Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC Database Group

4 5

Route object authentication for multiple inet(6)num
by fransossen＠yahoo.com 28 Oct '16

28 Oct '16

Hi, Following up on the AP policy WG discussion: https://www.ripe.net/ripe/mail/archives/address-policy-wg/2016-October/0119… If/when implemented it would eventually break up large contiguous inetnums with status ALLOCATED PI/UNSPECIFIED into smaller prefixes. As a consequence, route aggregation will be lost since when the parent inetnum is removed from the RIPE DB, the equivalent route will be removed as well. The current RIPE DB process and rules are not allowing for a /23 route to be created out of two /24s bit boundary contiguous prefixes registered as separate /24s without a common parent range. This is something that could be remedied by allowing a parent route to be created, the system could be rather easily implemented using the current DB rules layout. Existing inetnum objects in DB: inetnum: x.x.x.0/24 mnt-routes: ASXXXX-mnt mnt-by: prefix-holderA-mnt inetnum: x.x.y.0/24 mnt-routes: ASXXXX-mnt mnt-by: prefix-holderB-mnt Submission to the DB update: route: x.x.x.0/23 origin: AS-mnt mnt-by: ASXXXX-mnt authentication credentials for ASXXXX-mnt The DB would currently only look for an exact match and if none found, it will look for a less specific inetnum to authenticate the route creation. So today such an update would get rejected as you would not be able to authenticate whatever is above the /23. If it is changed to look for an exact match, then for more specifics with a matching summary to the route object prefix and then for a less specific, the creation of parent route would be allowed as part of the second step in the checks in the creation logic mechanism. It would not change the current authentication system logic, all will continue to work as it is today. Things to consider: A) Recall mechanism. To allow a prefix holders to recall a route object from a less specific route objects just like they today can with exact match and more specifics. Notifications could then be sent to the involved parties about the route recall having taken place. B) RIPE-NCC-RPSL-MNT! If the above mechanism was to be introduced, that maintainer could then create less specific route for any range, restrictions would need to be implemented in order to prevent mistakes or abuse of RIPE-NCC-RPSL-MNT. C) Adding this to the IRR wizard Alex Band described at the DB WG session. Simple interface and overview of what could be aggregated. D) Could any of this have any negative effect in the RIPE Database? E) Should this also be passed through the routing WG? Cheers, David Hilario

1 0

passwords
by ripedenis＠yahoo.co.uk 27 Oct '16

27 Oct '16

Hi Tim You just said that you can still use passwords with webupdates. I am looking at webupdates right now and I can't see any way to create or update an object using a password. You cannot get past the stage where it says "Login to create" or "Login to update". So where can I enter a password? cheersdenis

2 1

BGP Policy Update Questionnaire (only 3 questions) for research purposes (SNE/OS3 MSc. thesis University of Amsterdam)
by Stavros Konstantaras 27 Oct '16

27 Oct '16

Dear members, First of all, I would like to apologize if you received this message more than once. I am sending this e-mail on behalf of my colleague, Stamatios Maritsas, who is a master student of System and Network Engineering MSc. (SNE/OS3) program at University of Amsterdam and currently conducting his master's thesis project titled: "A decentralized system for automatic exchange of policies for BGP configurations”. The purpose of the questionnaire (only 3 questions :)), that you will find in the following link, is to help him gather important information based on your implemented BGP routing policy, which will help design an exchange policy system in the most efficient way. I want also to inform you that all the data that will be gathered and used will be only for research purposes and fully anonymized. Link of questionnaire: https://docs.google.com/forms/d/e/1FAIpQLSd7TzoYvFGcXAOUWaZa30v-zHeRH8jfm__… <https://docs.google.com/forms/d/e/1FAIpQLSd7TzoYvFGcXAOUWaZa30v-zHeRH8jfm__…> Thank you in advance for your time, and I hope that you can help him/us! Kind Regards, Stavros Konstantaras ---- Stavros Konstantaras Internet Research Engineer, NLnet Labs Science Park 400, 1098 XH, Amsterdam Fingerprint: 4502 7D16 2DF8 ADB0 4AA6 21A9 BF9E EFFF 2744 FE5D

1 0

RIPE 73 DB-WG agenda V1
by Piotr Strzyzewski 27 Oct '16

27 Oct '16

Dear DB-WG Members This is the 1st draft of the agenda for the DB-WG Meeting at RIPE73 at the Meliá Castilla hotel in Madrid, Spain. The DB-WG Meeting is 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. For the overall RIPE 73 meeting plan please refer to its most up-to-date version at https://ripe73.ripe.net/programme/meeting-plan/ Please feel free to comment agenda items or propose additional topics to be discussed both on the mailing list or direct to the WG Chairs at db-wg-chairs(a)ripe.net Looking forward to see you all in Madrid. All the best, Job, Nigel & Piotr ________________________________________________________________________ A. Administrative Matters [~10 min] . Welcome . select scribe (thanks to Nigel for volunteering again!) . finalise agenda . approval of minutes from previous WG meeting(s) B. Review of Numbered Work Items (Job Snijders) [~10 min] C. NWI model - where are we? (Job Snijders) [~10 min] D. DB Operational Update New and revised DB-Software functionality (proposed, test, deployment) Recent DB issues (Tim Bruijnzeels, RIPE NCC) [~15 min] E. Afrinic IRR homing project update (Piotr Strzyżewski) [~10 min] F. Recent work on the UI improvements (Alex Band, RIPE NCC) [~20 min] G. DB-WG - What next? (discussion) [~15 min] Y. Input from other Working Groups and/or Task Forces Z. AOB -- gucio -> Piotr Strzyżewski E-mail: Piotr.Strzyzewski(a)polsl.pl

6 8

Afrinic IRR homing project
by denis 26 Oct '16

26 Oct '16

Hi Piotr I commented some time ago about the possibility of a ROUTE object existing in both the RIPE Database and the Afrinic Database with different content. Did anyone do the simple check to see if any such objects exist? If they do, has anyone thought about who's responsibility it is to decide how to handle them? Has anyone considered what to do with AUT-NUM objects that reference the Afrinic ROUTE objects after they are deleted? At the Warsaw RIPE Meeting I dared to ask the question to the community about the RIPE NCC 'fixing' AUT-NUM objects (apparently a very controversial question). cheers denis

3 2

RIPE 73 DB-WG agenda V2
by Piotr Strzyzewski 26 Oct '16

26 Oct '16

Dear DB-WG Members This is the 2nd draft of the agenda for the DB-WG Meeting at RIPE73 at the Meliá Castilla hotel in Madrid, Spain. The DB-WG Meeting is 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. For the overall RIPE 73 meeting plan please refer to its most up-to-date version at https://ripe73.ripe.net/programme/meeting-plan/ Please feel free to comment agenda items or propose additional topics to be discussed both on the mailing list or direct to the WG Chairs at db-wg-chairs(a)ripe.net Looking forward to see you all in Madrid. All the best, Job, Nigel & Piotr ________________________________________________________________________ A. Administrative Matters [~10 min] . Welcome . select scribe (thanks to Nigel for volunteering again!) . finalise agenda . approval of minutes from previous WG meeting(s) B. WG Chairs Selection & discussion on DB-WG [~15 min] C. Review of Numbered Work Items NWI model - where are we? (Job Snijders) [~15 min] D. DB Operational Update (Tim Bruijnzeels, RIPE NCC) [~15 min] E. Afrinic IRR homing project update (Piotr Strzyżewski) [~10 min] F. Recent work on the UI improvements (Alex Band, RIPE NCC) [~20 min] Y. Input from other Working Groups and/or Task Forces Z. AOB -- gucio -> Piotr Strzyżewski E-mail: Piotr.Strzyzewski(a)polsl.pl

1 0

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 02 Sep '16

02 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

[training] RIPE NCC Training Courses October-December 2016
by Training Services 01 Sep '16

01 Sep '16

Dear colleagues, Our training team travels the RIPE NCC service region to deliver training courses to our members without any additional cost. Over the next few months, we'll be in Yerevan, Bucharest, Amman, Bern, Minsk, Belgrade, Dublin, Athens. Visit the following page to register and to check which training courses we are giving in your area: https://lirportal.ripe.net/training/courses The RIPE NCC delivers the following training courses: - LIR Training Course - RIPE Database Training Course - Basic IPv6 Training Course - DNSSEC Training Course - Measurements Tools Workshop - 2 days Advanced IPv6 Training Course - 2 days BGP Operations and Security Training Course For more information visit: https://www.ripe.net/support/training/courses With kind regards, Rumy Spratley-Kanis Training Services Manager

1 0

Progress on Number Work Items
by Trudy Prins 01 Sep '16

01 Sep '16

Dear working group, as usual at the beginning of every month, here is an overview of all open Numbered Work Items. 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 30 messages 11 participants last message: 16 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 <https://www.ripe.net/manage-ips-and-asns/db/numbered-work-items> Regards, Trudy Prins Manager SWE RIPE NCC

1 0

Re: [db-wg] [anti-abuse-wg] Definition of Abuse - preamble
by Marilson 25 Aug '16

25 Aug '16

Andre, Is praiseworthy your efforts as was the effort by Denis in this group. Sometimes I have the impression that you guys are giving punch in knife tip or barking up the wrong tree. The current discussion seems to seek answers at the semantic. And the idealization of the concepts and definitions begin to collide with the use of a language that is not native to all, as well remembered by Gunther Nitzsche in his last intervention. You are one step closer to doing what Gunther's ancestor did in the century XIX discussing On the Genealogy of Morality (F. Nietzsche) beginning to investigate the root of a single word: the word abuse. What is its genesis? And more importantly, what are the conditions of its genesis? Will discuss in the light of the uses and customs of the present age but there will no consensus. Anyway, I'll put the ball on the ground and try to give my definition of abuse in the most practical way possible, with my English. CAUSE AND EFFECT First remember that I am not an IT professional and I have no concern with possible abuses that ISPs, Registrars and RIRs may suffer. They have professionals and tools to care for themselves. What matters are the billion people on the planet victims of abuse as never before happened. Today the barbarian hordes do not invade the villages with their horses. They remain comfortable and cowardly sitting in front their keyboards stealing and angering millions of people every day - and properly protected and hidden under the cloak of pernicious "protect service". Today barbarians have a new name: coward psychopaths. DEFINITION AND SOLUTION There is nothing more dispensable than the definition of abuse. It is explicit in all AUPs, TOSs and ASPs that govern all contracts between these companies and their customers. Nothing is easier to implement than a solution to end the abuse. I have the perfect recipe: a dose of shame, a dose of honesty, a drop of ethics and a spray jet in the nose with Syntocinon to replace the Oxytocin that the hypothalamus of psychopaths do not produce - empathy. In other words, providers just need to put into practice what their AUPs, TOSs and ASPs, abundantly displayed on their websites, contractually determines. Losses and damage from such abuse are solely the responsibility of those companies. REGULATION AND MODUS OPERANDI If a victim denounces, with evidence, a customer of an ISP, the ISP must contact and warn his customer. If this victim denounce for a second time the same client, the ISP is obliged to penalize his client. In the third complaint ceases to be abuse to be a crime. Here it is characterized conspiracy to the practice of crime. And that is the psychotic posture, dishonest and greedy of most ISPs. No matter if we are denouncing a spammer or scammer. And by insisting on the complaint, copying to various institutions and to the media, the retaliation will be inexorable. Every crime is an abuse but neither all abuse is a crime. PROGNOSIS Nothing will be done. The status quo shall prevail. Marilson

1 0

NWI-3 - AFRINIC IRR Homing
by Job Snijders 16 Aug '16

16 Aug '16

Dear Working Group, (You can review https://www.ripe.net/ripe/mail/archives/db-wg/2016-April/005190.html to ensure you have an overview of the next steps.) NWI-3 - Afrinic IRR Homing -------- In recent years Afrinic set up an IRR instance that enforces authorisation for ROUTE(6) objects at rr.afrinic.net And while the general problem of out-of-region ROUTE(6) and AUT-NUM objects in the RIPE Database IRR, and the problem where the prefix and the ASN belong to different regions is not trivial to resolve, there seems to be a general consensus that simple cases where ROUTE(6) objects have both an ASN and prefix in Afrinic (~34k objects), should appear in the Afrinic IRR where authorisation can be done and not in the RIPE DB. Complicated cases where the prefix is in Afrinic, but the ASN is another region -or- where the ASN in Afrinic, but the prefix is out of region are out of scope for this NWI. -------- Some of you might wonder why this topic is back on the table. The chairs felt that it would be most appropiate to follow our new NWI formal process to help progress this work. Working group participants, if you agree/disagree with the above problem statement please voice your opinion. If you have suggestions to refine the text that is welcome too. Kind regards, Job

12 28

Progress on Number Work Items
by Tim Bruijnzeels 02 Aug '16

02 Aug '16

Dear working group, We currently have the following NWIs: 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

1 0

Conditions for Transferring or Making Available NRTM Data
by Tim Bruijnzeels 01 Aug '16

01 Aug '16

Dear colleagues, Some users of the Near Real Time Mirroring (NRTM) Service may wish to transfer or make data from the service available to third parties. In order to make the process clearer, the RIPE NCC has now published conditions for doing so: https://www.ripe.net/manage-ips-and-asns/db/nrtm-mirroring/conditions-for-t… <https://www.ripe.net/manage-ips-and-asns/db/nrtm-mirroring/conditions-for-t…> If you are interested in using the NRTM Service this way, please follow the link above to read the conditions and find instructions for submitting a request. Kind regards, Tim Bruijnzeels Assistant Manager Database Group RIPE NCC

1 0

NWI-5 - Out of region ROUTE(6) / AUT-NUM objects
by Job Snijders 28 Jul '16

28 Jul '16

Dear Working Group, This is a slighly longer problem statement, please bear with us. There has been a LOT of discussion about the problems related to out-of-region ROUTE(6) and AUT-NUM objects in the RIPE Database. We would like to provide a starting point of the problem definition here, and ask the community to discuss it further. NWI-5 - Out of region ROUTE(6) / AUT-NUM objects ---------- The RIPE Database Internet Routing Registry (IRR) requires authorisation to create ROUTE(6) objects, by the appropriate maintainer for the covering inet(6)num object - or an existing covering ROUTE(6) object for the prefix in the "route(6):" attribute, as well as the appropriate maintainer for aut-num object matching the "origin:". For resources within the RIPE region this authorisation is covered by either: * Objects that RIPE NCC creates upon assigning or allocating resources to LIRs or end-users with a sponsoring LIR * Objects held by legacy resource holders (authorisation may be delegated to others by holders of these objects) However for out-of-region space the authorisation is different. Because out-of-region resources are not maintained in the RIPE Database there are no proper maintainers in the RIPE Database to authorise the creation of such objects. Because there is a need for having ROUTE(6) objects for these routes, and there were no authoritative alternative IRRs available, the RIPE community decided to support the creation of these objects in the RIPE Database IRR through the use of placeholder objects for out-of-region IP resources and ASNs. In case of IP resources the INET(6)NUM objects delegate authorisation to create route objects through "mnt-routes:" to a special use maintainer with a well-known password: RIPE-NCC-RPSL-MNT. In case of out-of-region ASNs the RIPE NCC maintains placeholder AS-BLOCK objects. Since "mnt-routes:" does not exist on AS-BLOCK objects the RIPE-NCC-RPSL-MNT is added to "mnt-lower:" here instead. Any user of the database can therefore create a AUT-NUM object for an out-of-region ASN, and use it to authorise ROUTE(6) objects. There are a number of problems resulting from this approach: * Authorisation for out-of-region objects is anecdotal * Globally duplicate AUT-NUM objects are required for out-of-region ASNs, confusing contact information, policy etc * This facilitates hijacking for out-of-region resources and RIPE NCC is neither mandated nor staffed to deal with these issues. * Detailed placeholders need to be maintained, which causes overhead especially w.r.t. inter-RIR transfers --------- We invite the working group to better define this problem definition so that a structured discussion about (partial) solutions can follow. Kind regards, Job

3 2