Re: [db-wg] RPSL parser nits

Correct! I just drawing attention that while implementing the whois server, we've also checked some rpsl parsers, and most of them failed the sanity checks, even for parsing. As for interpreting the mp-export/import lines, those have a grammar that is also included in the rpsl parser in whois serv

Re: [db-wg] RPSL parser nits

Horváth Ágoston János wrote on 16/08/2020 19:57:> The ripe whois database (https://github.com/RIPE-NCC/whois) has an excellent (=clean, performant and heavily tested) RPSL parser in it for java. It's minimal work to copy the package, or, since this is BSD licence, you could release a copy of it

Re: [db-wg] RPSL parser nits

Hi Nick et al, The ripe whois database (https://github.com/RIPE-NCC/whois) has an excellent (=clean, performant and heavily tested) RPSL parser in it for java. It's minimal work to copy the package, or, since this is BSD licence, you could release a copy of it for others to use too. Cheers, Agost

Re: [db-wg] RPSL parser nits

Hi Lutz (and sorry for the late reply), Maybe you can have a look on “PolicyParser” located here: https://github.com/stkonst/PolicyParser It hasn’t received any commit the last 4 year, however It was working well until the moment I left the NLnet Labs.

Re: [db-wg] RPSL parser nits

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". Gi

Re: [db-wg] RPSL parser nits

> You may want to think twice about whether it's worth investing time and > effort in rpsl in 2020. That's true, but I do need some style of machine readable documentation internally as well as an slightly competent looking aut-num object for peering purposes. So the only choices are: a) inven

Re: [db-wg] RPSL parser nits

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 wa

[db-wg] RPSL parser nits

Hello, 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. Of course, there are invalid expressions in my terms for the sake of expressiveness, i.e. - next-hop is only valid for static routes - communities must