Re: [db-wg] Whois Release 1.106

2023-02-20 Thread Edward Shryane via db-wg
Dear Colleagues, We have now deployed Whois 1.106 to production. Regards Ed Shryane RIPE NCC > On 6 Feb 2023, at 11:48, Edward Shryane via db-wg wrote: > > Dear Colleagues, > > RIPE Database release 1.106 has been deployed to the Release Candidate > environment. We plan to deploy to producti

Re: [db-wg] country codes in the RIPE Database (was: ORGANISATION country code)

2023-02-20 Thread Leo Vegoda via db-wg
On Thu, 26 Jan 2023 at 07:18, denis walker wrote: [...] > This is exactly what I said. In the quoted para above I said "the > country codes have a well defined meaning", which you agree with. Then > I said "but when entered by users no one knows what it's purpose is.". > Another way of saying no

Re: [db-wg] RIPE-NONAUTH AS-SET bug fix

2023-02-20 Thread Edward Shryane via db-wg
Hi Denis, Colleagues, > On 6 Feb 2023, at 11:51, Edward Shryane via db-wg wrote: > > Dear Colleagues, > > The upcoming Whois 1.106 release will include the requested change below: an > AS-SET "source:" will be set to "RIPE-NONAUTH" if the AUT-NUM is in > "RIPE-NONAUTH". > > We will also upda

Re: [db-wg] country codes in the RIPE Database (was: ORGANISATION country code)

2023-02-20 Thread denis walker via db-wg
Hi Leo On Mon, 20 Feb 2023 at 15:58, Leo Vegoda wrote: > > On Thu, 26 Jan 2023 at 07:18, denis walker wrote: > > [...] > > > This is exactly what I said. In the quoted para above I said "the > > country codes have a well defined meaning", which you agree with. Then > > I said "but when entered b

Re: [db-wg] country codes in the RIPE Database (was: ORGANISATION country code)

2023-02-20 Thread Leo Vegoda via db-wg
On Mon, 20 Feb 2023 at 07:25, denis walker wrote: > On Mon, 20 Feb 2023 at 15:58, Leo Vegoda wrote: [...] > > Setting semantics aside... I don't know whether changing definitions — > > and adding a missing definition is a de facto change — would improve > > things or make them worse. What resea