Re: [db-wg] out of region routing in the RIPE Database

--- Begin Message --- > On 18 Jul 2017, at 17:03, Sander Steffann via db-wg wrote: > > > From: Sander Steffann > Subject: Re: [db-wg] out of region routing in the RIPE Database > Date: 18 July 2017 at 16:10:09 GMT+2 > To: George Michaelson

Re: [db-wg] NWI-7: abuse-c implementation plan

--- Begin Message --- Dear working group, We will come back with a more detailed implementation time line later this week. Informally speaking we expect that we can do the technical work to prepare the phase-1 whois release in the coming weeks. We will probably have to plan the clean-up after

Re: [db-wg] NWI-7: abuse-c implementation request

--- Begin Message --- Dear working group, We are working on an impact analysis for this NWI and we expect to have a response within two weeks. Kind regards, Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC > On 22 May 2017, at 20:56, William Sylvester via db-wg

Re: [db-wg] Whois release 1.89 deployed to the Release Candidate Environment

RIPE NCC Database Group > On 4 May 2017, at 14:55, Tim Bruijnzeels via db-wg <db-wg@ripe.net> wrote: > > > From: Tim Bruijnzeels <t...@ripe.net> > Subject: Whois release 1.89 deployed to the Release Candidate Environment > Date: 4 May 2017 at 14:55:51 GMT+2 >

[db-wg] Whois release 1.89 deployed to the Release Candidate Environment

--- Begin Message --- Dear working group, We just deployed release 1.89 to the Release Candidate (RC) environment. If no issues are raised we plan to deploy this version to production on 22 May 2017. This release contains a number of small improvements: - Include information on who changed an

Re: [db-wg] DB signatures

--- Begin Message --- Dear Aliaksei, working group, The split files, and all other content of the ftp site, are also available on https: https://ftp.ripe.net/ https://ftp.ripe.net/ripe/dbase/split/ They have been available here for quite a while but I realise that this was not widely

Re: [db-wg] Whois release 1.90 in Release Candidate environment, production release planned for 16 October

--- Begin Message --- Dear Working Group, Whois release 1.90 has now been deployed to production. Kind regards Tim Bruijnzeels Assistant Manager Software Engineering and Senior Technical Officer RIPE NCC > On 27 Sep 2017, at 10:28, Tim Bruijnzeels via db-wg <db-wg@ripe.net&

Re: [db-wg] RIPE Access Account: Cannot change registered e-mail address back to previously one

--- Begin Message --- Dear Christoffer, > On 12 Oct 2017, at 08:40, Christoffer Hansen wrote: > > Dear Tim > > I was not aware the RIPE NCC Access account system was a separate system > apart from the RIPE Database system. > > In retrospect supporting changing emails

Re: [db-wg] NWI-7: abuse-c implementation plan

--- Begin Message --- Dear working group, We have a proposed timeline for the implementation. Let me quote the proposal sent out on 28 June here, and comment in-line: > 1) Allow “abuse-c:” on INET(6)NUM and AUT-NUM objects > > We will deploy a new version of whois where the “abuse-c:”

Re: [db-wg] NWI-7: abuse-c implementation plan modification

nges they don't need to take action on of > data that is redundant. So if anyone has any strong objections please let us > know by the end of this week. Otherwise we can give Tim the go ahead to this > modification to the implementation plan. > > cheers > denis > co-chair DB-W

Re: [db-wg] Validation on "org-name:" syntax (double spaces and newlines)

Hi all, We propose to only allow single spaces, and disallow any other whitespace such as tabs and NULL-bytes Tim > On 22 Nov 2017, at 21:42, denis walker wrote: > > Hi Alex > > I presume 'whitespace' does include them, but to be sure Tim can confirm that. > >

Re: [db-wg] NWI-5 Out of region ROUTE(6)/AUT-NUM objects implementation request

Dear working group, We are tasked by the co-chairs on 19 October 2017 to come up with an implementation proposal for NWI-5. It was suggested that the proposal should follow the suggestions done in the problem definition phase and focus on: 1)Remove the "origin:" authorization requirement 2)

Re: [db-wg] NWI-5 Out of region ROUTE(6)/AUT-NUM objects implementation request

Hi Job, > On 5 Dec 2017, at 11:07, Job Snijders wrote: > > ps. I'd leave the 'clean up out-of-region AUT-NUMs' for a separate > discussion on how to handle that data. Combining datamodel changes and > governance of existing data in the same topic might distract. This can be a

Re: [db-wg] NWI-5 Out of region ROUTE(6)/AUT-NUM objects implementation request

cember 2017, 23:16 > Subject: Re: [db-wg] NWI-5 Out of region ROUTE(6)/AUT-NUM objects > implementation request > > Tim Bruijnzeels via db-wg wrote: > > Dear working group, > > > > We are tasked by the co-chairs on 19 October 2017 to come up with an > > implemen

Re: [db-wg] Validation on "org-name:" syntax (double spaces and newlines)

hat this is a real world issue. Tim > > > On Sun, Nov 12, 2017 at 07:35 Tim Bruijnzeels via db-wg <db-wg@ripe.net> > wrote: > Dear Working Group, > > Out of 114181 ORGANISATION objects, 112 objects use multiple consecutive > whitespace in the “org-name:” attrib

[db-wg] Clean up unreferenced maintainers (after 90 days)

Dear Working Group, In the light of data protection we already clean up unreferenced organisation, person and role objects, and also mntner-role and mntner-person pairs, 90 days after such objects become unreferenced. So-far unreferenced maintainers are not cleaned up. We have about 8k such

[db-wg] Validation on "org-name:" syntax (double spaces and newlines)

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

[db-wg] Proxy proposal large communities

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

Re: [db-wg] NRTM replication inefficiencies

> On 9 Nov 2017, at 17:57, Job Snijders wrote: > > On Thu, Nov 09, 2017 at 04:28:03PM +0100, Tim Bruijnzeels wrote: >>> On 7 Nov 2017, at 23:11, Job Snijders via db-wg wrote: >>> >>> I would also welcome an investigation into alternative approaches, (some

Re: [db-wg] NRTM replication inefficiencies

Hi Job, WG, > On 7 Nov 2017, at 23:11, Job Snijders via db-wg wrote: > > I would also welcome an investigation into alternative approaches, (some > not-via-WHOIS replication mechanisms), perhaps something over HTTPS can > be done? Either way, something more robust would be

Re: [db-wg] NWI-5 Out of region ROUTE(6)/AUT-NUM objects implementation request

Hi Job, all, > On 11 Jan 2018, at 02:27, Job Snijders wrote: > > On Thu, Jan 11, 2018 at 01:17:09AM +, denis walker wrote: >> Unless it has been modified recently there is the reclaim >> functionality that will allow the resource holder to delete the >> ROUTE(6) object

Re: [db-wg] Getting 'responsible organization' out of RDAP

Dear Brian, > On 20 Mar 2018, at 19:54, Brian Rak wrote: > > Is this happening in public somewhere I can follow? There is currently no public forum covering this topic, but this is a good suggestion. I am investigating how to accomplish this and will reply when I have an

Re: [db-wg] Getting 'responsible organization' out of RDAP

Dear all, There are known differences between the RIR implementations of RDAP. In some cases we will need to make extended RDAP specifications, e.g. a resource can have multiple countries in the RIPE region. The RIRs are working together to make an inventory of these differences, and based on

Re: [db-wg] NWIs update

Hi, auth-sso contains an identifier of an RIPE NCC Access SSO account. Actual details such as the email address and password are not stored in the RIPE DB. To me it would make sense to have a similar approach for API Tokens. Have some identifier that is kept on the MNTNER object, but store the

Re: [db-wg] NWIs update

Hi Cynthia > On 10 Apr 2019, at 14:14, Cynthia Revström wrote: > > Hi, > > On 2019-04-10 13:14, Tim Bruijnzeels via db-wg wrote: >> Hi, >> >> auth-sso contains an identifier of an RIPE NCC Access SSO account. Actual >> details such as the email address