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 ]
Christian Panigl, UniVie/ACOnet/VIX
Christian.Panigl at univie.ac.at
Fri Apr 28 19:52:37 CEST 2006
On 28.04.2006, at 19:24, Randy Bush wrote: > 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. Hi Randy, I don't think this alone would save your own (hopefully non- desaster ;-) prefixes from beeing damped somewhere, probably this would pose even a higher risk, that because of any instabilities in "The Internet" some far-ends would damp your (stable) prefixes. To really properly implement RFD for current BGP4 seems to be at least highly challenging, if you want to strictly avoid "false positives". One approach could be to apply damping only to prefixes which are originated by your direct (downstream) neighbors. To be effective, this would have to be done by every AS of course, which, however, won't be done because your direct neighbors beeing your customers are paying you for providing service not for damping them. Back to square one :-( Kind regards Christian
- 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 ]