[db-wg] proposal: disallow creation of new non-hierarchically named AS-SET objects

Hi Denis, Colleagues,

Following is the impact analysis of NWI-19. 

Low impact on Whois. 

* The DB team will disallow the creation of AS-SET objects which follow the 'short' naming style (i.e. starting with 'AS-' and without a colon). 
* Only AS-SET objects which follow the 'hierarchical' naming style (i.e. including one or more colons) can be created. 
* Existing AS-SET objects are not affected and can be updated or deleted as before. However, if an existing AS-SET object with short naming style is deleted, it cannot be re-created with the same name.

No impact on the LIR Portal or internal registry software.

No impact on the RPKI service.

Client software needs to be checked so that AS-SET objects with 'short' naming style will not be created in the RIPE database.

It will still be possible to create AS-SET objects with a 'short' naming style in other RIR databases and other IRR databases such as RADB. Clients may not be able to use the same name in the RIPE database as in other databases.

Implementing and deploying this change will take some time. In the meantime, there may be an increase in AS-SET object creation with a 'short' naming style.

Regards
Ed Shryane
RIPE NCC


> On 21 Nov 2022, at 15:00, Edward Shryane via db-wg <db-wg at ripe.net> wrote:
> 
> 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
> 
> 
> 
> -- 
> 
> To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/