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/db-wg@ripe.net/
[db-wg] Support for "::" notation in the "members" field
- Previous message (by thread): [db-wg] Support for "::" notation in the "members" field
- Next message (by thread): [db-wg] RIPE 85 session
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
James Bensley
james at inter.link
Fri Nov 4 13:29:17 CET 2022
Hi Nick, Thanks for the tip re; "Probably also this is routing-wg territory rather than db-wg." I will report to the routing-wg list. Regarding backwards compatibility; it breaks backwards compatibility with what? Within the scope of the IRR DB itself, I guess we need to ensure that an AS-SET or Route-Set can be called "RIPE::AS4200000011:AS-EXAMPLE-11" and that the same syntax is allowed in the members field. I think the problems you thinking off are external to the IRR DB (i.e., with irrd, bgpq3/4, irrtree, and similar tooling), or is there something else within the RIPE DB you think would break? If the former, I agree there will be issues with external tooling, but I want to address one thing at a time starting with the RIPE DB itself. If the later, what are you thinking? Kind regards, James Bensley (he/him) Network Team Inter.link GmbH Boxhagener Str. 80, 10245 Berlin, Germany Email: hello at inter.link, Phone: +49-030-577123821 Registry: Local court Charlottenburg, HRB 138876 Managing directors: Marc Korthaus, Theo Voss
- Previous message (by thread): [db-wg] Support for "::" notation in the "members" field
- Next message (by thread): [db-wg] RIPE 85 session
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]