November 2016 - db-wg - mailman.ripe.net

<auto-dbm@ripe.net> is slow this afternoon.
by RIPE Database Administration 17 May '18

17 May '18

Dear Colleagues, Because of a very high level of use this afternoon, the response time of <auto-dbm(a)ripe.net> is longer than normal. I have made contact with those who are responsible and I expect the situation to improve as the machine works through the queue. Please be patient. Obviously we at the RIPE NCC Database Group are continuously working to make the performance of the database as good as possible. However, we cannot make improvements in zero time. We thank you for your co-operation up to now and we ask for your continued co-operation so that everyone receives the best possible service. If you have anymore questions, please contact <ripe-dbm(a)ripe.net>. Regards, Ambrose Magee ____________________________ RIPE Database Administration.

2 2

WG Chairs Selection
by ripedenis＠yahoo.co.uk 20 Dec '16

20 Dec '16

Hi All I would like to clarify one point about my candidacy. Whilst it is no secret that I would love to improve the database design and model, that is a personal view and I accept that it is not well supported within the community. There is a time and place for such proposals and this is not the time. The next group of chairs have a growing list of important issues on the table already and that should be the focus. cheersdenis

11 14

RIPE WHOIS down?
by Patrick Velder 29 Nov '16

29 Nov '16

Hi there I just tried to use the RIPE WHOIS but it looks like it's currently down: on terminal: > patrick@patrickhome:~$ whois 185.117.xx.0 > connect: Connection refused web whois: > Proxy Error > > The proxy server received an invalid response from an upstream server. > The proxy server could not handle the request GET /search/query.html. > > Reason: Error reading from remote server Anyone else? Regards Patrick

4 3

WG Chairs Selection
by Piotr Strzyzewski 25 Nov '16

25 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 this year. 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. As you may know, Job Snijders decided at the RIPE73, last week, to step down. Moreover, Nigel Titley declare that when a new chair is found, he would like to step down as well. This means, that the only reason Nigel is staying on, is not to leave the WG with only one chair. Taking this opportunity, I would like to express my interest in being co-chair for another term. All the best, Piotr -- gucio -> Piotr Strzyżewski E-mail: Piotr.Strzyzewski(a)polsl.pl

22 43

New wizard for setting up Reverse DNS
by Alex Band 24 Nov '16

24 Nov '16

Dear colleagues, I'm exited to announce that the Software Engineering and Global Information Infrastructure departments have collaborated to provide a wizard for setting up Reverse DNS. The wizard replaces the form for creating RIPE Database objects manually, so when creating a new DOMAIN object you will be taken to it automatically: https://apps.db.ripe.net/webupdates A one-minute demo of the Reverse DNS wizard is online: https://youtu.be/7JzapYkca-Y Requesting reverse delegation for your zones has always been notoriously error prone, causing more user errors and support tickets than the creation of any other RIPE Database object. In order to maximise ease of use and success rate, we implemented the following features: - We present the user with a clear set of guidelines for the configuration of their name servers before starting the wizard - Manually creating reverse zones is no longer necessary, as you can simply fill in a prefix and the wizard will do the rest - Creating DOMAIN objects one by one is no longer necessary, as you can create up to 128 DOMAIN objects in one go - We perform a basic check on the name server before the full set of tests is run, to maximise the chance of success Please keep in mind that this is the first iteration of this functionality. We will now start gathering feedback and will run analytics to see how it can be improved further. For example, the current name server pre-checks are very basic and we can expand them in the future if needed. We are using Zonemaster for these checks and are in the process of migrating the full set of tests to this service. We’d like to thank IIS and AFNIC for their support. In case you are interested in the background story on the Reverse DNS wizard and Zonemaster, there are some presentations from RIPE 73 online: https://ripe73.ripe.net/archives/video/1517/ https://ripe73.ripe.net/archives/video/1511/ Kind regards, Alex Band Product Manager RIPE NCC

1 0

[training] RIPE NCC Training Courses January-March 2017
by Training Services 23 Nov '16

23 Nov '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 Barcelona, London, Lebanon, Turin, Hamburg, Moscow, Riga, Turkey, Nicosia, Tashkent, Ljubljana, Oslo. 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 and RIPE Database Training Course - DNSSEC Training Course - Measurements Tools Training Course - Basic IPv6 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

Workinggroup Chair Job Description
by Hans Petter Holen 22 Nov '16

22 Nov '16

I see in the ongoing discussion in the chair selection process that there has been some questions regarding the role and commitments of the chair: The "Job Description" can be found in RIPE 542: "Working Group Chair Job Description and Procedures" https://www.ripe.net/publications/docs/ripe-542 As others have stated, it is not necessarily for the chair to be present at every single RIPE meeting. It is however always good to meet in person, at the WG meeting, the WG chairs lunch and informally with other chairs, RIPE NCC staff and myself. While I have enjoyed virtual life for close to 30 years - I do still see the value of meeting in person now and then. -- Sincerely, Hans Petter Holen, RIPE Chair

3 2

Puzzled by RIPE-NCC-LOCKED-MNT
by Ronald F. Guilmette 22 Nov '16

22 Nov '16

I am having a bit of trouble decyphering the explanation/description of RIPE-NCC-LOCKED-MNT given on the following page, and I hope someone will help me to understand. https://www.ripe.net/publications/news/announcements/deprecation-of-the-non… It appears from the above, that there was a transition/reorganization that took place back around 2004, and that RIPE-NCC-LOCKED-MNT was set as the maintainer on various objects that were present in the data base at that time (specifically objects which were not already adequately password protected) in order to protect some such objects from unauthorized modification. Is that description approximately accurate, I mean to a first approximation? (I understand that I'm probably glossing over a number of the fine points here, but I am doing so just because I doubt that any of those are even pertinent to my real question.) So anyway, my real question is this: If in fact RIPE-NCC-LOCKED-MNT was just something which was used as a sort-of "passing phase" stop-gap mechanism, i.e. as just a convenient expedient for securing things that would otherwise poorly secured, and if it was only applied in this way back in 2004, and for perhaps a year or two afterwards, then what would be the explanation for a *recently created* data base object (e.g. a route object) that has a created: date of, say, 2014, 2015, or 2016 and also a mnt-by value of RIPE-NCC-LOCKED-MNT? Regards, rfg

7 12

Creating a mntner
by Ronald F. Guilmette 21 Nov '16

21 Nov '16

Sorry. I know this is probably an faq and a dumb question, but can some kind soul tell me the exact procedure for creating a new RIPE mntner object? Does one already have to be a dues-paying member of RIPE NCC in order to do that? Where is the form that needs to be filled out and what if any supporting documentation must be provided? Birth certificate? Company incorporation documents?

2 2

More-specific abuse-c
by Sebastian Wiesinger 16 Nov '16

16 Nov '16

I'm currently struggling with abuse-c management for a big organisation which wants multiple abuse contacts for different parts of the organisation. The org is using a lot of PI resources, some of them legacy. Currently they all use the same org object which is inextricably linked to the same abuse-c mailbox. They have a new field of business which is mostly decoupled from the rest (own AS, own routers, PI space, etc.) but still uses the same org object. As cumbersome as having to create a new org object would be, I would've gone this road but as all of them are PI I can't change the org object! It is managed by the RIPE NCC. So the only solution right now would be to ask the RIPE NCC to change the org for all objects to a new one just to change the abuse-c for the resources. I would not be surprised if this turns out to be more complicated because of the end-user contract stuff but I'll need input from the NCC how they handle such cases. Also having multiple org objects that have the same data (company name, address, phone,...) just to have a different abuse-c is something that irks me to no end. Now I have to update X orgs when the phone number or address changes. Also: redundant data in the database! I tried to follow past discussions regarding this but it seems they all kind of fizzed out without any conclusion? I would propose to fix this and add an abuse-c to resource objects that would be "more specific" than the org abuse-c and overrides it. If there are other ideas please don't hesitate to state them but to me it seems like a low-cost solution to this mess. Best Regards Sebastian -- GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A 9D82 58A2 D94A 93A0 B9CE) 'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE SCYTHE. -- Terry Pratchett, The Fifth Elephant

11 25