- db-wg - mailman.ripe.net

[training] RIPE NCC Training Courses January-March 2016
by Training Services 07 Dec '15

07 Dec '15

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 Amsterdam, London, Toulouse, Prague, Baku, St. Petersburg, Helsinki, Vilnius, Chisinau, Bishkek. 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 - 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

anyone using the RIPE Databse MUST now have an SSO account?
by ripedenis＠yahoo.co.uk 02 Dec '15

02 Dec '15

Hi guys When was it discussed, agreed or announced that Webupdates will no longer allow objects to be created or updated with a password? As Webupdates is the only way to access an unfiltered version of your own MNTNER object, it is no longer possible to even retrieve a version of your own MNTNER without signing up for an SSO account. I did not realise this has become mandatory. So has it been agreed that SSO is the only authorisation method allowed to access the RIPE Database? Did I miss the announcement that passwords and PGP are being deprecated? cheersdenis

6 6

revisiting rpsl-related set of rcf documents?
by Wilfried Woeber 26 Nov '15

26 Nov '15

Following up on the discussion here, during the DB-WG session in Bucharest, where changes to different aspects of using the RIPE registry database - including a reference to discussions relating to cross-RIR authorisation - I'd like to ask the following question to the community: Is it about time to revisit the set of RFCs and either get them updated to properly reflect the (more) current reality, or consciously have them declared historic and overtaken by events? What's your point of view? Thanks, Wilfried

6 7

RIPE TEST DATABASE REST INTERFACE PROBLEM
by PRANEETH, MANASVI 25 Nov '15

25 Nov '15

Hi, I have created a maintainer EIPAM-MNT for testing the ripe rest in Test system. But looks like the query/update function is not working through rest Interface. Can you confirm whether the RIPE REST is working for TEST database. [cid:image001.png@01D125DE.B2187610] Request sent: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <whois-resources> <objects> <object type="INET6NUM"> <source id="TEST"/> <attributes> <attribute name="inet6num" value="2001:1be0:1000:1e::/64"/> <attribute name="netname" value="EIPAMGUYATT"/> <attribute name="descr" value="EIPAMGUYATT"/> <attribute name="country" value="US"/> <attribute name="admin-c" value="EP1-TEST"/> <attribute name="tech-c" value="EP1-TEST"/> <attribute name="status" value="ASSIGNED"/> <attribute name="mnt-by" value="EIPAM-MNT"/> <attribute name="mnt-lower" value="TEST-DBM-MNT"/> <attribute name="source" value="TEST"/> </attributes> </object> </objects> </whois-resources> Response received: Errormessage part: <errormessages> <errormessage severity="Error" text="Authorisation for [%s] %s failed using "%s:" no valid maintainer found "> <args value="inet6num"/> <args value="2001:1be0:1000:1e::/64"/> <args value="mnt-by"/> <args value=""/> </errormessage> <errormessage severity="Error" text="The maintainer '%s' was not found in the database"> <args value="EIPAM-MNT"/> </errormessage> <errormessage severity="Error" text="Unknown object referenced %s"> <attribute name="tech-c" value="EP1-TEST"/> <args value="EP1-TEST"/> </errormessage> <errormessage severity="Error" text="Unknown object referenced %s"> <attribute name="mnt-by" value="EIPAM-MNT"/> <args value="EIPAM-MNT"/> </errormessage> <errormessage severity="Error" text="Unknown object referenced %s"> <attribute name="admin-c" value="EP1-TEST"/> <args value="EP1-TEST"/> </errormessage> <errormessage severity="Info" text="To create the first person/mntner pair of objects for an organisation see https://apps.db.ripe.net/startup/"/<https://apps.db.ripe.net/startup/%22/>> </errormessages> Thanks, Manasvi praneeth Nannapaneni INSTAR-EIPAM Development/office:(636) 544-5448/mp418b(a)att.com<mailto:(636)%20544-5448/mp418b@att.com>

2 2

Database release 1.83 deployed to RC environment
by Alex Band 24 Nov '15

24 Nov '15

Dear colleagues, We are happy to announce the deployment of RIPE Database software release 1.83 to the Release Candidate (RC) environment, which has gone live on Friday 30 October. This release is still focussed on seamlessly integrating RIPE NCC Access (SSO) into the webupdates user interface. In addition, several other changes have been made, such as: - Webupdates will show full object details by default - Partial route object creation has been greatly improved, indicating which maintainer needs to complete the authorisation - When deleting a person object, you will be prompted to also delete the associated maintainer if it has no other dependencies - When trying to delete an object that is still referenced, you will get a list of blocking objects - Auto-complete of person, role and organisation attributes is now available throughout the interface - The TEST database now has its own URL instead of having to be selected with a radio button Please let us know if you have any questions or comments. Kind regards, Alex Band Product Manager RIPE NCC

3 4

RIPE 72 minutes
by Nigel Titley 19 Nov '15

19 Nov '15

Folks Here is the first cut at the minutes. Comments (and particularly complaints about missing/additional action points) to me All the best Nigel

1 0

RIPE 71 DB-WG agenda V4
by Piotr Strzyzewski 19 Nov '15

19 Nov '15

Dear DB-WG Members This is the 4th draft of an agenda for the DB-WG Meeting at RIPE71 at the JW Marriott Bucharest Grand Hotel in Bucharest, Romania. The DB-WG Meeting is scheduled as usual for Thursday, Nov 19th, starting at 14:00 local time, after the lunch break. The length of our timeslot is 90 minutes. For the overall RIPE 71 meeting plan please refer to its most up-to-date version at https://ripe71.ripe.net/programme/meeting-plan/ Although the agenda is fully packed right now, 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 Bucharest. All the best, Job, Nigel & Piotr ________________________________________________________________________ A. Administrative Matters [~5 min] . Welcome . select scribe (thanks to Nigel for volunteering again!) . finalise agenda . approval of minutes from previous WG meeting(s) . review of action list (Nigel Titley) B. Database Updates (Tim Bruijnzeels, RIPE NCC) [~30 min] . operations . new functionality . "changed:" deprecation . Implementation proposal descr line . restrict usage of RIPE-NCC-RPSL-MNT . other aspects . personalised authentication C. Updated Database documentation (Alex Band, RIPE NCC) [~10 min] D. Routing policies vs. reality in BGP (Tomas Hlavacek) [~15 min] E. Afrinic IRR (Michel Odou) [~10 min] Afrinic IRR homing project update (Tim Bruijnzeels, RIPE NCC) [~10 min] F. ROUTE object authorisation update (Job Snijders) [~5 min] G. Control over associating objects for number blocks (William Sylvester) [~5 min] X. Heads up about recent discussions at db-wg mailing list 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

Bootstraping a new private whois instance
by CUBIC, SCOTT 18 Nov '15

18 Nov '15

Hi all, I'm new to the db-wg, and I'm just beginning to explore the code from https://github.com/RIPE-NCC/whois.git. I'd like to use the code to run a private whois server to integrate with our Infoblox IPAM system. I've cloned the repository and followed the instructions posted at https://github.com/RIPE-NCC/whois/wiki/Installation-instructions . The instructions, however, don't include any details on 'priming' the whois database - using the SQL from the whois-commons/target/classes/<database>_schema.sql files, I get all my databases and tables created, but there is no data in the tables. I'm assuming that I need to have at least a 'mntner' in the WHOIS_LOCAL/mntner table, and I added a single entry manually with an object_id of 0, but I still can't seem to use any update method (synchupdates, REST, etc.) to add new information to the database. Would it be possible to get a push in the right direction for manually populating the WHOIS database with enough stuff (user IDs, passwords, etc.) to begin using the APIs to modify the database? Regards, Scott Cubic cubic(a)att.com<mailto:cubic@att.com>

2 1

Control over associating objects for number blocks
by William Sylvester 18 Nov '15

18 Nov '15

Dear Database Working Group Members, At the last RIPE meeting we discussed the topic of orphaned objects, and it seems that this term was confusing to some. This is an attempt to clarify the problem and hopefully find a solution forward. This continues to be a problem where number block holders are getting “locked” out of being able to manage their routing objects and in-addr records. Today, we continue to have a problem where a block holder does not have an ability to manage the objects that operationally impact their number blocks. Examples include a routing or reverse dns object that exist in the database but are not currently maintained by an active number block maintainer. This is typically the case where a number block holder (usually legacy) may have contracted services through a third party. Time goes by, the business relationship ends but the third party never removed their associated records (in-addrs, routing objects, etc). The number block holder now seeks to update the block (either directly or through a new service provider) and is unable to add these resource records to their number block. The database can help fix this problem through allowing the appropriate control for a number block holder to maintain their own information. In many cases the last resort is to contact RIPE NCC to make the change to an object the number block holder should have had online access to manage directly in the first place. This proposal intends to enable number block holders to have a greater ability to manage their own resources. I propose that the maintainer of a number block shall have full control over the association of contacts, routing, and reverse dns entries related to the number block held. The number block holder should not be able to delete an object they do not have maintainer status for, but they should be able to remove the association from their number block. The number block maintainer shall have an ability to delete the relationship between a related object and the number block through the LIR Portal, Webupdates, and related systems. Open items to discuss; 1) What is the best method to enable a number block holder to manage and control objects associated with their blocks in Ripe DB? 2) Should any objects be excluded from this control? 3) What is a reasonable schedule for announcements and implementation? Thank you for your consideration and I look forward to your comments. Billy William Sylvester william.sylvester(a)addrex.net<mailto:william.sylvester@addrex.net>

5 12

Solving the issue of rogue ROUTE objects in the RIPE Database
by denis 14 Nov '15

14 Nov '15

Hi All I raised an idea before the last RIPE Meeting but it did not generate a lot of interest at that time. I brought it up again yesterday on the Anti Abuse WG list and it seemed to get quite a bit of support. So I will bring it back to the DB WG as it is a DB issue. I have CC'ed both AA WG and Routing WG for information. But it may be useful to keep the discussion now on the DB WG list. I don't claim this will solve all the problems of the universe, but it does satisfy an immediate goal to have all ROUTE objects in the RIPE Database created with the knowledge and approval of the related resource holders. And I believe it could be implemented in a relatively short space of time giving immediate benefits. cheers denis STEP 1 Any ROUTE object submitted for creation in the RIPE Database involving an out of region resource (address space and/or ASN) where that out of region resource does not exist in the authoritative RIR database (has not been allocated or assigned), reject the creation. The RIPE NCC mirrors the operational data from all the other 4 RIRs. These mirrors are updated daily as well as the RIRs daily stats. It is easy to determine if a resource is registered in the authoritative database. STEP 2 For those ROUTE objects from STEP 1 where the out of region resource does exist, hold the object creation as pending. The mechanism for doing this already exists in the RIPE Database software as it is used for multiple authentications. Lookup the out of region resource(s) in the authoritative database(s) and find the contacts for that resource. Send a notification to those contacts informing them of the pending ROUTE object creation in the RIPE Database. The notification mechanism already exists in the RIPE Database software. If they don't approve, do nothing and the creation request will time out after a week and the object will not be created. If they do approve, respond in some way (many technical options for doing this that the RIPE NCC can choose from). If appropriate approval(s) are received within a week, create the ROUTE object. STEP 3 On a daily basis, for each ROUTE object in the RIPE Database that relates to an out of region resource, check for the continued existence of that resource in the appropriate RIR database. If it no longer exists, delete the ROUTE object from the RIPE Database. STEP 4 This is a one off cleanup of existing ROUTE objects. For all ROUTE objects currently in the RIPE Database that relate to an out of region, existing resource, send the appropriate notifications. For any that no response is received, delete the ROUTE object from the RIPE Database. We can be a bit more generous on the timing for this step and even send multiple reminder notifications to be sure. (Possible) STEP 5 If a delete request is sent to the RIPE Database for a ROUTE object related to out of region address space without the proper authorisation, send a notification to the contacts for the authoritative address space holder. If an appropriate response is received back, delete the ROUTE object. This would simulate the reclaim functionality for RIPE address space holders. AUT-NUM copies Another byproduct of implementing this is that we no longer need to hold copies of AUT-NUM objects in the RIPE Database. The out of region ASN auth requirement is satisfied by the appropriate response to the notification. So all 'foreign' AUT-NUM objects could be immediately deleted. (Or after allowing time for these ASN holders to make sure their routing policy is actually up to date in the authoritative AUT-NUM object.)

10 25