Hi Lutz

Is your problem with the RPSL syntax in an AUT-NUM you try to create in the RIPE Database, or with some RPSL parser you are using on data you have extracted from the RIPE Database?

Nick, "You may want to think twice about whether it's worth investing time and

effort in rpsl in 2020". Given that the discussion you tried to get going recently on the future of RPSL hardly got off the ground, then unless someone already has advanced plans on a replacement for RPSL I don't see it going away anytime soon.

cheers

denis

co-chair DB-WG

On Thursday, 2 July 2020, 17:12:29 CEST, Nick Hilliard via db-wg <db-wg@ripe.net> wrote:

Lutz Donnerhacke via db-wg wrote on 02/07/2020 15:47:

> I try to be a bit more expressive in the aut-num of ASN199284, but
> fail to get accepted at least the valid parts by the RPSL parser.

rpsl(ng) hasn't seen any significant development work since the 1990s,
and the only real update since then was to support ipv6 (rfc4012 in
2005). The only functional parser out there, irrtoolset, is crippled
with functional shortcomings and is basically abandonware.

You may want to think twice about whether it's worth investing time and
effort in rpsl in 2020.

Nick