This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[db-wg] RIPE NCC to remove mnt-lower RIPE-NCC-END-MNT from ASSIGNED PI objects
- Previous message (by thread): [db-wg] RIPE NCC to remove mnt-lower RIPE-NCC-END-MNT from ASSIGNED PI objects
- Next message (by thread): [db-wg] Call for agenda items DB-WG meeting during RIPE70, Amsterdam, NL
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tim Bruijnzeels
tim at ripe.net
Fri Mar 6 17:07:43 CET 2015
Dear Aleksi, WG, > On 06 Mar 2015, at 04:17, Aleksi Suhonen <ripe-ml-2012 at ssd.axu.tm> wrote: > > Hello, > >> On 25 Feb 2015, at 13:27, Marco d'Itri <md at Linux.IT> 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 <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: </ripe/mail/archives/db-wg/attachments/20150306/e2011073/attachment.html>
- Previous message (by thread): [db-wg] RIPE NCC to remove mnt-lower RIPE-NCC-END-MNT from ASSIGNED PI objects
- Next message (by thread): [db-wg] Call for agenda items DB-WG meeting during RIPE70, Amsterdam, NL
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]