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/db-wg@ripe.net/

[db-wg] consensus on AS23456

Previous message (by thread): [db-wg] Further cleanup (was: RIPE NONAUTH route(6) objects
Next message (by thread): [db-wg] consensus on AS23456

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

denis walker ripedenis at gmail.com
Mon Jul 12 18:13:53 CEST 2021

Colleagues

Whilst part of the discussion continues, there does seem to be a
consensus on adding AS23456 to the reserved list maintained by the
RIPE NCC. This would prevent anyone creating a ROUTE(6) object with
AS23456 as the origin.

The chairs also recognise the consensus to not delete or modify any
set objects that reference AS23456. This is in line with past views
not to purge set objects when an AUT-NUM object is deleted for any
reason.

The chairs therefore ask the RIPE NCC to add AS23456 to the RIPE
Database reserved list.

Regards
William & denis
co-chairs DB-WG

Previous message (by thread): [db-wg] Further cleanup (was: RIPE NONAUTH route(6) objects
Next message (by thread): [db-wg] consensus on AS23456

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

[ db-wg Archives ]