From nigel at titley.com Mon Mar 2 14:27:11 2015 From: nigel at titley.com (Nigel Titley) Date: Mon, 02 Mar 2015 22:27:11 +0900 Subject: [db-wg] Monthly open-items summary Message-ID: <54F4652F.3070808@titley.com> Folks, The WG chairs have decided that a monthly "open-items" list might be useful to the WG. I'm doing the first and it will then rotate around the other chairs on a monthly basis. - "source: field for non RIPE address space", this proposal needs to be reworked to accommodate the large transfer of route objects from RIPE to the new AFRINIC DB - "restrict usage of RIPE-NCC-RPSL-MNT" we need to continue this discussion and request action from RIPE NCC - proposal for latin1 primary keys, utf8 allowed in user modifiable data - cross routing registry authorisation. This is a long term project which will ultimately allow authorisation between registries and will allow de-duplication of data across the registry system as a whole. This will be progressed as a BOF at RIPE 70 meeting if possible. - continue promotion of the the new Afrinic RR If I've missed anything please let me know. Nigel From ripe-ml-2012 at ssd.axu.tm Fri Mar 6 04:17:18 2015 From: ripe-ml-2012 at ssd.axu.tm (Aleksi Suhonen) Date: Fri, 06 Mar 2015 05:17:18 +0200 Subject: [db-wg] RIPE NCC to remove mnt-lower RIPE-NCC-END-MNT from ASSIGNED PI objects In-Reply-To: <78516137-869B-495C-BD76-49852BBB738D@ripe.net> References: <20150225122752.GA5118@bongo.bofh.it> <78516137-869B-495C-BD76-49852BBB738D@ripe.net> Message-ID: <54F91C3E.5070702@ssd.axu.tm> Hello, > On 25 Feb 2015, at 13:27, Marco d'Itri wrote: >> Good idea. Is the up to date business logic of the database >> available somewhere? On 02/25/2015 06:21 PM, Tim Bruijnzeels wrote: > The business logic is how we typically implement RIPE policy > restrictions on the RIPE database. These restrictions are documented > in RIPE policy documents and implementation plans. I think what Marco d'Itri wanted, and what I want in any case, is to see the programme code or logic statements that implement the restrictions documented in RIPE policy documents etc. We as a community want to verify that our wishes are implemented correctly and transparently. Some may even want to point out inaccuracies or offer corrections or performance enhancements. As long as they are within the scope of agreed policy I don't see why this could be a problem. The RIPE DB software is sufficiently large that we'd like a pointer to where we should start looking for said code, instead of going through the whole thing ourselves. Yours sincerely, -- Aleksi Suhonen Let bogons be bogons. From tim at ripe.net Fri Mar 6 17:07:43 2015 From: tim at ripe.net (Tim Bruijnzeels) Date: Fri, 6 Mar 2015 17:07:43 +0100 Subject: [db-wg] RIPE NCC to remove mnt-lower RIPE-NCC-END-MNT from ASSIGNED PI objects In-Reply-To: <54F91C3E.5070702@ssd.axu.tm> References: <20150225122752.GA5118@bongo.bofh.it> <78516137-869B-495C-BD76-49852BBB738D@ripe.net> <54F91C3E.5070702@ssd.axu.tm> Message-ID: Dear Aleksi, WG, > On 06 Mar 2015, at 04:17, Aleksi Suhonen wrote: > > Hello, > >> On 25 Feb 2015, at 13:27, Marco d'Itri wrote: >>> Good idea. Is the up to date business logic of the database >>> available somewhere? > > On 02/25/2015 06:21 PM, Tim Bruijnzeels wrote: >> The business logic is how we typically implement RIPE policy >> restrictions on the RIPE database. These restrictions are documented >> in RIPE policy documents and implementation plans. > > I think what Marco d'Itri wanted, and what I want in any case, is to see the programme code or logic statements that implement the restrictions documented in RIPE policy documents etc. > > We as a community want to verify that our wishes are implemented correctly and transparently. Some may even want to point out inaccuracies or offer corrections or performance enhancements. As long as they are within the scope of agreed policy I don't see why this could be a problem. > > The RIPE DB software is sufficiently large that we'd like a pointer to where we should start looking for said code, instead of going through the whole thing ourselves. The code for all these additional validations applied to updates can be found here: https://github.com/RIPE-NCC/whois/tree/master/whois-update/src/main/java/net/ripe/db/whois/update/handler/validator However, implementation details may not always be obvious without knowing the larger code base, and not everyone can read Java code. For this reason we are also working on a text document listing the existing rules per object type, plus the reasoning and references behind each rule. Doing this properly takes some time, but we are fully committed to providing transparency on these rules to everyone in an easy to understand format. Kind regards, Tim Bruijnzeels > > Yours sincerely, > > -- > Aleksi Suhonen > Let bogons be bogons. -------------- next part -------------- An HTML attachment was scrubbed... URL: From job at ntt.net Mon Mar 23 14:22:06 2015 From: job at ntt.net (Job Snijders) Date: Mon, 23 Mar 2015 14:22:06 +0100 Subject: [db-wg] Call for agenda items DB-WG meeting during RIPE70, Amsterdam, NL Message-ID: <20150323132206.GE697@Hanna.local> Dear DB-WG participants, We are reaching out to you for agenda items for the Database Working Group session during the RIPE70 meeting in Amsterdam, Netherlands 11-15 May 2015. Some of the current topics are: - 'source:' differentiation - RIPE-NCC-RPSL-MNT - UTF-8 in the DB - cross-registry authorisation - updates from RIPE NCC - .... your topic? Please submit your items or topic suggestions to the chairs directly or to the list for public discussion. Soon we'll publish a draft agenda, waste no day if you want microphone time! :-) The Database Working Group session is scheduled Thursday 14 May, from 16:00 till 17:30. Looking forward to a successful session and see you soon in the beautiful city of Amsterdam! Kind regards, Job, Piotr & Nigel From training at ripe.net Mon Mar 30 11:58:04 2015 From: training at ripe.net (Training Services) Date: Mon, 30 Mar 2015 11:58:04 +0200 Subject: [db-wg] [training] RIPE NCC Webinars - new dates Message-ID: <55191E2C.3000406@ripe.net> 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 . We look forward to seeing you online. Kind regards, RIPE NCC Training Services From tim at ripe.net Tue Mar 31 17:54:27 2015 From: tim at ripe.net (Tim Bruijnzeels) Date: Tue, 31 Mar 2015 17:54:27 +0200 Subject: [db-wg] Database release 1.79 deployed to RC environment Message-ID: <8C05F990-FA8C-4C64-9C1F-C7475642CA6A@ripe.net> Dear colleagues, The RIPE NCC is pleased to announce the deployment of RIPE Database software release 1.79 to the Release Candidate (RC) environment: https://www.ripe.net/data-tools/db/release-notes/rc-release-candidate-environment This release introduces the new attributes "created:" and "last-modified:" as part of the first phase of the deprecating the changed attribute in the RIPE Database. You can find more information about the three phases of this effort here: https://labs.ripe.net/Members/tim/deprecating-the-changed-attribute-in-the-ripe-database It should be noted however that: = The new attributes will only be enabled in output this Thursday 2 April (because updating all objects with initial values takes a long time) = We have found that we needed to use the 1970-01-01T00:00:00Z instead of 0000-00-00T00:00:00Z (because it's invalid, and we observed inconsistencies in dealing with year 0 AD different libraries) We will update the referenced article shortly to reflect these changes. This release also changes attribute "referral-by" from mandatory to optional. This attribute is part of a mntner object for historical reasons and will be deprecated. Detailed release notes are published here: https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.79 Documentation for this release is published here: https://www.ripe.net/data-tools/support/documentation/ripe-database-documentation-1.79 Please let us know if you find any issues with this release. We plan to deploy this release to the production environment on Tuesday 28 April, and we plan to enable the new "created:" and "last-modified:" attributes the following Monday 4 May - after the initial values have been added for all objects. Please let us know if you have any questions or comments. Kind regards, Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC -------------- next part -------------- An HTML attachment was scrubbed... URL: