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]/
[db-wg] RPSL parser nits
- Previous message (by thread): [db-wg] RPSL parser nits
- Next message (by thread): [db-wg] RPSL parser nits
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Lutz Donnerhacke
L.Donnerhacke at iks-service.de
Thu Jul 2 17:21:19 CEST 2020
> 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?
- Previous message (by thread): [db-wg] RPSL parser nits
- Next message (by thread): [db-wg] RPSL parser nits
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]