[db-wg] RIPE-NONAUTH AS-SET bug fix
- Previous message (by thread): [db-wg] Whois Release 1.106
- Next message (by thread): [db-wg] RIPE-NONAUTH AS-SET bug fix
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Edward Shryane
eshryane at ripe.net
Mon Feb 6 11:51:03 CET 2023
Dear Colleagues, The upcoming Whois 1.106 release will include the requested change below: an AS-SET "source:" will be set to "RIPE-NONAUTH" if the AUT-NUM is in "RIPE-NONAUTH". We will also update *existing* AS-SET objects "source:" address accordingly when we deploy the Whois 1.106 release on Monday 20th February. We will notify the maintainers of all affected AS-SET objects by email today. Regards Ed Shryane RIPE NCC > On 24 Jan 2023, at 16:55, Edward Shryane via db-wg <db-wg at ripe.net> wrote: > > Hi Denis, > > Here is an impact analysis for this change: > > * This change will increase the size of the RIPE-NONAUTH database. Up to now, objects could not be created in the RIPE-NONAUTH database (only updated or deleted). > > * Approximately 76 existing AS-SET objects referencing an aut-num object in RIPE-NONAUTH will have the source changed to RIPE-NONAUTH. We will notify the maintainer(s) accordingly. > > * Approximately 3 existing AS-SET objects referencing an ASN with no matching aut-num object in RIPE or RIPE-NONAUTH will also have the source changed to RIPE-NONAUTH and notify maintainer(s). > > * When an inter-RIR transfer of an AS number occurs, any AS-SET referencing the corresponding aut-num will have its source changed to match. > > Otherwise Whois behaviour is unchanged. > > We are implementing this change and will include in a Whois release shortly. > > Regards > Ed Shryane > RIPE NCC > > > >> On 16 Dec 2022, at 13:01, Edward Shryane via db-wg <db-wg at ripe.net> wrote: >> >> Hi Denis, >> >> The DB team will implement this change, including an impact analysis in advance. >> >> Regards >> Ed Shryane >> RIPE NCC >> >> >>> On 16 Dec 2022, at 10:29, denis walker <ripedenis at gmail.com> wrote: >>> >>> Colleagues >>> >>> The chairs agree that we have a consensus on making this change and >>> regarding it as a bug fix on the implementation of NWI-5. We therefore >>> ask the RIPE NCC to implement this bug fix when it is convenient to >>> fit it into their development plans. >>> >>> It can be done in two stages: >>> 1/ Creating any new AS-SET object authorised by an ASN in RIPE-NONAUTH >>> will also have the source RIPE-NONAUTH >>> 2/ Any existing AS-SET object that was created with authorisation by >>> an ASN in RIPE-NONAUTH will have it's source changed to RIPE-NONAUTH >>> >>> cheers >>> denis and William >>> co-chairs DB-WG >>> >> >> >> -- >> >> To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg > > > -- > > To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg
- Previous message (by thread): [db-wg] Whois Release 1.106
- Next message (by thread): [db-wg] RIPE-NONAUTH AS-SET bug fix
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]