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] RIPE-NONAUTH AS-SET bug fix

Previous message (by thread): [db-wg] RIPE-NONAUTH AS-SET bug fix
Next message (by thread): [db-wg] Whois Release 1.105

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Edward Shryane eshryane at ripe.net
Fri Dec 16 13:01:53 CET 2022

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
>

Previous message (by thread): [db-wg] RIPE-NONAUTH AS-SET bug fix
Next message (by thread): [db-wg] Whois Release 1.105

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]