- db-wg - mailman.ripe.net

RIPE Database Release 1.74
by Denis Walker 17 Jul '14

17 Jul '14

Dear colleagues, The RIPE NCC is pleased to announce the RIPE Database software release 1.74 to the Release Candidate (RC) environment. For information about features, changes and how this release might affect your operations, please see the release notes: https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.74… Major features introduced in this release include the: - Removal of generated "remarks:" from AUT-NUM objects - Change of syntax of the "role:" attribute - Prevention of the removal of "abuse-c:" when linked to a resource object This release also fixes a number of issues. More details are available in the release notes. More information about the RC environment is available online: https://www.ripe.net/data-tools/db/release-notes/rc-release-candidate-envir… We look forward to any questions or comments you might have. Regards, Denis Walker RIPE NCC

1 1

Revising the RIPE Database Documentation
by Denis Walker 15 Jul '14

15 Jul '14

Dear colleagues, The RIPE NCC is currently revising the RIPE Database documentation. We have outlined our planning and the goals for this project in a RIPE Labs article: https://labs.ripe.net/Members/fatemah_mafi/revising-the-ripe-database-docum… Please send any feedback or specific content requests to the Database Working Group Mailing List by Wednesday, 30 July 2014 so that we can incorporate your input into our planning. Regards, Denis Walker RIPE NCC

1 0

[training] RIPE NCC Webinars - new dates
by Training Services 24 Jun '14

24 Jun '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

RIPE Bulk WHOIS change anonymization
by Micha 17 Jun '14

17 Jun '14

Hi Ripe Team, I asked your DB Managers and they suggested to forward my question to you. I hope that I don't unnecessarily spam you, but I couldn't find this in your db-wg archive with a quick look. Question: Is it possible to keep the actual "date" of the "changed:" line unanonymized? By now it's always: changed: unread(a)ripe.net 20000101 I get that you want to protect personal data like the mail adresses in this field, but I can't see how this date could harm anyone. I would like to use this date field for research purpose and I am happy about your answers! Michael Oelke Institute of Information Systems Humboldt-University Berlin

3 2

RIPE Database Release 1.73.1 Available in the Release Candidate Environment
by Johan Åhlén 13 Jun '14

13 Jun '14

Dear colleagues, Based on feedback from users testing RIPE Database release 1.73 in the Release Candidate (RC) environment, the RIPE NCC Database Group have made some software improvements that we’ve decided to incorporate into the next deployment. We will not deploy version 1.73 to production. Instead, we will deploy the improved version, 1.73.1, to the RC environment today, 19 May, and to production on 27 May 2014. The main concern with RIPE Database release 1.73 was related to user-automated assignment generation in the RIPE Database for legacy address space. With release 1.73, if a legacy object was updated with an incorrect "status:" attribute value, then the update would fail. With version 1.73.1, the database software will accept the update, regardless of any value supplied by the user, but will show a warning if the “status:” attribute value is incorrect. For more information about this release and how it might affect your operations, please see the release notes: https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.73… We look forward to any questions or comments you might have. Kind regards, Johan Åhlén Assistant Manager Database RIPE NCC

5 6

Blocking Access to Personal Data Objects in the RIPE Database
by Denis Walker 28 May '14

28 May '14

Dear colleagues, At RIPE 68, we again raised the issue of how the blocking mechanism works in the RIPE Database. Currently it is all or nothing — if a user queries for too much personal data, we block their access to everything. We often find that this causes issues for legitimate users of the database. This is a recent example of the requests our Customer Services department receives: "This is the outgoing NAT IP for a vast shared hosting cluster. We can't control the type of queries our customers run, there are over 250,000 websites, a tiny fraction might use RIPE but those customers are using RIPE database for a good reason and need to be able to query it. This is why I'm asking for a blanket allow.” Clearly we cannot whitelist any IP address for unlimited access to personal data. However, the option to only block access to personal data objects when the limit is reached would be a great help in these situations. No decision has been made on this issue. We are hoping that it can be further discussed by the community to see if a consensus can be reached. Regards Denis Walker Business Analyst RIPE NCC Database Team

8 7

"AND NOT" in as-expression
by Aris Lambrianidis 27 May '14

27 May '14

Good morning all, After tinkering around with import-via/export-via attributes, I realised that "AND NOT" is not supported in the as-expression part of peering specifications, although it is described in RFC2622 (along with the semantically equivalent EXCEPT) and included in example (6) of page 25. e.g. currently: import: from AS-AMS-IX-PEERS and not AS6777 accept ANY is not supported, while import: from AS-AMS-IX-PEERS except AS6777 accept ANY is. I have raised a ticket with RIPE NCC about it. Also, Job Snijders was kind enough to act quickly and provide patches for both irrtoolset and whois: https://github.com/RIPE-NCC/whois/pull/237 http://irrtoolset.isc.org/ticket/48 Kind regards, Aris Lambrianidis AMS-IX

2 4

Getting: HTTP/1.1 401 UNAUTHORIZED
by Ye, Hong 22 May '14

22 May '14

Hi Gurus, I am new to RIPE API and hope someone can help me get through this. Could some please let me know what is the proper way to use “curl” to get data back from following URL? I could use the same login name/password get in web portal but not from command line. Do I have to encode my logins? Or should I pass my logins as part of the URL parameters? Regards Hong Ye https://atlas.ripe.net/api/v1/measurement/xxxxxxxxxxx/result/?start=1392336… * Adding handle: conn: 0x7f9a74000000 * Adding handle: send: 0 * Adding handle: recv: 0 * Curl_addHandleToPipeline: length: 1 * - Conn 0 (0x7f9a74000000) send_pipe: 1, recv_pipe: 0 * About to connect() to atlas.ripe.net port 443 (#0) * Trying 2001:67c:2e8:22::c100:69e... * Connected to atlas.ripe.net (2001:67c:2e8:22::c100:69e) port 443 (#0) * TLS 1.2 connection using TLS_RSA_WITH_AES_256_CBC_SHA256 * Server certificate: *.ripe.net * Server certificate: DigiCert High Assurance CA-3 * Server certificate: DigiCert High Assurance EV Root CA * Server certificate: Baltimore CyberTrust Root > GET /api/v1/measurement/xxxxxxxxxxx/result/?start=1392336000&stop=1392249599&format=json HTTP/1.1 > User-Agent: curl/7.30.0 > Host: atlas.ripe.net > Accept: */* > < HTTP/1.1 401 UNAUTHORIZED < Date: Wed, 21 May 2014 20:14:54 GMT * Server Apache is not blacklisted < Server: Apache < Vary: Cookie < Set-Cookie: atlasessp=3933053c2caeb8d03a3179fa216e0882; Domain=atlas.ripe.net; expires=Wed, 04-Jun-2014 20:14:54 GMT; httponly; Max-Age=1209600; Path=/ < Content-Length: 0 < Connection: close < Content-Type: text/html; charset=utf-8 < * Closing connection 0

2 1

[training] RIPE NCC Webinars - new dates
by Training Services 19 May '14

19 May '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

Options for extending "abuse-c:"
by Denis Walker 15 May '14

15 May '14

Dear colleagues, At RIPE 67 in Athens, the RIPE NCC agreed to take another look at the implementation of RIPE Document ripe-563, "Abuse Contact Management in the RIPE Database." Two issues have been identified that are seen to be difficult to handle with the current model - partitioned subnets within one organisation and adding abuse contacts to more specifics for End Users. The RIPE NCC has considered these two issues and found what we believe to be practical solutions, available within the current model. More information about these solutions and the implementation of "abuse-c:" is available on RIPE Labs: https://labs.ripe.net/Members/denis/suggestions-for-improving-abuse-handling This topic will also be raised during the Anti-Abuse Working Group session at RIPE 68 in Warsaw. Regards, Denis Walker Business Analyst RIPE NCC Database Team

5 17