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: [email protected], Phone: +49-030-577123821 Registry: Local court Charlottenburg, HRB 138876 Managing directors: Marc Korthaus, Theo Voss -- 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
