- db-wg - mailman.ripe.net

WG Chairs Selection
by Piotr Strzyzewski 16 Nov '16

16 Nov '16

Dear DB-WG Members As agreed during DB-WG session at RIPE69 Meeting in London on 06.11.2014, the WG Chair Selection procedure is executed at yearly intervals. This means that it is about time to run it for the very first time. This is the call for interested parties. Interested parties have 2 weeks to make their interest known on this mailing list. All members of the community are encourage to make a discussion and express their approval or otherwise of the presented candidates. After two weeks the chairs will declare consensus. Since there is a limit of 3 co-chairs, if at the end of the discussion phase there will be more than 3 proposed co-chairs then a call will be made for any of the candidates to withdraw. If there still will be more than 3 candidates then names will be put into a hat and the first three names drawn from the hat will take on the role of chairs for the next 12 months. All three of present co-chairs expressed their interest in being co-chairs for another term. All the best, Job, Nigel & Piotr -- gucio -> Piotr Strzyżewski E-mail: Piotr.Strzyzewski(a)polsl.pl

9 11

Fwd: WG Chairs Selection
by Horváth Ágoston János 04 Nov '16

04 Nov '16

While operational experience is indeed important, the role of a chair is different from a role of a president. I find that a chair will need to invest time, a lot of time, into bringing some much-needed life to the db-wg. The database has not had any notable changes since its original redesign in 1999. All what there was was mostly patchwork than real innovation. As far as I see, this was mainly caused by the lack of general interest. Newbies struggled through the years, but once they learned how to do what they wanted, they were OK with not changing anything on it. This did preserve the status quo. I find the fact that RIPE NCC has a whole-day training course over the use of RIPE DB a sign in itself that it is not for this age. I think no matter who goes as a chair, they have to start breathing life into the WG activities; come up and support real, actual redesign with today's usage patterns, mindset and expectations in mind. That will require precious time that a professional would not have or want to invest. For this reason, I'd like to cast my vote on Denis, knowing that the other chairs would have a more professional background. He does have a lot of good ideas and does have the time and energy to see them through. Cheers, Agoston On Fri, Nov 4, 2016 at 10:32 AM, Job Snijders <job(a)instituut.net> wrote: > On Friday, 4 November 2016, Randy Bush <randy(a)psg.com> wrote: >> >> > What role does the database play in your professional work? >> >> is this repeated question trying to elicit conflict of interest? >> >> and could the current co-chairs also answer it? :) > > > Leadership whom clearly have a stake in the well-being of the database would > have my preference. > > Example: people that work for orgs that depend on the database for their > routing security posture have one up on people who don't even work for a LIR > and as such don't face daily operational reality. > > Last meeting Nigel stated that he wants to step down because he doesn't do > actually work with the database any longer. With new chairs I'd like to > prevent such alienation from the get-go. > > Kind regards, > > Job

1 0

numbered work item suggestion: support PGP authentication with whois-api
by Thomas von Dein 03 Nov '16

03 Nov '16

Hello WG, I'd like to propose an enhancement of the whois REST api to support PGP authenticated POST requests for create,update,delete methods. Currently the API doesn't support this, so you have to use the REST interface to download objects and the MAIL interface to modify them if you don't want to use password authentication. A consistent user interface however, would be more reliable, easier to understand and maintain. Thanks in advance, Thomas von Dein -- Thomas von Dein <admins(a)f-i-ts.net> Finanz Informatik Technologie Service GmbH & Co. KG, OE 76052 Tel:089/94511-8833, Fax:089/94511-8941, http://www.f-i-ts.net

4 4

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