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] Proxy proposal large communities
- Previous message (by thread): [db-wg] Proxy proposal large communities
- Next message (by thread): [db-wg] Proxy proposal large communities
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at foobar.org
Mon Nov 13 12:58:57 CET 2017
Job Snijders wrote: > Can we, based on the observation that irrtoolset will consider any > extension to the RPSL rp-attribute dictionary an error, conclude that > RPSL can not be extended in this direction? How did you come to this conclusion? irrtoolset is non rfc compliant, not the other way around. At a practical level, it's relatively easy to add a new token into the rpsl parser to shut irrtoolset up, even if it's a mess to add proper support for large communities to the code so that they actually do what you'd expect of them. > Another approach would be to introduce yet another 'import/export'-style > attribute, so that we'd have 'import:', 'export:', 'mp-import:', > 'mp-export:', 'import-via:', 'export-via:', and now also: > 'import-via-large:', 'export-via-large:'. Though this doesn't strike me > as a healthy direction for growth and extendability. No need for export-via-large. "export-via" was required because it changed the semantics of the export stanza. Nick
- Previous message (by thread): [db-wg] Proxy proposal large communities
- Next message (by thread): [db-wg] Proxy proposal large communities
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]