- db-wg - mailman.ripe.net

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

Revised RIPE Database Documentation on ripe.net
by Denis Walker 03 Nov '14

03 Nov '14

Dear colleagues, The RIPE NCC has expanded the revised RIPE Database documentation to include the information from the RIPE Database Query Reference Manual. The RIPE Database Query Reference Manual itself will be removed over the coming weeks. This revised documentation is available for version 1.76 of the RIPE Database software: https://www.ripe.net/data-tools/support/documentation/ripe-database-documen… We look forward to your feedback. Regards, Denis Walker RIPE NCC

1 0

WG chair selection procedure
by Nigel Titley 28 Oct '14

28 Oct '14

Folks We need to have a documented procedure in place by the end of the next WG meeting for the affirmation and re-affirmation of WG chairs. I strongly feel that voting has no place in the running of RIPE working groups and also feel that inability to attend a RIPE meeting should not be a barrier to either becoming a chair or participating in the selection process. So I propose the following procedure. 1. A call for interested parties is made on the WG mailing list at yearly intervals 2. Interested parties have 2 weeks to make their interest known, again on the mailing list 3. The DB-WG chairs issue a call for discussion as per normal. WG members express their approval or otherwise of the presented candidates. 4. After two weeks the chairs declare consensus as they would do for a policy proposal I would propose a maximum number of 3 co-chairs. If at the end of the discussion phase there are more than 3 proposed co-chairs then a call is made for any of the candidates to withdraw. If there are still more than 3 candidates then names are 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. Comments are welcome. Best regards Nigel

5 5

Call for agenda items, DB-WG Meeting during RIPE69, London, UK
by Wilfried Wöber 15 Oct '14

15 Oct '14

Dear DB-WG folks, this is a _call for agenda items for the meeting of the DataBase-WG during RIPE69 in London, UK, November 3 - 7, 2014 Please submit (to the WG list!) your item requests and|or suggest topics for discussion to be included in the draft agenda! Please note that the DataBase-WG meeting is *at the moment* scheduled for *Thursday*, Nov. 6 (starting at 16:00 local time). This is according to the *draft* meeting plan - which is pretty stable already, but may still need to be changed as we get closer to the meeting date! The overall (draft) RIPE 68 meeting outline is already available at https://ripe69.ripe.net/programme/meeting-plan/ Looking forward to a successful meeting and see you soon in London! Wilfried.

1 0

Revised RIPE Database Documentation on www.ripe.net
by Denis Walker 07 Oct '14

07 Oct '14

Dear colleagues, Earlier this year, the RIPE NCC announced our intentions to revise the RIPE Database documentation, as requested by the community at RIPE Meetings: https://labs.ripe.net/Members/fatemah_mafi/revising-the-ripe-database-docum… The first batch of new documentation pages are available online: https://www.ripe.net/data-tools/support/ripe-database-documentation These pages replace the contents of the RIPE Database Update Reference Manual, which has now been removed fromwww.ripe.net, and include the contents of several other database-related webpages. We will publish further documentation pages, replacing the RIPE Database Query Reference Manual, before RIPE 69 in London, 3-7 November 2014. Features of this new documentation include: - A glossary of commonly-used terms shown throughout the documentation marked by dots (...) underneath. Mousing over these words will show the corresponding glossary entry. Alternatively, you can browse the glossary for a list of words and phrases and their definitions. - An export feature so that you can export the entire contents of the documentation to a .pdf for printing. We invite feedback from the community about the new documentation, which will be revised with each release of the RIPE Database software. Please reply toripe-dbm(a)ripe.net or provide your feedback on the RIPE Database Working Group mailing list. Regards, Denis Walker RIPE NCC

1 0

Revers DNS
by Colin Pyne 07 Oct '14

07 Oct '14

Hello, Please can anyone offer any advice as to what I am doing wrong in the setup of my revers DNS zone? I am getting two error messages when I submit the domain via webupdates. * No name servers found at child. No name servers could be found at the child. This usually means that the child is not configured to answer queries about the zone. * Fatal error in delegation for zone 38.57.185.in-addr.arpa. No name servers found at child or at parent. No further testing can be performed. Object data domain 38.57.185.in-addr.arpa descr Reverse DNS for LCH admin-c CP9084-RIPE tech-c CP9084-RIPE zone-c CP9084-RIPE nserver lchns1.unlimitednameservers.com nserver lchns2.unlimitednameservers.com mnt-by MOTIVE-MNT changed colin.pyne(a)motive.co.uk 20141007 source RIPE I have looked at this https://www.ripe.net/data-tools/dns/reverse-dns/how-to-set-up-reverse-deleg… I can perform a zone lookup 38.57.185.in-addr.arpa using NSLOOKUP > server 185.57.38.1 Default Server: host-185-57-38-1.lowcosthosting.co.uk Address: 185.57.38.1 > set type=ns > 38.57.185.in-addr.arpa Server: host-185-57-38-1.lowcosthosting.co.uk Address: 185.57.38.1 38.57.185.in-addr.arpa nameserver = lchns2.unlimitednameservers.com 38.57.185.in-addr.arpa nameserver = lchns1.unlimitednameservers.com lchns1.unlimitednameservers.com internet address = 185.57.38.1 lchns2.unlimitednameservers.com internet address = 185.57.38.2 Any advice would be very appreciated. Regards, Colin Pyne Colin Pyne | IT Manager T: 01539 797464 E: Colin.Pyne(a)motive.co.uk Visit our website: www.motivetechnology.com<http://www.motivetechnology.com/> Credentials & Partnerships [http://www.motivetechnology.com/MotiveTechnology/media/Motive/email/sponsor…] Lets Connect [http://www.motivetechnology.com/MotiveTechnology/media/Motive/email/motiveB…] <http://www.motivetechnology.com/Blog> [http://www.motivetechnology.com/MotiveTechnology/media/Motive/email/motiveF…] <https://www.facebook.com/motivetechnologyUK> [http://www.motivetechnology.com/MotiveTechnology/media/Motive/email/motiveT…] <https://twitter.com/Team_Motive_UK> [http://www.motivetechnology.com/MotiveTechnology/media/Motive/email/motiveL…] <https://www.linkedin.com/company/motive-technology-uk-limited> The content of this message and attached file are confidential and / or privileged and are for the intended recipient only. If you are not the intended recipient, any unauthorised review, use, re-transmission, dissemination, copying, disclosure or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you receive this message in error please contact the sender immediately and then delete this email from your system. Copyright in this email and attachments created by us belongs to Motive Technology UK Limited . Any attachment with this message should be checked for viruses before it is opened. Motive Technology UK Limited cannot be held responsible for any failure by the recipient to test for viruses before opening any attachments. Should you communicate with anyone at Motive Technology UK Limited by email you consent to us monitoring and reading any such correspondence. Motive Technology UK Limited - Company No: 06813205 - Registration Number: 947 4034 15 Registered Office: Richard House, Winckley Square, Preston, Lancashire, PR1 3HP

2 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

last-modified:, a succesor to changed:
by Job Snijders 16 Sep '14

16 Sep '14

Dear DB Working Group, Assessing the "freshness" of database objects can be a useful component in many business processes, but as it stands today the "changed:" attribute is severely crippled: Eleanor:~ job$ whois -h whois.ripe.net AS15562 | grep changed Eleanor:~ job$ whois -h whois.radb.net AS15562 | grep changed changed: unread(a)ripe.net 20000101 Eleanor:~ job$ Fantastic! Now we are absolutely none the wiser. :-) I propose that we introduce a new attribute called "last-modified" as a replacement for functionality offered by past implementations of "changed:". The "last-modified" attribute is set by the whois server software and represents the date and time at which the last succesful modification was received by the server. When a user submits an update for an object in which the attribute is present, the server software will ignore the attribute, insert its own attribute with the current time, and present a warning to the user that the user's version of "last-modified" was ignored. The "last-modified" attribute should be presented by the server software in all types of objects (autnums, poems, etc) for which the server is responsible (e.g. do not touch foreign or mirrored objects). The date and time are represented following the ISO 8601 [1] profile for complete date plus hours, minutes and seconds, always expressed in UTC, including the special UTC designator 'Z'. The "last-modified" attribute should be presented above, but close to the "source:" attribute. The advantage is that the date and time are both human readable and computer parsable! A valid example "last-modified" attribute would be: last-modified: 2014-04-15T13:15:30Z I look forward to the group's feedback! Also, I'm interested in how people would use this attribute in their workflows or automation. Kind regards, Job [1] - https://xkcd.com/1179/

15 43

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

11 Sep '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

Request for large number of request
by Giovane C. M. Moura 04 Sep '14

04 Sep '14

Dear Sir/Madam, I found on [1] that users can request permissions to have a large number of requests on the whois service. I would like to request permission for that -- we're talking about 500K requests max. I can provide more details and why this is important to be used in our research. Thanks and best, /giovane [1] https://www.ripe.net/ripe/mail/archives/db-wg/2005-June/003069.html -- Giovane C. M. Moura, PhD Postdoctoral Researcher Economics of Cybersecurity Group Faculty of Technology, Policy, and Management Delft University of Technology http://homepage.tudelft.nl/6a4w6/

1 0