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: disallow creation of new non-hierarchically named AS-SET objects
- Previous message (by thread): [db-wg] proposal: disallow creation of new non-hierarchically named AS-SET objects
- Next message (by thread): [db-wg] proposal: disallow creation of new non-hierarchically named AS-SET objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Edward Shryane
eshryane at ripe.net
Mon Nov 21 15:00:21 CET 2022
Hi Denis, Colleagues, > On 21 Nov 2022, at 13:54, denis walker via db-wg <db-wg at ripe.net> wrote: > > Colleagues > > The chairs discussed this issue over the weekend and agreed that we > see a consensus to change the syntax rules for AS-SET object names in > the RIPE Database. We also agreed that we believe this feature request > can be managed through the Numbered Work Item process. We therefore > ask the RIPE NCC to document 'NWI-19 Change to AS-SET object naming > rules'. I've updated the NWI page: https://www.ripe.net/manage-ips-and-asns/db/numbered-work-items This change will go live shortly after an internal review. > > The chairs would like the RIPE NCC to prepare an impact analysis. > The DB team will prepare an impact analysis now. Regards Ed Shryane RIPE NCC
- Previous message (by thread): [db-wg] proposal: disallow creation of new non-hierarchically named AS-SET objects
- Next message (by thread): [db-wg] proposal: disallow creation of new non-hierarchically named AS-SET objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]