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] Prevent use of RIPE-NCC-RPSL-MNT in a mnt-by
- Previous message (by thread): [db-wg] Prevent use of RIPE-NCC-RPSL-MNT in a mnt-by
- Next message (by thread): [db-wg] Prevent use of RIPE-NCC-RPSL-MNT in a mnt-by
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at inex.ie
Fri May 15 14:39:14 CEST 2015
On 14/05/2015 19:27, denis wrote: > To prevent this situation getting any worse is, I believe, a one line fix > in the software. Adding this MNTNER name to a list of MNTNERs kept in the > software that users cannot directly reference will: > -prevent any new direct reference being made in user's objects > -force users to replace it with their own MNTNER if they want to update an > object that has a reference to this MNTNER > -have no impact on the intended use for hierarchical authorisaton > > I can't imagine anyone not agreeing with this, so if we get a few +1s the > NCC can implement this in the next software release. sounds good to me. Nick
- Previous message (by thread): [db-wg] Prevent use of RIPE-NCC-RPSL-MNT in a mnt-by
- Next message (by thread): [db-wg] Prevent use of RIPE-NCC-RPSL-MNT in a mnt-by
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]