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] Proposal to limit the use of the RIPE-NCC-RPSL-MNT on mnt-by

• Previous message (by thread): [db-wg] Proposal to limit the use of the RIPE-NCC-RPSL-MNT on mnt-by
• Next message (by thread): [db-wg] Proposal to limit the use of the RIPE-NCC-RPSL-MNT on mnt-by

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

Nick Hilliard nick at inex.ie
Thu Oct 22 19:02:23 CEST 2015

On 21/10/2015 15:32, Tim Bruijnzeels wrote:
> Provided that the working group agrees with this, we expect this can be
> done in the space of a few weeks after the business rule is
> implemented.

sounds good (i.e. +1).  Could you send 3M/1M/1W notifications of the
removal and the consequences of the object being locked?  Locking has
operational implications and a bunch of people got hit with problems due to
the mntner md5 locking issue a couple of months ago.

Nick

• Previous message (by thread): [db-wg] Proposal to limit the use of the RIPE-NCC-RPSL-MNT on mnt-by
• Next message (by thread): [db-wg] Proposal to limit the use of the RIPE-NCC-RPSL-MNT on mnt-by

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

[ db-wg Archives ]