Brian Dickson wrote (on Fri 28-Dec-2012 at 19:02 +):
>
> If there is a chance that some NLRI weren't properly decoded:
>
> - What about requesting (presuming the option was negotiated)
>a route-refresh, or a "confirm per-AFI-SAFI prefix list"?
If the sender is sending broken updates, then
Jakob Heitz wrote (on Fri 28-Dec-2012 at 21:35 +):
> All we can hope for after a malformed update is a
> temporary mitigation until human intervention can
> fix the problem.
>
> IMO, the goal of error handling is to limit the
> damage, not to cure the problem.
>From previous discussions i
Rob Shakir wrote (on Fri 28-Dec-2012 at 13:10 +):
>
> (re: CCing IDR & GROW)
>
> On 28 Dec 2012, at 12:28, Chris Hall wrote:
>
> > Rob Shakir wrote (on Thu 27-Dec-2012 at 18:44):
> >>
> >> Any comments very welcome (to me or grow@).
> > I'm afraid I still don't get it :-( What am I missing
Hi Brian,
We discussed this at some length previously (the -00 of the requirements draft
discussed automatically triggering some form of means to recover from the
error). I think that there is some merit in doing so, but there are clearly
also scaling considerations around this (in terms of req
