[db-wg] consensus on AS23456
- Previous message (by thread): [db-wg] consensus on AS23456
- Next message (by thread): [db-wg] consensus on AS23456
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Edward Shryane
eshryane at ripe.net
Tue Jul 13 10:02:53 CEST 2021
Hi Denis, Colleagues, I've added AS23456 as a reserved AS number to Whois. It's no longer possible to create a route(6) object with origin: AS23456, now an error will be returned: ***Error: Cannot use reserved AS number 23456 There are no existing route(6) objects in RIPE or RIPE-NONAUTH with origin: AS23456. Regards Ed Shryane RIPE NCC > On 12 Jul 2021, at 18:13, denis walker via db-wg <db-wg at ripe.net> wrote: > > 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] consensus on AS23456
- Next message (by thread): [db-wg] consensus on AS23456
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]