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/[email protected]/
[routing-wg] RPSL
- Previous message (by thread): [routing-wg] RPSL
- Next message (by thread): [routing-wg] RPSL
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
ripedenis at yahoo.co.uk
ripedenis at yahoo.co.uk
Thu May 14 16:00:09 CEST 2020
Hi Gert 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? cheersdenis co-chair DB-WG On Thursday, 14 May 2020, 14:45:11 CEST, Gert Doering <gert at space.net> wrote: Hi, On Thu, May 14, 2020 at 09:52:06AM +0000, ripedenis--- via routing-wg wrote: > 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. Right. That said, the data quality regarding import: and output: lines in the RIPE DB is so poor that "bad and useless" is not halfway sufficient to describe its badness. I think import/export is beyond repair - it is too complex to correctly parse, and at the same time not expressive enough to describe policy precisely enough ("export to AS X as peer, no further upstreaming permitted" vs. "export to AS Y as upstream, further distribution expected"). Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/routing-wg/attachments/20200514/a88addd3/attachment.html>
- Previous message (by thread): [routing-wg] RPSL
- Next message (by thread): [routing-wg] RPSL
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]