[routing-wg] Adding "::" notation to RIPE DB

Alexander Zubkov wrote on Thursday, November 10, 2022 8:07 AM:
> Maybe we can add some standard mechanism to identifiy the supported
> "features" by the IRR server? So client before sending the request
> can figure out whether the server supports source-tagged as-sets
> (like bgpq4 now checks if the server supports !a queries). Then the
> client can add some "flag" in the query that it is willing to receive
> source-tagged as-sets. On the server side we can strip source prefixes
> in the reply if the client did not identify its will to receive them.
> In that case legacy tools should not brake.

And not to forget to add this "feature probing" to NRTM sessions (and
likely other places).

Still, by introducing "::", you might change the way a set name is defined
in RFC2280/RFC2622 ... (might, because most of us likely read it as 'a 
single ":" separates AS numbers and set names' based on the examples).

Markus