Dear authors I reviewed this draft presented at IETF 117 and would like to provide some feedback.
I agree with the problem statement that the restart router all its LSAs still exist on all routers in the area until they maxage naturally. Am wondering if this is really a problem that needs to be fixed. I have never seen this cause any impact to routing aa this has existed Day 1. Once the router is down the intra area routes from the default RIB routing table are immediately removed, however even though the routes still exist in the LSDB that has no impact on the RIB / FIB hardware programming of the forwarding plane. I agree maybe as a cleanup process it maybe good to purge the LSDB, however naturally when the restart router establishes all its adj again to FULL during the FSM and flooding full SPF calc the new LSAs lower sequence numbers are flooded and the older stale LSAs are purged automatically by design. How does this new process of purging impact GR grace lsa restart router to helper router negotiation process of graceful restart and marking the old routes and LSDB entires as stale from the restart router for forwarding for Routing engine or processor switchover negotiated so traffic can flow hitless throughout the switchover process. As well the NSR non stop routing db checkpoint between active and standby route processor or engine locally significant not negotiated with neighbors. Kind Regards Gyan
_______________________________________________ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr
