Hi Lutz (and sorry for the late reply), Maybe you can have a look on “PolicyParser” located here: https://github.com/stkonst/PolicyParser <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. And is python based, so it will be easy for reading and patching/expanding. Hope the above helps. Best regards, Stavros Konstantaras | Sr. Network Engineer | AMS-IX M +31 (0) 620 89 51 04 | T +31 20 305 8999 ams-ix.net > On 2 Jul 2020, at 17:21, Lutz Donnerhacke via db-wg <db-wg@ripe.net> wrote: > >> 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) invent something new for internal usage and update the RADB in addition. > b) use the existing ideas and tools. > > I do not have any problem in patching or rewriting software, if necessary. > For solution a) I have to do everything by myself anyway, so where is the > difference to b), even if I'm the only user? > > If the projects are abandoned, who is to contact to shift the responsibility? >
