- db-wg - mailman.ripe.net

Validation on "org-name:" syntax (double spaces and newlines)
by Tim Bruijnzeels 23 Nov '17

23 Nov '17

Dear Working Group, Out of 114181 ORGANISATION objects, 112 objects use multiple consecutive whitespace in the “org-name:” attribute and only 1 uses a multi-line value. While this is a tiny fraction these objects are a bit problematic to us when we verify that the “org-name:” matches the name of the organisation that we allocated or assigned resources to in our records. We also believe that this is highly confusing to users and tools parsing these objects. Therefore we like to clean these objects up and remove any multi-whitespace or multi-line occurrences. We can of course follow up with these organisation individually, but the reason that I bring it up here is that we also want to have stricter syntax rules in place to prevent this from happening again. We can do either of the following: 1) replace multi-whitespace or multi-line occurrences on input (warn, but just strip the additional space) 2) reject multi-whitespace or multi-line occurrences on input I am leaning towards option 2, but I would value your input. Kind regards, Tim Bruijnzeels Assistant Manager Software Engineering and Senior Technology Officer RIPE NCC

6 6

Proxy proposal large communities
by Tim Bruijnzeels 14 Nov '17

14 Nov '17

Dear Working Group, As discussed at RIPE 75 I want to forward a request by Job Snijders on GitHub: https://github.com/RIPE-NCC/whois/issues/410 Job is asking to add a “large_community" keyword to RPSL dictionary where applicable. And provides the following example: Suggestion: name the keyword large_community mp-export: afi ipv6.unicast to AS13105 announce AS-RCNET-V6 AND NOT large_community.contains(21414:0:570) export: to AS6777 action large_community .= { 6777:0:6777 }; announce AS-FORTHNET mp-import: afi ipv6.unicast from AS8631 msk-rs2.ripn.net action large_community={31376:0:2}; pref=100; accept AS-MSKROUTESERVER import: from AS35082 95.128.51.234 at 95.128.51.233 action pref=500; large_community.append(29527:0:35082,29527:0:60000,29527:0:61200,29527:0:61210); accept AS-VIBUS-LONDON filter-set: fltr-as21229-export descr: Filter for AS21229 exported prefixes filter: AS-TVNETWORK AND large_community(21229:0:1) From our end I do not see any issues implementing this on the server side, but I can’t speak to how this will be treated by scripts that may parse RPSL today. Please discuss. Kind regards, Tim Bruijnzeels Assistant Manager Software Engineering and Senior Technology Officer RIPE NCC

5 24

new NWI? - was: mntner object updates by mail
by Piotr Strzyzewski 27 Oct '17

27 Oct '17

Dear WG Members After a nice chat just a seconds after DB-WG session has ended it was brought to the attention of few of us that there was an email sent last December by Ulf Kieber (with some responses) about mntner object updates by mail. Dear Chairs, can we proceed with that and make it next NWI? Piotr -- Piotr Strzyżewski Silesian University of Technology, Computer Centre Gliwice, Poland

5 5

Co-Chair Resignation
by William Sylvester 20 Oct '17

20 Oct '17

All, Denis and I were notified this morning by David that he is resigning as a co-chair for the database working group. He also indicated that he had resigned from Larus and was no longer employed there. He had intended to notify the working group sooner; his delays were the result of his relocation from Hong Kong back to Europe. He will not be attending the RIPE meeting next week in Dubai. David is very apologetic for what has transpired and that it has taken focus from the working groups primary tasks. I know this has been a very charged situation for the working group, and I appreciate everyone maintaining the professionalism I greatly respect within our community. We wish David the best in his future endeavors and thank him for his contributions. As a working group, we consider this issue closed. If you have any questions or concerns please notify the chairs. As we are nearing the end of the year, Denis and I have agreed to kick off the chair selection process earlier this year. We will be sending details out on the chair selection process soon. Best regards, William & Denis, co-chairs

2 1

NWI-2 Displaying history for database objects where available
by den is 20 Oct '17

20 Oct '17

Colleagues The DB WG co-chairs would now like to address this issue. There was some discussion on the mailing list in May to July of 2016. In brief the issue is that the current history mechanism has an arbitrary design constraint that only the history of currently existing objects can be seen. This may also not be complete if the object has been deleted and re-created. The problem definition has not yet been finalised. Also there was some discussion about the reasons for wanting more historical information being made available for resource objects (and possibly some other object types). We would therefore like to ask anyone with concerns about historical data to please review what was said last year and express support or otherwise and perhaps add some reasoning as to why more data is needed. cheers denis co-chair DB WG

4 4

DMARC Settings Change on RIPE Database Working Group Mailing List
by Adam Castle 19 Oct '17

19 Oct '17

Hi RIPE Database Working Group, In March 2017, the RIPE NCC implemented a requested DMARC change to this list < https://www.ripe.net/ripe/mail/archives/db-wg/2017-March/005514.html > The change was to enable the DMARC 'Wrap Message' setting in Mailman so that DMARC-enabled users could receive emails from the list sent via other DMARC-enabled users. Unfortunately, this caused some users to see emails come through as attachments, as well as various other compatibility issues with some mail clients. After consultation with the RIPE Database Working Group Co-Chairs, we have changed the Mailman setting to 'Munge the From address'. If you experience any emails from this mailing list as attachments from this point onwards, then please let me know. Many thanks, Adam Castle Web Services Manager RIPE NCC

2 1

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?
by Rob Evans 19 Oct '17

19 Oct '17

Hi, > 1) Remove the "origin:" authorization requirement. RIPE is currently > the only RIR that requires this, the current implementation creates > data concurrency issues across Internet databases by requiring the > creation of duplicate autnums. > > 2) Flag "route:" objects for non-RIPE-managed space with "source: > RIPE-NONAUTH" to identify non-authoritative data. I support both of those. I’ll observe that there have been attempts to do (1) in the past that have floundered. > 3) Consider possible, simple options to allow non RIPE resource > holders to 'approve' (if not authorise) the creation of a foreign > ROUTE object. I wouldn’t want to lose the ability to make progress on (1) and (2) because we end up getting bogged down in the details of (3), which is what I fear will happen, so I’d put something like this on the back burner for now. Cheers, Rob

5 5

Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?
by Randy Bush 18 Oct '17

18 Oct '17

> 2) Flag "route:" objects for non-RIPE-managed space with "source: > RIPE-NONAUTH" to identify non-authoritative data. why not go the other, more positive, direction, and identify authorised data with RIPE-AUTH or whatever? no need to be pejorative. randy

4 6

Re: [db-wg] violation of DB T&C by DB-WG co-chair, is it acceptable?
by Nick Hilliard 18 Oct '17

18 Oct '17

Bill, a single issue has been addressed in your email, relating to the RIPE NCC's actions in dealing with a violation of the RIPE DB T&Cs. The core issue of the complaint, namely the actions of one of the WG co-chairs, remains completely unaddressed. Can you kindly inform the working group whether, and if so, when the Database WG chairs intend to address this? Nick William Sylvester via db-wg wrote: > This message is to follow up on thread created recently with regard to a > reported violation of the RIPE Database Terms and Conditions. Several > members have commented publically and a few privately on this matter and > we wanted to publically addresses these concerns. The working group > chairs after consulting with the RIPE NCC and the RIPE Chair have > identified two primary issues in question; > > > > 1. A violation of the terms and conditions has been reported to the > working group, this is out of scope for the working group. Concerns > over usage in regard to the terms and conditions should be reported > to the RIPE NCC directly and not on the Database working group > mailing list. RIPE NCC has the responsibility and the resources to > handle these violations appropriately. It is our understanding that > the RIPE NCC has a process they have followed, and have done so with > the complaint registered on the working group mailing list. It is > the RIPE NCC’s responsibility to investigate and take action as > appropriate. As the working group, with this item referred to RIPE > NCC, we consider this issue handled and closed. > > > > 2. Conduct of a co-chair for a working group. This is a much more > challenging issue, should a chair be held accountable for the > actions of an employer? What are examples of unacceptable behavior > for a chair and when misconduct is suspected, what action, if any, > should be taken? Currently in the RIPE community there are no > policies for the removal of a chair. In the history of the RIPE > community a working group chair has only been removed once. Chair > selection is conducted through the processes identified by each > working group. Lacking a defined process, it seems that the chair > selection process coming up is the primary way the working group > selects or changes the working group leadership. > > > > I have always found David to be a good person who cares deeply about the > RIPE community, as a working group chair he has always handled working > group business with the highest integrity. I urge the working group to > consider mistakes we have each made as individuals, by our employers, > and in life. As working group chairs, we serve the working group for the > benefit of the RIPE community, we embrace open discussion from all > working group members, and we strive to resolve issues transparently > through community feedback and rough consensus. We continue to seek > community guidance in all aspects of managing the working group and look > forward to facilitating the database work in our working group. > > > > Thanks, > > > > William on behalf of the > > Database Working Group Chairs >

1 0

Re: [db-wg] violation of DB T&C by DB-WG co-chair, is it acceptable?
by Randy Bush 18 Oct '17

18 Oct '17

this is a brilliant exercise to see how far the community will bend over in pseudo-politeness while it is being slimed and abused. randy

2 2