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] 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 ]
Job Snijders
job at instituut.net
Mon Nov 13 12:22:04 CET 2017
On Mon, Nov 13, 2017 at 12:16 PM, Mark Prior <mrp at mrp.net> wrote: > On 13/11/17 21:36, Job Snijders wrote: >> On Mon, Nov 13, 2017 at 12:01 PM, Mark Prior <mrp at mrp.net> wrote: >>> In this particular case I would suggest that you do want the tool to >>> complain rather than ignore the new rp-attribute. >> >> Why would you break backwards compatibility? >> > It's only broken if you include a large community formatted string in > your policy and your tool doesn't support it. In that case I would like > the script to break rather than load a broken configuration to a router > that potentially causes chaos. OK, but what about the tools from other people/organisations that parse your autnum object? I'm not sure why you ignore the recommendation "When changing the dictionary, full compatibility should be maintained." without offering any arguments on what the benefits for doing so are.
- 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 ]