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]Draft doc proposing Route Flap Damping Obsolesence
- Previous message (by thread): [routing-wg]Draft doc proposing Route Flap Damping Obsolesence
- Next message (by thread): [routing-wg]Draft doc proposing Route Flap Damping Obsolesence
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Rob Evans
rhe at nosc.ja.net
Fri Apr 28 19:58:36 CEST 2006
> i suggested that the rfd spec be modified, at least to be per-prefix as > opposed to prefix+path, to allow the disaster prefixes to be easily > detected and damped. I get the impression from RFC2439 (sec. 4.4.3) that the authors intended it would be optional for the path to be included in the per-route state, so perhaps some vendor pressure to implement the relevant knob? Or am I missing some other aspect of the document? Then the pathological prefixes could be damped by using some "generous" parameters that most prefixes would never reach in even the most severe circumstances. Is that the idea? Rob
- Previous message (by thread): [routing-wg]Draft doc proposing Route Flap Damping Obsolesence
- Next message (by thread): [routing-wg]Draft doc proposing Route Flap Damping Obsolesence
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]