This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/
[db-wg] [opensource-wg] Question for RPSL Parser
- Previous message (by thread): [db-wg] [opensource-wg] Question for RPSL Parser
- Next message (by thread): [db-wg] [opensource-wg] Question for RPSL Parser
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Stavros Konstantaras
stavros at nlnetlabs.nl
Wed Aug 19 16:39:09 CEST 2015
Hi Wilfried. Yes I know that related RFCs are quite old but I wasn’t aware of this issue that you mention. Thanks for pointing it out. The oldness of RPSL is something that is already known to me and next year we will focus on that part. Kind Regards Stavros > On 19 Aug 2015, at 16:27, Wilfried Woeber <woeber at cc.univie.ac.at> wrote: > > Hi Stavros! > > On 2015-08-19 16:00, Stavros Konstantaras wrote: > [...] >> * George, yes you are right. This should be the #1 step, take corresponding >> RPSL RFCs and implement them in Python. > > A word of caution here... > > While this suggestion is probably a sound one, formally, everyone needs to > be aware that the set of RFCs out there is ancient. Not all of the provisions > in the documents have been implemented (in some or all IRRs) and, ototh, some > IRRs did implement some (minor?) extensions which never made it back into > updated documents. > > But I guess you are aware of that. > > FWIW, > Wilfried > >> However, that would take too much time and will not allow us to work on other missing functionalities of the prototype. And we would like to have something ready at the beginning of November. However, I will check your solution as well. >> >> I hope now that I made myself more clear. Big thanks to everyone, every help, info or idea is kindly appreciated. >> >> Kind Regards >> Stavros >> >> >> ---- >> Stavros Konstantaras >> Internet Research Engineer, NLnet Labs >> Science Park 400, 1098 XH, Amsterdam >> >> Fingerprint: 4502 7D16 2DF8 ADB0 4AA6 21A9 BF9E EFFF 2744 FE5D >> >>> On 19 Aug 2015, at 14:39, Tomas Hlavacek <tomas.hlavacek at nic.cz> wrote: >>> >>> Hi Stavros! >>> >>> On 08/19/2015 02:15 PM, Ondrej Filip wrote: >>>> >>>> Vis o necem? >>>> >>>> -------- Forwarded Message -------- >>>> Subject: [opensource-wg] Question for RPSL Parser >>>> Date: Wed, 19 Aug 2015 14:13:58 +0200 >>>> From: Stavros Konstantaras <stavros at nlnetlabs.nl> >>>> To: db-wg at ripe.net >>>> CC: opensource-wg at ripe.net >>>> >>>> >>>> >>>> >>>> Hi all WG members, >>>> >>>> For my project at NLnet Labs I would like to ask you if you know any >>>> (relatively) complete RPSL parser written in *Python*. I searched >>>> around and I didn’t find anything. Does someone know any repository >>>> where I can get one or maybe contact someone who has written one? >>> >>> It depends on what you need... I wrote one - >>> https://github.com/tmshlvck/bgpcrunch , but the aim was rather data >>> analysis than "authoritative" RPSL translation. When it comes to filter >>> interpretation my approach is quite "heuristic" and it is focused on >>> speed and ability to take short-cuts which wouldn't be possible with >>> full parsing the RPSL objects according to EBNF metasyntax. >>> >>> Have you considered creating simple Python interface for peval from >>> IRRToolSet? It might do the job if you don't need any special features. >>> >>> Cheers, >>> Tomas >> >>
- Previous message (by thread): [db-wg] [opensource-wg] Question for RPSL Parser
- Next message (by thread): [db-wg] [opensource-wg] Question for RPSL Parser
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]