[db-wg] Entry Deduplication

Hello Peter,

The Query UI depends on the Whois REST API, which separates only "member:" attributes with comma-separated values, deduplicates and returns each value as a separate "members:" attribute, so member ASNs in the response can be more easily parsed. This is not done on Port 43 queries.

On update, currently there is no validation done to prevent duplicate "member:" values in an AS-SET (comma-separated or not).

It is possible to change either/both the query and update behaviour for AS-SET, if there is consensus to do so.

Regards
Ed Shryane
RIPE NCC



> On 28 Jul 2023, at 23:44, Peter Potvin via db-wg <db-wg at ripe.net> wrote:
> 
> Hey there DB-WG,
> 
> Apologies in advance if this is the wrong mailing list for this.
> 
> I noticed that the RIPE DB Query UI automatically deduplicates entries (i.e. multiple instances of an ASN in an AS-SET only appears once) through the webUI, however when queried through whois on any modem operating system the entry shows the raw data including the duplicates within it.
> 
> I'm a bit curious as to how this is done, and whether it's possible/planned to have the same functionality implemented in the WHOIS back-end that RIPE uses.
> 
> Regards,
> Peter Potvin | Executive Director
> ------------------------------------------------------------------------------
> Accuris Technologies Ltd.
> 56A Mill St E, Unit #470, Acton, ON L7J 1H3 Canada
> Email: peter.potvin at accuristechnologies.ca
> Office: +1 (877) 352-6105
> Network Operations Center: +1 (877) 321-1662
> -- 
> 
> To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/