Brian Dickson wrote (on Fri 28-Dec-2012 at 19:02 +0000): > > 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 a route-refresh might repeat the error. But that doesn't make things any worse. In fact, since one would only keep those routes which the route-refresh sent correctly, that would improve things :-) The draft (section 5) talks about Graceful Restart and extensions thereof, but if those are not available, Route-Refresh might be. Is Route-Refresh a sufficiently common option that one can stop trying to square the "Once you have a malformed update, NOTHING is certain" circle ? It might be nice to only refresh/confirm the affected AFI/SAFI... but if MP_XXX attributes have gone walkabout, it may not be clear which AFI/SAFI those are :-( Chris _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
