Re: [db-wg] NRTM replication inefficiencies

Hi Job, > On 8 Dec 2017, at 13:51, Job Snijders wrote: > > On Fri, Dec 08, 2017 at 12:56:11PM +0100, Edward Shryane wrote: >> We could also add an 'end-of-stream' comment in keep-alive mode, >> something like '%END (starting serial) - (ending serial)', which is >> output

Re: [db-wg] NRTM replication inefficiencies

Hi Agoston, > On 8 Dec 2017, at 15:05, Edward Shryane via db-wg <db-wg@ripe.net> wrote: > > Hi Agoston, > >> On 8 Dec 2017, at 13:43, Horváth Ágoston János via db-wg <db-wg@ripe.net> >> wrote: >> >> Or you could use TCP's built-in keepalive fea

Re: [db-wg] NRTM replication inefficiencies

Hi Job, WG, > On 10 Nov 2017, at 15:31, Tim Bruijnzeels via db-wg wrote: > > We can look into this next week. > > Kind regards > > Tim there is an existing NRTM 'end-of-stream' indicator, if keep-alive is not used: a comment '%END RIPE' is output after the last object. We

Re: [db-wg] NRTM replication inefficiencies

Hi Agoston, > On 8 Dec 2017, at 13:43, Horváth Ágoston János via db-wg > wrote: > > Or you could use TCP's built-in keepalive feature: > > http://tldp.org/HOWTO/TCP-Keepalive-HOWTO/overview.html > Yes, this is already possible, you can set the SO_KEEPALIVE option on the

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

Dear Working Group, thank you for your feedback, we have now started to also delete unreferenced maintainer (mntner) objects. Regards Ed Shryane RIPE NCC > On 12 Nov 2017, at 07:12, Tim Bruijnzeels via db-wg wrote: > > Dear Working Group, > > In the light of data

Re: [db-wg] NRTM replication inefficiencies

Dear Job, Working Group, > On 7 Nov 2017, at 23:11, Job Snijders via db-wg wrote: > > Dear all, > > There may be some improvement opportunity for NRTMv3. > > The problem with the RIPE NRTMv2/NRTMv3 format is that it has no > 'end-of-stream' indicator, thus making the only way

Re: [db-wg] NRTM replication inefficiencies

Hi Job, > On 21 Feb 2018, at 16:38, Job Snijders wrote: > > On Wed, Feb 21, 2018 at 04:32:07PM +0100, Edward Shryane wrote: >> as part of the Whois 1.91 release, we've added an NRTM "end of stream" >> comment, and deployed to the Release Candidate environment. >> >> Try

Re: [db-wg] Implementation plan and dates for NWI5 - Out-of-region ROUTE(6) objects and removal of ASN authorisation for ROUTE(6) object creation.

Dear Colleagues, thank you all for your feedback. We will implement the following for NWI-5, and also deploy to production on 4th September: - Separate NRTM streams by source. Updates to out of region objects (route, route6, aut-num) will appear on the RIPE-NONAUTH stream only. In order to

Re: [db-wg] Implementation plan and dates for NWI5 - Out-of-region ROUTE(6) objects and removal of ASN authorisation for ROUTE(6) object creation.

Dear Job, DB-WG, we plan to return objects from both the RIPE and RIPE-NONAUTH sources for NRTM, as it will be less disruptive when NWI-5 goes into production. - If clients do nothing, they still receive all updates. - If we do not return all updates by default, then out of region object

Re: [db-wg] Whois release 1.91 in Release Candidate environment, production release planned for 7th March

has been deployed on RC for testing. Regards Ed Shryane RIPE NCC > On 21 Feb 2018, at 16:14, Edward Shryane via db-wg <db-wg@ripe.net> wrote: > > Dear Working Group, > > RIPE Database release 1.91 has been deployed to the Release Candidate > environment. If no i

Re: [db-wg] Whois release 1.91 in Release Candidate environment, production release planned for 7th March

Dear Working Group, we have now deployed Whois release 1.91.1 to production. Regards Ed Shryane RIPE NCC > On 9 Mar 2018, at 09:19, Edward Shryane via db-wg <db-wg@ripe.net> wrote: > > Dear Working Group, > > we have delayed the Whois production release until nex

Re: [db-wg] Whois Update Server Migration

l what will > happen if anyone submits an update during this downtime, or for any automated > scripts that send in updates? > > cheers > denis > co-chair DB WG > > > From: Edward Shryane via db-wg <db-wg@ripe.net> > To: Database WG <db-wg@ripe.net>

Re: [db-wg] Whois Update Server Migration

Dear Working Group, the Whois Update server migration is complete, there was a short downtime for updates (<5 minutes), and no interruption for queries. Regards Ed Shryane / Gabriel Ajabahian RIPE NCC > On 19 Mar 2018, at 17:19, Edward Shryane via db-wg <db-wg@ripe.net> wrot

[db-wg] Whois Update Server Migration

Dear Working Group, on Wednesday 21st March, we plan to migrate the Whois Update Server to a new configuration. This will cause a short downtime for Whois updates. Queries will not be affected. We will also create a Service Announcement on the RIPE NCC website. Regards, Ed Shryane RIPE NCC

Re: [db-wg] remove bogon prefixes in the RIPE IRR NON-AUTH DB?

Hi Job, Colleagues, > On 4 Sep 2018, at 12:46, Job Snijders via db-wg wrote: > > Dear WG, > > I'd like to raise the issue of bogon prefixes in the RIPE IRR, and ask > RIPE NCC to remove all "bogon" route object registrations from the > "RIPE-NONAUTH" IRR database. > > Today I was made aware

Re: [db-wg] remove bogon prefixes in the RIPE IRR NON-AUTH DB?

Hi Denis, > On 8 Oct 2018, at 19:51, denis walker wrote: > > HI Ed > > Are there any ROUTE(6) objects with source: RIPE for bogon prefixes or is > this one that Job mentioned with source RIPE-NONAUTH the only one in the > database (with either source)? > > cheers > denis > co-chair DB-WG >

Re: [db-wg] Proposal for restricting authentication concerning use of revoked and expired GPG ID's in key-cert objects

Hi Christoffer, DB WG, > On 1 Nov 2018, at 15:35, Christoffer Hansen (Lists) via db-wg > wrote: > > Dear DB WG, > > It came to my attention the RIPE NCC Database does not do validation of > signed updates. (Other than checking the key is allowed to sign updates > for object(s) in question) >

Re: [db-wg] remove bogon prefixes in the RIPE IRR NON-AUTH DB?

Hi Denis, sorry I wasn't clear, we will contact the user directly to ensure this object is removed. Regards Ed Shryane RIPE NCC > On 8 Oct 2018, at 23:20, denis walker wrote: > > Thanks Ed. Perhaps a way forward then would be if you can ask Customer > Services to contact the maintainers of

Re: [db-wg] improve --list-sources query to display latest serial?

Hi Job, this is due to a difference between the Whois Query service (port 43) and NRTM (port ). > On 28 Aug 2018, at 00:33, Job Snijders via db-wg wrote: > > Hi all, > > It appears there currently is no easy way to retrieve the current serial > from the RIPE DB. We're implementing some

[db-wg] Whois release 1.92.6 deployed to Production

Dear Working Group, we have deployed a bug-fix release 1.92.6 to production that fixes a bug when updating an object with a lowercase source value (e.g. "source: ripe"). The release notes have been updated: https://www.ripe.net/manage-ips-and-asns/db/release-notes/ripe-database-release-1.92

Re: [db-wg] Whois Release 1.93

/blob/master/changes.txt We now plan to deploy this release to production next Monday, 4th March. Regards Ed Shryane RIPE NCC > On 11 Feb 2019, at 15:34, Edward Shryane via db-wg wrote: > > Dear Working Group, > > RIPE Database release 1.93 has been deployed to the Re

[db-wg] Whois Release 1.92.6.2

Dear Working Group, RIPE Database release 1.92.6.2 was deployed to production yesterday evening, with a single change from the previous 1.92.6 release. Following the Database downtime on 22 February, this change restores the Full Text Search functionality. More information on the downtime can

Re: [db-wg] Whois Release 1.93

Dear Working Group, we have now deployed Whois 1.93.2 to production. Regards Ed Shryane RIPE NCC > On 1 Mar 2019, at 12:51, Edward Shryane via db-wg wrote: > > Dear Working Group, > > the RIPE Database release 1.93 was delayed due to the Full Text Search > downtime

Re: [db-wg] NWI-8 LIR´s SSO Authentication Groups

Hi Tore, the DB team will get started on an implementation proposal for the DB-WG. Regards Ed > On 18 Feb 2019, at 10:05, Tore Anderson via db-wg wrote: > > * denis walker via db-wg > >> We had a long discussion on this in January. I don't see any objections to >> this NWI so I would like

Re: [db-wg] Proposal for restricting authentication concerning use of revoked and expired GPG ID's in key-cert objects

Hi Denis, > On 11 Feb 2019, at 16:53, denis walker wrote: > > Hi Ed > > Thanks for following up on this. Just one question, have you taken into > account time zones? If an update is signed now in Dubai it is 19:51. If the > update is processed on Amsterdam time, it is 16:51. Will this update

Re: [db-wg] Proposal for restricting authentication concerning use of revoked and expired GPG ID's in key-cert objects

> >> On Feb 11, 2019, at 11:41 AM, Edward Shryane via db-wg >> wrote: >> >> Hi Denis, >> >>> On 11 Feb 2019, at 16:53, denis walker wrote: >>> >>> Hi Ed >>> >>> Thanks for following up on this. Just one question

[db-wg] Whois Release 1.93

Dear Working Group, RIPE Database release 1.93 has been deployed to the Release Candidate environment. If no issues are found, we plan to deploy to production on Monday, 25th February. Release 1.93 includes the following main changes: * Improved email address validation. * Do not allow

Re: [db-wg] Suggestion further validity-checking

Hi Jens, > On 28 May 2019, at 13:59, Jens Ott - Opteamax GmbH wrote: > > Hi Ed, > >> >> Whois does validate the holes attribute when creating or updating a >> route/route6 object, but these invalid values were added before this rule >> was added (in 2009 or earlier). > > The attributes of

Re: [db-wg] Suggestion further validity-checking

Hi Jens, > On 28 May 2019, at 12:07, Jens Ott - Opteamax GmbH via db-wg > wrote: > > Dear DB-WG, > > I am newly subscribed to this mailing-list although I am already active > in RIPE-community for quite some time. Some of you might know me in person. > > To be honest, I am not sure if this

Re: [db-wg] NWI-8: LIR's SSO Authentication Groups - Implementation Plan

Hi Tore, Cynthia, > On 24 May 2019, at 09:20, Tore Anderson wrote: > > * Edward Shryane via db-wg > >> here is the RIPE NCC's proposed implementation plan for NWI-8: LIR's SSO >> Authentication Groups. > > Hi Ed. > > I was unfortunately unable to make

[db-wg] GDPR and the RIPE Database

Dear Working Group, as mentioned in last week's DB-WG meeting, we will shortly be implementing the following changes: - Do not include personal data in historical queries (notify, e-mail, address attributes). - Do not include person/role references in historical queries (admin-c, tech-c,

[db-wg] Extending Unreferenced Object Cleanup

Dear Working Group, as presented at last week's DB-WG meeting, I'd like to extend the current Unreferenced Object Cleanup: https://www.ripe.net/manage-ips-and-asns/db/support/clean-up-of-unreferenced-data which deletes the following unreferenced objects after 90 days: - organisation,

[db-wg] Authenticating References to Objects

Dear Working Group, as mentioned at last week's DB-WG meeting, I'd like to propose extending authenticating references to other objects. Currently, only references to organisation objects can be protected with the mnt-ref attribute. However, we could extend this protection to other types of

[db-wg] Whois Release 1.94.1

Dear Working Group, RIPE Database release 1.94.1 has been deployed to the Release Candidate environment. This is a bug-fix release, with no new features. If no issues are found, we plan to deploy to production on Monday, 8th July. This release contains two main changes: - Consistent

Re: [db-wg] Whois Release Process

Dear Working Group, as there isn't a clear consensus on dropping the Release Candidate environment for bug fixes, we will continue to use it for all releases. Regards Ed Shryane RIPE NCC > On 23 May 2019, at 20:20, Edward Shryane via db-wg wrote: > > Hi Cynthia, Working Group, &

Re: [db-wg] Whois Release Process

Hi Nick, > On 23 May 2019, at 14:37, Nick Hilliard wrote: > > Cynthia Revström via db-wg wrote on 23/05/2019 14:26: >> Ed proposed a change to the WHOIS release process at the DB-WG session @ >> RIPE78. >> This change would be to immediately deploy bug fixes without a release >> candidate. >>

Re: [db-wg] Whois Release 1.94

Dear Working Group, we have now deployed Whois 1.94 to production. Regards Ed Shryane RIPE NCC > On 24 Apr 2019, at 14:34, Edward Shryane via db-wg wrote: > > Dear Working Group, > > RIPE Database release 1.94 has been deployed to the Release Candidate > environment. If n

Re: [db-wg] Whois Release 1.94.1

Dear Working Group, we have now deployed Whois 1.94.1 to production. Regards Ed Shryane RIPE NCC > On 24 Jun 2019, at 17:03, Edward Shryane via db-wg wrote: > > Dear Working Group, > > RIPE Database release 1.94.1 has been deployed to the Release Candidate > environment.

[db-wg] Whois Release 1.94

Dear Working Group, RIPE Database release 1.94 has been deployed to the Release Candidate environment. If no issues are found, we plan to deploy to production on Wednesday, 8th May. Release 1.94 includes the following changes: * Notify the user in the abuse-c comment if address validation has

Re: [db-wg] AUT-NUM authorization on ROUTE(6) objects

Hi Hank, DB-WG, > On 25 Aug 2019, at 19:47, Hank Nussbacher via db-wg wrote: > > Didn't we also say that route object creation should generate an alert to AS > origin admin-c or tech-c? > > -Hank > > Yes, this change was documented at the time in the NWI-5 impact analysis:

Re: [db-wg] AUT-NUM authorization on ROUTE(6) objects

Hi Sander, DB-WG, > On 25 Aug 2019, at 18:16, Sander Steffann via db-wg wrote: > > Hi, > > I was looking at > https://www.ripe.net/manage-ips-and-asns/db/support/documentation/ripe-database-documentation/10-authorisation/10-7-protection-of-route-6-object-space > > That page still documents

[db-wg] Whois Release 1.95

Dear Working Group, RIPE Database release 1.95 has been deployed to the Release Candidate environment. If no issues are found, we plan to deploy to production on Monday, 9th September. This release contains two main changes: - Whois queries are now normalised to the latin-1 character set, in

Re: [db-wg] Extending Unreferenced Object Cleanup

Dear Working Group, > On 27 May 2019, at 11:08, Edward Shryane via db-wg wrote: > > > Dear Working Group, > > as presented at last week's DB-WG meeting, I'd like to extend the current > Unreferenced Object Cleanup: > ... > to also delete the following groups of un

[db-wg] Synchronising Users from the LIR Portal to the Default Maintainer in the RIPE Database

Dear colleagues, Following a request by the Database Working Group earlier this year, we have implemented a new feature to synchronise users from the LIR Portal to the Default Maintainer in the RIPE Database. More information can be found in the Labs article:

Re: [db-wg] Whois Release 1.95.1

Dear Working Group, We have now deployed Whois 1.95.1 to production. Regards Ed Shryane RIPE NCC > On 4 Sep 2019, at 17:22, Edward Shryane via db-wg wrote: > > Dear Working Group, > > RIPE Database release 1.95.1 has been deployed to the Release Candidate

Re: [db-wg] Synchronising Users from the LIR Portal to the Default Maintainer in the RIPE Database

Dear Colleagues, we have now deployed this feature in the LIR Portal. Regards Ed Shryane RIPE NCC > On 18 Sep 2019, at 16:56, Edward Shryane via db-wg wrote: > > Dear colleagues, > > Following a request by the Database Working Group earlier this year, we have > impleme

Re: [db-wg] Internationalized domain names in the data abase?

Hi Piotr, DB-WG, > On 6 Nov 2019, at 21:17, Piotr Strzyzewski wrote: > >> DB-WG: should we allow non-ASCII addresses in the RIPE database? > > Do you mean email addresses or street addresses as well? > I mean to continue to allow non-ASCII (i.e. Latin-1 encoded) IDN email addresses, such as

Re: [db-wg] Internationalized domain names in the data abase?

Hello Ronald, DB-WG, > On 6 Nov 2019, at 00:13, Ronald F. Guilmette via db-wg wrote: > >>> I have found at least one specific case where an IDN does appear >>> in the data base as a UTF-8 encoded string, but since I had >>> never seen that before, I just wanted to know if that was an >>>

Re: [db-wg] Internationalized domain names in the data abase?

Hello Ronald, > On 2 Nov 2019, at 21:55, Ronald F. Guilmette via db-wg wrote: > > Sorry if I am interrupting any ongoing discussion, but I just > have a quick and simple question... > > Is it permitted to have internationalized domain names appear > within the database? > Currently the RIPE

Re: [db-wg] Internationalized domain names in the data abase?

Hi Nick, > On 8 Nov 2019, at 11:19, Nick Hilliard wrote: > > Edward Shryane via db-wg wrote on 08/11/2019 10:10: >> - if (a), should the RIPE database automatically convert IDN domain >> names in email addresses into punycode? > > Where though? Only in fields wh

Re: [db-wg] Internationalized domain names in the data abase?

Hello Ronald, DB-WG, > On 6 Nov 2019, at 23:46, Ronald F. Guilmette via db-wg wrote: > > In message <20191106210554.gb5...@hydra.ck.polsl.pl>, > Piotr Strzyzewski wrote: > >> I do not object having properly coded non-ASCII email addresses in the >> database. > > First, just to be clear, we

Re: [db-wg] Whois Release 1.96

Dear Working Group, We have now deployed Whois 1.96 to production. We have also performed the "Remove legacy status remark attribute" and "Remove aut-num mnt-lower attribute" cleanups. Regards Ed Shryane RIPE NCC > On 20 Nov 2019, at 17:10, Edward Shryane via db-wg w

Re: [db-wg] Removing the Legacy Status "remarks" attribute

11:41, Edward Shryane via db-wg wrote: > > Dear Colleagues, > > As presented during the DB-WG session at RIPE 79, we plan to remove the > legacy status "remarks" attribute from inetnum and aut-num objects in the > RIPE database. > > This remark was added

Re: [db-wg] Removing the "mnt-lower" attribute from aut-num objects

. updates won't fail). We will notify the DB-WG again once this is complete. Regards Ed Shryane RIPE NCC > On 21 Oct 2019, at 11:34, Edward Shryane via db-wg wrote: > > Dear Colleagues, > > as presented during the DB-WG session at RIPE 79, we plan to remove the > "mnt-lo

[db-wg] Cleanup Locked Person Objects - Implementation Plan

Dear Colleagues, As presented during the DB-WG session at RIPE 79, we will shortly begin to cleanup locked person objects in the RIPE database. We will select person objects maintained by RIPE-NCC-LOCKED-MNT, which are referenced by inetnum allocations or assignments, and re-assign them to the

[db-wg] Whois Release 1.96

Dear Working Group, RIPE Database release 1.96 has been deployed to the Release Candidate environment. We plan to deploy to production on Wednesday 4th December. This release contains the following main changes since 1.95.1: * Added "country:" attribute to organisation object type * Deprecated

Re: [db-wg] GDPR and the RIPE Database

ailgun.ipregistry.co/c/eJwdjbsOgjAAAL-m3SDQWtChA0IIISCbRhfTF9LIyxYQ_l5icrncdpJKwTDCUNM4ym93w_3qEhckXjNWJtUafNKszJz09pAc4OSaL1sxb87Tnt4LQGdHfMHB65hu3dffYuhgQ2uuQsKxJIJzjxB1lL7HUEgwQlgGdQBb2kzTaAGOAEp39Kj7enD1sDfjs1XQUGUbs7Fe7QOjR-X2avoBd-Y3FA>) > are legally wrong? are you going to take any action? > > Regards, > Laurent > > Le lun. 7 oct. 2019 à 12:38, Edward Shryane via db-wg <mailto:db-wg@ripe.net>> a écrit : > Dear Working Group,

Re: [db-wg] GDPR and the RIPE Database

ase-release-1.95> Apologies if this was not clear. Regards Ed Shryane RIPE NCC > On 27 May 2019, at 11:30, Edward Shryane via db-wg wrote: > > Dear Working Group, > > as mentioned in last week's DB-WG meeting, we will shortly be implementing > the following changes: >

Re: [db-wg] database support for ed25519 PGP keys

Hello Marco, > On 18 Dec 2019, at 18:35, Marco d'Itri via db-wg wrote: > > Can RIPE staff clarify if there are plans to support PGP authentication > of database updates using ed25519 keys? > This should require not much more that upgrading gnupg to a modern release. > We've supported the

[db-wg] NWI-9: Making the Whois NRTM Service Public

Dear colleagues, Last month, as part of the DB-WG NWI-9 proposal, the RIPE NCC Executive Board resolved to make the Whois NRTM Service public. The full minutes of the Board meeting are on our website:

Re: [db-wg] 2018-06 Proposal Implemented (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)

ane via db-wg wrote: > > Dear Working Group, > > The RIPE NCC Database team have now implemented the 2018-06 proposal (now > ripe-731), "RIPE NCC IRR Database Non-Authoritative Route Object Clean-up". > > We plan to deploy this to production on Wednesday 15th Jan

[db-wg] 2018-06 Proposal Implemented (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)

Dear Working Group, The RIPE NCC Database team have now implemented the 2018-06 proposal (now ripe-731), "RIPE NCC IRR Database Non-Authoritative Route Object Clean-up". We plan to deploy this to production on Wednesday 15th January. A nightly job will run from that evening onwards. We expect

Re: [db-wg] poetic-form mnt-by/creation

Hi Cynthia, This sounds like a bug. According to the RIPE database documentation: "A poetic-form object defines the supported poem types. A new ‘poetic form' must be approved by the community ‘style council'."

Re: [db-wg] Whois Release 1.97

Dear Working Group, We have now deployed Whois 1.97 to production. Regards Ed Shryane RIPE NCC > On 18 Mar 2020, at 16:02, Edward Shryane via db-wg wrote: > > Dear Working Group, > > RIPE Database release 1.97 has been deployed to the Release Candidate > environment.

[db-wg] Whois Release 1.97.1

Dear Working Group, RIPE Database release 1.97.1 has been deployed to the Release Candidate environment. We plan to deploy to production on Wednesday 6th May. This is a bugfix release, with no new functionality. The release notes are on the website:

[db-wg] Whois Release 1.97

Dear Working Group, RIPE Database release 1.97 has been deployed to the Release Candidate environment. We plan to deploy to production on Wednesday 1st April. The major change in this release is to open the NRTM service (regardless of membership status). The release notes are on the website:

Re: [db-wg] API keys for database maintenance

Hi Gunnar, We're indeed also working on Client Certificate authentication (we have tested it, and now it's pending a security review). However, to make use of this, a user must: - Generate an X.509 certificate - Extract the certificate as text and create a key-cert object from it - Associate

Re: [db-wg] API keys for database maintenance

Dear Colleagues, I support this proposal, it's an improvement for RIPE DB users and also benefits the DB team. I propose implementing the feature within an SSO account, as both the LIR Portal and RIPE database (at least) can share the same feature, and we reduce the implementation cost. We

Re: [db-wg] Whois Release 1.97.1

Dear Working Group, We have now deployed Whois 1.97.1 to production. Regards Ed Shryane RIPE NCC > On 22 Apr 2020, at 16:58, Edward Shryane via db-wg wrote: > > Dear Working Group, > > RIPE Database release 1.97.1 has been deployed to the Release Candidate > environment.

Re: [db-wg] mntner with misleading primary key

Hi Chriztoffer, > On 7 Sep 2020, at 12:45, Chriztoffer Hansen via db-wg wrote: > > On 07/09/2020 12:16, ripedenis--- via db-wg wrote: >> enforce this on all 'new' MNTNER object creations >> I'm all for enforcing this syntax per you comment above. > > Makes sense to _always_ be able to expect

Re: [db-wg] MNTNER Naming : Consensus

Dear colleagues, Here is the impact analysis on the proposal to require the suffix '-MNT' when creating new MNTNER objects. (1) Impact to Whois Update When creating an MNTNER object, an additional syntax check will be performed on the MNTNER name to require an -MNT suffix. If this suffix is

Re: [db-wg] Whois Release 1.98

Dear Working Group, We have now deployed Whois 1.98 to production. Regards Ed Shryane RIPE NCC > On 17 Sep 2020, at 15:49, Edward Shryane via db-wg wrote: > > Dear Working Group, > > RIPE Database release 1.98 has been deployed to the Release Candidate > environment.

[db-wg] Whois Release 1.98

Dear Working Group, RIPE Database release 1.98 has been deployed to the Release Candidate environment. We plan to deploy to production on Thursday 1st October. This release includes the following main changes: * NWI-11 Punycode Internationalized Domain Names in email addresses. * Return remark

[db-wg] Cleanup Locked Person Objects in the RIPE Database (Implementation on 3rd June)

Dear colleagues, As previously announced, the RIPE Database Team plan to clean up locked person objects in the RIPE Database. We will select person objects maintained by RIPE-NCC-LOCKED-MNT, which are referenced by inetnum allocations or assignments, and re-assign them to the resource

Re: [db-wg] To internationalise or not, that is the question?

ts. > > > > > > cheers > > > denis > > > > > > co-chair DB-WG > > > > > > On Wednesday, 29 July 2020, 18:20:14 CEST, Leo Vegoda > > <mailto:l...@vegoda.org>> wrote: > > > > > > > > > Hi, > > > >

Re: [db-wg] NWI-11 Internationalised Domain Names

Hello Gert, Benedikt, > On 7 Jul 2020, at 15:03, Gert Doering via db-wg wrote: > > Hi, > > On Tue, Jul 07, 2020 at 02:53:47PM +0200, Benedikt Neuffer via db-wg wrote: >> I don't get it. Does the RIPE DB prevent the usage of punycode? >> >> Can someone give me an example, where punycode

Re: [db-wg] Puny code or UTF-8 (or both)?

Hello Peter, WG, > On 13 Jul 2020, at 15:03, Peter Koch via db-wg wrote: > > On Mon, Jul 13, 2020 at 12:12:42PM +, ripedenis--- via db-wg wrote: > >> Do we therefore have support to introduce Puny code now and then consider >> how to move forward with UTF-8? > > I'm not sure I understand

Re: [db-wg] RDAP fails, WHOIS works

Hi Brian, The DB team publishes a list of known issues with our RDAP implementation in our repository: https://github.com/RIPE-NCC/whois/blob/master/README.RDAP.md We've been making improvements to our RDAP implementation over time, in cooperation with the other RIRs (to resolve ambiguities in

[db-wg] Whois Release 1.97.2

Dear Working Group, RIPE Database release 1.97.2 has been deployed to the Release Candidate environment. We plan to deploy to production on Monday 6th July. This release includes the following changes: • Improved inetnum status validation to align with RIPE policy •

Re: [db-wg] NWI-11 Internationalised Domain Names

Dear Colleagues, Here is the impact analysis for the NWI-11 implementation. The Database team plans to implement NWI-11 as per the Solution Definition: https://www.ripe.net/ripe/mail/archives/db-wg/2020-June/006525.html (1) Impact to Whois Update The implementation will automatically apply

Re: [db-wg] proposal: new attribute 'geofeed:

Hi Michael, > On 8 Jan 2021, at 15:16, Michael Kafka via db-wg wrote: > > Dear members, > ... > Much more critical are the 100k or maybe even millions of RIPE-db > entries, containing name and street address of natural persons which > are under the sole control of RIPE. > > Best regards, > >

[db-wg] Cleanup of trailing dot in "nserver:" attributes in domain objects in the RIPE database

Dear colleagues, The RIPE NCC database team have found some syntactically incorrect "nserver:" attributes in domain objects in the RIPE database, which contain a trailing dot ('.') character (signifying a fully qualified name). The convention since 2012 has been to strip out this trailing dot

[db-wg] Domain Object Cleanup in the RIPE Database

Dear colleagues, As mentioned in the Operational update during the DB-WG session at RIPE81, the RIPE NCC will shortly clean up (delete) domain objects without a mandatory "nserver:" attribute. This will affect approximately 1,600 domain objects in the RIPE database, which have not been

[db-wg] Whois Release 1.99

Dear Working Group, RIPE Database release 1.99 has been deployed to the Release Candidate environment. We plan to deploy to production on Monday 21st December. This release includes the following main changes: * NWI-10: require -mnt suffix * Filter out sensitive information in API response on

Re: [db-wg] Whois Release 1.99

Hi Sander, > On 7 Dec 2020, at 17:29, Sander Steffann wrote: > > Hi, > >> * NWI-10: require -mnt suffix > > That description doesn't match the NWI number… > Apologies, the "-MNT Suffix" change does not have an NWI number. Thanks for pointing it out, I'll update the release notes. Regards

Re: [db-wg] Domain Object Cleanup in the RIPE Database

Dear colleagues, The RIPE NCC has now completed the domain object cleanup. A total of 1,582 domain objects without "nserver:" attributes were deleted and maintainers were notified. Regards Ed Shryane RIPE NCC > On 30 Nov 2020, at 11:09, Edward Shryane via db-wg wrote: > &

Re: [db-wg] Whois Release 1.99

Dear Working Group, We have now deployed Whois 1.99 to production. Regards Ed Shryane RIPE NCC > On 7 Dec 2020, at 16:44, Edward Shryane via db-wg wrote: > > Dear Working Group, > > RIPE Database release 1.99 has been deployed to the Release Candidate > environment.

Re: [db-wg] Weirdness in DB files

Hi Cynthia, The DB team will investigate further and let you know. Regards Ed Shryane RIPE NCC > On 17 Dec 2020, at 03:49, Cynthia Revström via db-wg wrote: > > Hi DB-WG, > > I just noticed that the (at the time of writing, serial 49363913) latest > aut-num split db file (possibly

Re: [db-wg] proposal: new attribute 'geofeed:'

Hi Denis, Colleagues, > On 5 Jan 2021, at 14:30, denis walker wrote: > > Hi Ed > > Can you do a quick count on INETNUM and INET6NUM objects and see how > many currently have a "remarks: Geofeed" attribute and if any have > more than one. > I found 47 inetnums, 17 inet6nums and 2 aut-num

Re: [db-wg] Deprecation of whitepages

Hi Denis, > On 28 Jan 2021, at 19:37, denis walker wrote: > > Hi Will > > I wasn't aware that the RIPE Atlas system/service had any reliance on > objects in the RIPE Database. Maybe Robert can elaborate more on this? > > There are only 4 PERSON objects in the RIPE Database that reference >

Re: [db-wg] Deprecation of whitepages

Hi Will, Denis, > On 28 Jan 2021, at 20:30, Will Scott wrote: > > Can I request that EON11-RIPE be added to the same list? > I have added EON11-RIPE to the exclude list for the cleanup unreferenced object job. > That satisfies my immediate goal as much as the white page, > and the

Re: [db-wg] Removal of bogon route objects

Hi Ronald, > On 11 Jun 2021, at 23:19, Ronald F. Guilmette via db-wg > wrote: > > In message <4282f6ef-99c9-4306-817b-95382487c...@ripe.net>, > Edward Shryane wrote: > >>> I see. That message is very interesting. There are a couple of parts >>> of it that I have trouble interpreting

Re: [db-wg] "status:" attribute values in the RIPE database

Hi Carsten, > On 7 Jun 2021, at 12:57, Carsten Schiefner wrote: > > Ed & all - > > makes sense to me, too. > > However: Instead of forcing this on the creator/updater of an object - > how about the NCC to be as liberal as possible (John Postel's law, the > robustness principle) and to accept

Re: [db-wg] Issue creating new AS-SET

Hi Job, Denis, > On 9 Jun 2021, at 15:55, Job Snijders via db-wg wrote: > > On Wed, Jun 09, 2021 at 02:29:17PM +0200, Denis Fondras via db-wg wrote: >> I am trying to add a new AS-SET but I get an error : >> >> as-set: Syntax error in AS201376:AS-MEMBERS:DIRECT >> >> AS201376:AS-MEMBERS

[db-wg] Whois Release 1.101

Dear Working Group, RIPE Database release 1.101 has been deployed to the Release Candidate environment. We plan to deploy to production on Thursday 1st July. This release includes the following main changes: * Switch RIPE database to UTC timezone (all timestamps will be in UTC and all

Re: [db-wg] fulltextsearch question

Hi Hank, The webpage is restricted to a maximum of 10 pages with 10 matches on each page, but if you don't mind reading XML or JSON you can make the call directly: XML: https://apps.db.ripe.net/db-web-ui/api/rest/fulltextsearch/select?facet=true=true=(TEST)=0=800 JSON:

Re: [db-wg] fulltextsearch question

Hi Hank, > On 17 Jun 2021, at 23:46, Edward Shryane via db-wg wrote: > > Hi Hank, > > I spoke too soon, Whois still restricts the maximum results to 100. I'll > investigate how to retrieve more results and get back to you. > > Regards > Ed > Apologies for

Re: [db-wg] fulltextsearch question

Hi Hank, > On 18 Jun 2021, at 07:36, Hank Nussbacher wrote: > > On 18/06/2021 00:38, Edward Shryane wrote: > > This helps as a start. I had played with standard search: > http://rest.db.ripe.net/search?type-filter=inetnum=TEST > but as per the documentation in github: >

Re: [db-wg] fulltextsearch question

Hi Hank, > On 18 Jun 2021, at 08:32, Hank Nussbacher wrote: > > On 18/06/2021 08:36, Hank Nussbacher wrote: > > As I delve deeper I am more confused. I went to: >

Re: [db-wg] fulltextsearch question

Hi Hank, You can also use the "-a" or "--all-sources" flag instead of enumerating all possible sources with multiple "--sources" flags. Regards Ed > On 21 Jun 2021, at 10:38, Edward Shryane via db-wg wrote: > > ... > As a workaround, you

  1   2   3   >