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/routing-wg@ripe.net/
[routing-wg] RPSL
- Previous message (by thread): [routing-wg] New on RIPE Labs: From REX to RIPEstat: a Look at the Past and the Challenges Ahead
- 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 11:52:06 CEST 2020
Colleagues 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. If we were to change from RPSL to something else the data would not necessarily be of any better quality. But it would be 'non standard' compared to all the other IRRs. Changing RPSL, as a means of inputting and outputting routing data, is not something that can be considered unilaterally within the RIPE Database. Perhaps a different question to ask could be, "is all the routing information contained in the RIPE Database still meaningful, useful and necessary (regardless of the language)?". cheersdenis co-chair DB-WG -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/routing-wg/attachments/20200514/1c746e3f/attachment.html>
- Previous message (by thread): [routing-wg] New on RIPE Labs: From REX to RIPEstat: a Look at the Past and the Challenges Ahead
- Next message (by thread): [routing-wg] RPSL
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]