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-NONAUTH AS-SET bug fix

Previous message (by thread): [db-wg] RIPE-NONAUTH AS-SET bug fix
Next message (by thread): [db-wg] Newbie-ish type of questions

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Edward Shryane eshryane at ripe.net
Mon Feb 20 16:13:38 CET 2023

Hi Denis, Colleagues,

> On 6 Feb 2023, at 11:51, Edward Shryane via db-wg <db-wg at ripe.net> 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 update *existing* AS-SET objects "source:" address accordingly when we deploy the Whois 1.106 release on Monday 20th February.
> 
> We will notify the maintainers of all affected AS-SET objects by email today.
> 

We have now updated 76 AS-SET objects "source:" attribute to "RIPE-NONAUTH" to match the AUT-NUM "source:", and notified the maintainers.

Regards
Ed Shryane
RIPE NCC

Previous message (by thread): [db-wg] RIPE-NONAUTH AS-SET bug fix
Next message (by thread): [db-wg] Newbie-ish type of questions

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]