<html><head></head><body><div class="ydp21049696yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div></div> <div dir="ltr" data-setdir="false">Hi Gert</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">You are right, this has been an issue for many years. It is not only the problem of parsing RPSL but also an issue with people understanding it as a language and applying it correctly. But should this be an issue taken up by the IETF? Or do you think the RIPE Database could/should do something different to all other IRRs?</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">cheers</div><div dir="ltr" data-setdir="false">denis</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">co-chair DB-WG</div><div dir="ltr" data-setdir="false"><br></div><div><br></div> </div><div id="ydp4c683329yahoo_quoted_0440346518" class="ydp4c683329yahoo_quoted"> <div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;"> <div> On Thursday, 14 May 2020, 14:45:11 CEST, Gert Doering <gert@space.net> wrote: </div> <div><br></div> <div><br></div> <div>Hi,<br clear="none"><div class="ydp4c683329yqt5561396357" id="ydp4c683329yqtfd21788"><br clear="none">On Thu, May 14, 2020 at 09:52:06AM +0000, ripedenis--- via routing-wg wrote:<br clear="none">> Just a comment on the RPSL issue from the RIPE 80 session today. RPSL has little to do with the accuracy of data in the RIPE IRR. RPSL is just a language. Assuming you understand the language, it is your choice whether or not you maintain your data and keep it accurate and up to date.</div><br clear="none"><br clear="none">Right.<br clear="none"><br clear="none">That said, the data quality regarding import: and output: lines in the<br clear="none">RIPE DB is so poor that "bad and useless" is not halfway sufficient <br clear="none">to describe its badness.<br clear="none"><br clear="none">I think import/export is beyond repair - it is too complex to correctly<br clear="none">parse, and at the same time not expressive enough to describe policy<br clear="none">precisely enough ("export to AS X as peer, no further upstreaming permitted"<br clear="none">vs. "export to AS Y as upstream, further distribution expected").<br clear="none"><br clear="none">Gert Doering<br clear="none"> -- NetMaster<br clear="none">-- <br clear="none">have you enabled IPv6 on something today...?<br clear="none"><br clear="none">SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer<br clear="none">Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann<br clear="none">D-80807 Muenchen HRB: 136055 (AG Muenchen)<br clear="none">Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279</div> </div> </div></body></html>