- db-wg - mailman.ripe.net

Fwd: RIPE68 DB-WG Draft Agenda (interim) V2
by Wilfried Woeber 11 May '14

11 May '14

Sorry for the finger-trouble :-( -ww144 -------- Original Message -------- Subject: RIPE68 DB-WG Draft Agenda (interim) V2 Date: Sun, 11 May 2014 12:34:23 +0200 From: Wilfried Woeber <Woeber(a)CC.UniVie.ac.at> Reply-To: Woeber(a)CC.UniVie.ac.at Organization: UniVie - ACOnet To: db-wg(a)CC.UniVie.ac.at CC: RIPE NCC Meeting Role <meeting(a)ripe.net>, RIPE WG Chairs <wg-chairs(a)ripe.net> This is an (interim) 2nd draft of an agenda for the DB-WG Meeting at RIPE68 in Warsaw, scheduled for Wednesday, May 14, 2014. Please expect anotehr update closer to the WG MEeting Wilfried. ________________________________________________________________________ A. Administrative Matters . Welcome . select scribe . finalise agenda . approval of minutes from previous WG meeting(s) . review of action list B. Data Base Operational Update (Denis Walker, Ed Shryane, RIPE NCC) C. New DB-Software functionality - in test, schduled for deployment (sponsoring LIR) D. Proposals for changes to schema - consensus on removing referral-by:? - discussion changed: vs. last-modified E. 2012-07 implementation F. Status update on IETF WEIRDS activities (Ed Shryane, RIPE NCC) G. Personalised Authorisation (Denis Walker, RIPE NCC) Y. Input from other Working Groups and/or Task Forces - review of abuse contact stuff (N.N. t.b.c.)) Z. AOB ________________________________________________________________________ 11.05.2014 10:30 UTC

1 0

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

RIPE Database Release 1.73
by Denis Walker 29 Apr '14

29 Apr '14

Dear colleagues, The RIPE NCC is pleased to announce the RIPE Database software release 1.73 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.73 Major features introduced in this release include the: -Addition of a "sponsoring-org:" attribute for End User resources -Addition of a "status:" attribute for all AUT-NUM objects -Change of "status:" values for all legacy (early registration) INETNUM objects to 'LEGACY' This release also fixes a number of issues. More details are available in the release notes. Where necessary, data in the RC Database has been changed to reflect the new/changed attributes. Please check your data and test your implementation in the RC environment. 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 Business Analyst RIPE NCC Database Team

1 0

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

RIPE68 DB-WG Draft Agenda V1
by Wilfried Woeber 23 Apr '14

23 Apr '14

Dear DB-WG folks, Chairpersons, "Meeting"! This is the 1st -rough- draft of an agenda for the DB-WG Meeting at RIPE68 in Warsaw, scheduled for Wednesday, May 14, 2014. For time slot allocations please refer to the most up-to-date meeting plan at https://ripe68.ripe.net/programme/meeting-plan/ The DB-WG Meeting is scheduled for *Wednesday*, starting at 14:00 local time[1], after lunch . The length of our timeslot is 90 Minutes. The overall (draft) RIPE 68 meeting outline is already available at https://ripe68.ripe.net/programme/meeting-plan/ Please feel free to propose additional topics to be discussed! I'd also suggest that you submit your points of view regarding the topics on the proposed agenda on the mailing list, preferably before the WG meeting's start :-) Best regards, hope to see you soon in Poland, Wilfried. [1] for remote participation, this 12:00 UTC ________________________________________________________________________ A. Administrative Matters . Welcome . select scribe . finalise agenda . approval of minutes from previous WG meeting(s) . review of action list B. Data Base Operational Update (N.N., RIPE NCC) C. New DB-Software functionality - in test, schduled for deployment (sponsoring LIR) D. Proposals for changes to schema - consensus on removing referral-by:? - discussion changed: vs. last-modified E. 2012-07 implementation F. Status update on IETF WEIRDS activities (N.N. t.b.c.) Y. Input from other Working Groups and/or Task Forces - review of abuse contact stuff (N.N. t.b.c.)) Z. AOB ________________________________________________________________________ 23.04.2014 13:20 UTC

1 0

Changes to Syntax of End User Resources in the RIPE Database
by Denis Walker 17 Apr '14

17 Apr '14

Dear colleagues, The RIPE NCC will soon be deploying to our Resource Candidate (RC) Test Environment some changes to all End User resources. These changes are being implemented to satisfy two recently approved policies - ripe-603, "Publication of Sponsoring LIR for Independent Resources" and ripe-605, "RIPE NCC Services to Legacy Internet Resource Holders". The changes include: -The addition of a "sponsoring-org:" attribute to all End User resources (INETNUM, INET6NUM, AUT-NUM) -The addition of a mandatory "status:" attribute to all AUT-NUM objects -A change of "status:" for all legacy INETNUM objects (including all more specifics) to 'LEGACY' The RC Test Environment will include a copy of the RIPE Database with dummified personal data. All of the status additions and changes will be fully implemented in this test database. The "sponsoring-org:" attributes will all be set to reference a dummy ORGANISATION object in this test database. We do not expect any immediate changes to be necessary for any scripts that you use to generate these objects. Our software is tolerant to these attributes being missing and will generate them where necessary. Provided your scripts are tolerant to unknown attributes, as is recommended in the RPSL RFCs, you should not experience any issues even if your scripts query any of these objects. A comprehensive list of anticipated frequently-asked questions (FAQs) will be published alongside this release. We expect this FAQ will answer most questions. A "remarks:" attribute added to the changed objects will reference this FAQ page. Regards, Denis Walker Business Analyst RIPE NCC Database Team

1 0

Call for agenda items, DB-WG Meeting during RIPE68, Warsaw, PL
by Wilfried Woeber 15 Apr '14

15 Apr '14

Dear DB-WG folks, planning activities for the next RIPE Meeting - RIPE68 in Warsaw, PL, May. 12 - May. 16, 2014, have already started a while ago - thus this _call for agenda items_ for the meeting of the Database Working-Group. 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 *Wednesday* (starting at 14: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://ripe68.ripe.net/programme/meeting-plan/ Looking forward to a successful meeting and see you soon in Poland! Wilfried.

1 0

[training] RIPE NCC Webinars - new dates
by Training Services 08 Apr '14

08 Apr '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 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