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] 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 ]
Randy Bush
randy at psg.com
Fri Oct 23 12:51:47 CEST 2015
>> On 22 Oct 2015, at 23:05, denis <ripedenis at yahoo.co.uk> wrote: >> >> Maybe I have missed something here. But I thought Tim was very clear >> that his proposal is to prevent the use of this MNTNER in a "mnt-by" >> attribute. He also said clearly it has nothing to do with the >> parallel discussion on hierarchical authorisation for out of region >> ROUTE objects. > > The current proposal just prevents the use of this maintainer on > mnt-by, but it is still used to authorise the creation of the > objects. This is easy to implement and just enforces current best > practice without fundamentally changing the authorisation model. > > Therefore we propose to do this as a quick first step +1 (despite the wg chairs having told us to vote otherwise) > then continue with the discussion below. sigh randy
- 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 ]