March 2014 - 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

Draft minutes of RIPE 67 meeting
by Nigel Titley 05 Nov '14

05 Nov '14

Please find draft minutes of the DB-WG meeting held in Athens today. Comments, complaint, misrepresentations etc, to me Nigel

1 1

Proposal to remove "referral-by" attribute in "mntner" object or make it optional
by Martin Tõnusoo 06 Oct '14

06 Oct '14

Hello, "referral-by" attribute(defined in RFC2725) is mandatory in "mntner" object: [martint@ ~/ripe-db]$ whois -BHrh whois.ripe.net -t mntner | grep referral-by referral-by: [mandatory] [single] [ ] [martint@ ~/ripe-db]$ I checked the db-wg mailing-list archive since January 2000 and only discussion I found regarding this attribute was from Engin Gunduz(former RIPE NCC Senior Software Engineer) in June 2004: [martint@ ~/ripe-db]$ for year in {2000..2014}; do for month in January February March April May June July August September October November December; do wget -q --no-check-certificate https://www.ripe.net/ripe/mail/archives/db-wg/$(printf '%s-%s.txt.gz\n' "$year" "$month"); done; done [martint@ ~/ripe-db]$ zgrep -Hi "referral-by" * 2000-August.txt.gz:-irb (or -ireferral-by) <maintainer name> 2000-August.txt.gz:Returns all objects whose referral-by attribute matches the query 2001-August.txt.gz:referral-by: RIPE-DBM-MNT 2001-May.txt.gz:If you mean referral-by, it points to mntner handle, mandatory in mntner 2003-April.txt.gz:referral-by: RIPE-DBM-MNT 2003-April.txt.gz:referral-by: RIPE-DBM-MNT 2003-August.txt.gz:> referral-by: RIPE-DBM-MNT 2003-December.txt.gz: referral-by: MAINT-RGNET 2003-December.txt.gz: referral-by: MAINT-RGNET 2003-December.txt.gz: referral-by: MAINT-RGNET 2003-December.txt.gz: referral-by: MAINT-RGNET 2003-December.txt.gz: referral-by: MAINT-RGNET 2003-December.txt.gz:> referral-by: MAINT-RGNET 2003-December.txt.gz:> referral-by: MAINT-RGNET 2003-December.txt.gz:> > referral-by: MAINT-RGNET 2003-December.txt.gz:> > referral-by: MAINT-RGNET 2003-July.txt.gz:referral-by: RIPE-DBM-MNT 2004-April.txt.gz:referral-by: RIPE-DBM-MNT 2004-June.txt.gz:referral-by: [mandatory] [single] [inverse key] 2004-June.txt.gz:referral-by: RIPE-DBM-MNT 2004-June.txt.gz:Subject: [db-wg] Proposed Change 2004.2: Removal of "referral-by:" Attribute 2004-June.txt.gz:[2004.2] Removal of "referral-by:" Attribute from the MNTNER Object 2004-June.txt.gz:Remove the "referral-by:" attribute from the MNTNER objects' schema. This 2004-June.txt.gz:The "referral-by:" attribute was introduced into MNTNER objects when the 2004-June.txt.gz:"referral-by:" is defined in RFC2725: 2004-June.txt.gz: referral-by This attribute is required in the maintainer object. It 2004-June.txt.gz: referral-by. An auth-override can only be added to a maintainer 2004-June.txt.gz: those identified by the maintainer in the referral-by have 2004-June.txt.gz: "referral-by" attribute is now mandatory in the "maintainer" object 2004-June.txt.gz: referenced by a "referral-by" attribute elsewhere. 2004-June.txt.gz:The RIPE NCC introduced the "referral-by:" attribute as a place-holder, 2004-May.txt.gz:referral-by: [mandatory] [single] [inverse key] 2005-May.txt.gz:> referral-by: [mandatory] [single] [inverse key] 2005-May.txt.gz:> > referral-by: [mandatory] [single] [inverse key] 2005-November.txt.gz:>referral-by: RIPE-DBM-MNT 2005-November.txt.gz:> >referral-by: RIPE-DBM-MNT 2005-November.txt.gz:> > >referral-by: RIPE-DBM-MNT 2007-July.txt.gz:> referral-by: RIPE-DBM-MNT 2007-July.txt.gz:>> referral-by: RIPE-DBM-MNT 2007-June.txt.gz: referral-by: RIPE-DBM-MNT 2007-June.txt.gz: referral-by: RIPE-DBM-MNT 2007-June.txt.gz:> referral-by: RIPE-DBM-MNT 2007-June.txt.gz:> referral-by: RIPE-DBM-MNT 2012-April.txt.gz:referral-by: DEV-ROOT-MNT 2013-March.txt.gz:referral-by: TRUBNIKOV-MNT 2013-March.txt.gz:> referral-by: TRUBNIKOV-MNT 2013-March.txt.gz:> referral-by: TRUBNIKOV-MNT 2013-March.txt.gz:>> referral-by: TRUBNIKOV-MNT 2013-March.txt.gz:>>> referral-by: TRUBNIKOV-MNT [martint@ ~/ripe-db]$ He also proposed to remove the "referral-by" attribute, but there was no feedback to his e-mail. One can read his e-mail here: https://www.ripe.net/ripe/mail/archives/db-wg/2004-June/002797.html In addition, while RIPE database manual says that "referral-by attribute may never be altered after the addition of the maintainer", one can easily change it at least in current RIPE database version. Is the "referral-by" attribute obsolete? Or is it needed in some specific situation? If not, I propose to remove the "referral-by" attribute in "mntner" object or at least make it optional. WBR, Martin Tonusoo -------------------------- LINXTELECOM www.linxtelecom.com -------------------------- NOC 24/7: +372 622 3300

13 25

Support for expansion of an origin into a list of prefixes
by Job Snijders 01 May '14

01 May '14

Dear RIPE DB-WG, Much like my previous request regarding server side expansion of objects, I'd very much like the RIPE Database team to implement two flags which IRRd currently supports: !g & !6 I've filed an enhancement request on github: https://github.com/RIPE-NCC/whois/issues/73 The !g and !6 flags signficantly reduce the amount of RPSL interpretation a client has to perform, as the server provides the clients with a straight answer (abeit simplified). If the DB team implements such a feature, I'd also very much like an implementation in context or RDAP so I can query for lists of prefixes through HTTP rather than WHOIS. Kind regards, Job

2 1

Proposal: DB object syntax change
by Piotr Strzyzewski 25 Apr '14

25 Apr '14

Dear working group I would like to propose syntax change of the role attribute of the ROLE object in the RIPE DB. Bellow you can find all details. I would like to hear your opinion about this idea and ask for the support to allow RIPE NCC to implement it. ------------- Short description: I would like to propose to change the syntax of the role attribute of the ROLE object from <person-name> to <organisation-name>, where both <person-name> and <organisation-name> are defined in RIPE Database Update Reference Manual. I would like to emphasize that I don't want to change the syntax of the nic-hdl attribute of the ROLE object. Nevertheless, my proposal influence the automatic mechanism of choosing the nic-hdl attribute value of the ROLE object, while it is created with AUTO directive. Rationale: Abuse-c implementation have influenced business procedures of LIRs and have led to increased importance of ROLE object. Since ROLE object is mandatory in the process of proper abuse-c registration, LIRs could be interested in automatic creation of it. Right now, due to its syntax, the role attribute of the ROLE object has number of limitations and cannot accept bunch of characters and or whole labels/words which are natural parts of company names. As an example, it is impossible to create ROLE objects with one of the following role attributes: - Company Father, Son & Daughter Abuse Team - 4U Network Abuse Team - 123 Ltd. Hostmaster - WOW! Network Dept. and so on. Moreover, the original intention was for the ROLE object to represent business roles and not personal data (see: paragraph 1.2.17 of the RIPE Database Update Reference Manual). Taking this into account the <organisation-name> would be the natural choice since it both perfectly solves the problem and is already well defined and implemented. Possible problems: As for now, the nic-hdl attribute of the ROLE object is auto-generated and based on the value of the role attribute. Since <person-name> do not allow all-numeric labels, this mechanism is quite simple. However, similar mechanism exists for the auto-generated organisation attribute of the ORGANISATION object, where <organisation-name> allows this kind of labels. While this is significant change to syntax, I would like to emphasize that <person-name> is a subset of <organisation-name>. This means that even if some people may rely on the current syntax, this change would most probably not influence their procedures. ----------- Best regards, Piotr -- gucio -> Piotr Strzyżewski E-mail: Piotr.Strzyzewski(a)polsl.pl

7 11

RIPE Database Release 1.72 - including SSO Integration
by Denis Walker 07 Apr '14

07 Apr '14

Dear colleagues, We are pleased to announce RIPE Database release 1.72. For more information about the features, changes and how this release might affect your operations, please see these release notes: https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.72 A major feature introduced in this release is the integration of RIPE Database services with RIPE NCC Access. This gives maintainers the option to use their RIPE NCC Access account for authorising updates to the RIPE Database. The first applications that utilise this feature are Webupdates and Syncupdates from a web form. Linking a RIPE NCC Access account to an organisation is a requirement for certifying PI address space. No change has been made to existing authorisation options. This release also fixes a number of issues, so please read the release notes. By fixing certain issues with the JSON output from the REST API, the structure of that output has changed slightly. This should not affect any users as it was broken in the first place. To ensure this is the case, please test your implementation in the Release Candidate environment. More information about the Release Candidate environment is described in this document: https://www.ripe.net/data-tools/db/release-notes/rc-release-candidate-envir… We look forward to hearing any questions or comments you might have. Regards, Denis Walker Business Analyst RIPE NCC Database Team

7 12

Status %s not allowed when more specific object has status %s
by Tim Garrison 27 Mar '14

27 Mar '14

Greetings, I was wondering if it would be possible for the "Status %s not allowed when more specific object has status %s" error to be expanded in such a way that it reports what that specific object is. As it stands, it is rather difficult to determine when there is any overlap, especially when the upper and lower bounds of my inetnum object don't return any results when searching by single IP. Thanks in advance for considering this! -- Tim Garrison Lead, Systems Development *SoftLayer, an IBM Company* 315 Capitol Street Suite 205, Houston, TX 77002 281.714.4213 direct | 713.540.4325 mobile | 281.714.4657 fax | tgarrison(a)softlayer.com

2 2

[training] RIPE NCC Webinars - new dates
by Training Services 25 Mar '14

25 Mar '14

Dear colleagues, We are pleased to announce the launch of new dates for our Webinars. The RIPE NCC Webinars are live and take only one hour. You can interact with our trainers without leaving your desk. We focus on the topics and issues most important for LIRs. Register now at https://www.ripe.net/lir-services/training/e-learning/webinars Participation is limited to 20 people, so don't hesitate if you want to take part! If you have questions, please email <training(a)ripe.net>. We look forward to seeing you online. Kind regards, RIPE NCC Training Services

1 0

Suggestion of change for inverse query of notify
by Fredrik Widell 19 Mar '14

19 Mar '14

Hello db-wg. I would like to change the behaviour of the whois-output for the following query whois -h whois.ripe.net -- "-r -T inetnum,route -i notify info(a)resilans.se" Via that question, I will see every object that has the notify info(a)resilans.se set, which right now is inetnum: 194.14.3.0 - 194.14.3.255 netname: RESILANS descr: Resilans AB remarks: VV org: ORG-ABUS1000-RIPE country: SE admin-c: RESI1-RIPE tech-c: RESI1-RIPE status: ASSIGNED PI mnt-by: RESILANS-MNT mnt-domains: RESILANS-MNT mnt-routes: RESILANS-MNT source: RIPE # Filtered However, my request is that the above query should give the exact same output as the below query whois -h whois.ripe.net -- "-r -T inetnum,route 194.14.3.0" which will also display the corresponding route-object, is there any real reason why this is not displayed with an inverse query? it looks like: inetnum: 194.14.3.0 - 194.14.3.255 netname: RESILANS descr: Resilans AB remarks: VV org: ORG-ABUS1000-RIPE country: SE admin-c: RESI1-RIPE tech-c: RESI1-RIPE status: ASSIGNED PI mnt-by: RESILANS-MNT mnt-domains: RESILANS-MNT mnt-routes: RESILANS-MNT source: RIPE # Filtered route: 194.14.3.0/24 descr: Resilans AB origin: AS12381 mnt-by: RESILANS-MNT source: RIPE # Filtered -- Best regards Fredrik Widell Resilans AB http://www.resilans.se/ mail: info(a)resilans.se , fredrik(a)resilans.se phone: +46 8 688 11 80

4 4

Prefix length for the "pingable" attribute
by Tore Anderson 16 Mar '14

16 Mar '14

Hi WG, The documentation unequivocally states the value of the "pingable" attribute in route[6] objects must include a prefix length: $ whois -h whois.ripe.net -- -v route [...] pingable Allows a network operator to advertise an IP address of a node that should be reachable from outside networks. This node can be used as a destination address for diagnostic tests. The IP address must be within the address range of the prefix containing this attribute. An address prefix is represented as an IPv4 address followed by the character slash "/" followed by an integer in the range from 0 to 32. The following are valid address prefixes: 128.9.128.5/32, 128.9.0.0/16, 0.0.0.0/0; and the following address prefixes are invalid: 0/0, 128.9/16 since 0 or 128.9 are not strings containing four integers. $ whois -h whois.ripe.net -- -v route6 [...] pingable Allows a network operator to advertise an IP address of a node that should be reachable from outside networks. This node can be used as a destination address for diagnostic tests. The IP address must be within the address range of the prefix containing this attribute. <ipv6-address>/<prefix> Therefore I added mine as /32 and /128. That ended up in me getting complaints that I broke some people's scripts, which were assuming that value of this attribute should be a "bare" IP address. (For example: http://ip.v6net.ru/archives/1764) Contradictory to what the documentation says, the e-mail robot happily accepted my update to remove the prefix length. So hopefully people's scripts are unbroken now. This sparked my curiosity, though: - What exactly is the purpose of the prefix length? - How should one interpret a value that has a prefix length other than /32 (in "route" objects) or /128 (in "route6" objects)? - Why does the documentation say it is mandatory when it clearly is not? - And finally, am I really the only LIR hostmaster in the RIPE that actually do RTFM? :-) $ curl -s ftp://ftp.ripe.net/ripe/dbase/split/ripe.db.route{,6}.gz | zgrep -c '^pingable:.*/' 0 Tore

4 4

[training] RIPE NCC Courses in Sofia, Bulgaria 16-17 April 2014
by Training Services 14 Mar '14

14 Mar '14

Dear Colleagues, The RIPE NCC Training Services Department invites you to register for our upcoming Training Courses in Sofia, Bulgaria: Course type: RIPE Database Training Course Date: Wednesday, 16 April 2014 Time: 09:00-17:30 Course type: IPv6 for LIRs Training Course Date: Thursday, 17 April 2014 Time: 09:00-17:30 How to register: ---------------- You can register up to two people from your LIR for each course by using the LIR Portal at: https://lirportal.ripe.net/training/courses Registration will close when maximum capacity is reached, so please register soon to ensure your attendance. The course is free of charge. We provide lunch and printed training materials. We do not cover any of your travel expenses or accommodation. We give all of our training courses in English. RIPE Database Training Course: ------------------------------ You should attend this training course if you are part of the staff of a Local Internet Registry (LIR) in the RIPE NCC Service Region. You can find more information about the course at: https://www.ripe.net/lir-services/training/courses/rdb IPv6 for LIRs Training Course: ------------------------------ You should attend this training course if you are part of the staff of a Local Internet Registry (LIR) in the RIPE NCC Service Region and if you: * Are thinking about deploying IPv6 in your organisation * Have been told you need to deploy IPv6 * Need to convince your manager that IPv6 needs to be deployed * Looked at an IPv6 address and thought it was too complicated to deploy in your network You can find more information about the course at: http://www.ripe.net/lir-services/training/courses/ipv6 If you have any questions, send an e-mail to <training(a)ripe.net>. Kind regards, RIPE NCC Training Services

1 0

Implementation plan for 2012-07, "RIPE NCC Services to Legacy Internet Resource Holders"
by Nikolas Pediaditis 12 Mar '14

12 Mar '14

Dear colleagues, The RIPE NCC has published the proposed implementation plan for ripe-605 "RIPE NCC Services to Legacy Internet Resource Holders" (accepted policy proposal 2012-07): The overall implementation: https://labs.ripe.net/Members/nikolas_pediaditis/policy-proposal-2012-07-ri… The implementation that specifically relates to the RIPE Database: https://labs.ripe.net/Members/xavier/policy-proposal-2012-07-db-proposed-im… We are sending this email to three working groups because the implementation is related to anyone holding AUT-NUM or legacy INETNUM objects in the RIPE Database but we ask that comments be made on the RIPE NCC Services Working Group mailing list only. We aim to begin implementation the week of 25 March. Please do not hesitate to contact us if you have any comments or questions. Kind regards, Nikolas Pediaditis IP Resource Analyst RIPE NCC

1 0

[training] RIPE NCC Webinars - new dates
by Training Services 11 Mar '14

11 Mar '14

Dear colleagues, We are pleased to announce the launch of new dates for our Webinars. The RIPE NCC Webinars are live and take only one hour. You can interact with our trainers without leaving your desk. We focus on the topics and issues most important for LIRs. Register now at https://www.ripe.net/lir-services/training/e-learning/webinars Participation is limited to 20 people, so don't hesitate if you want to take part! If you have questions, please email <training(a)ripe.net>. We look forward to seeing you online. Kind regards, RIPE NCC Training Services

1 0