Thanks Acess, Les. So ideally it is recommended to tear down OSPF adjacency and signal topology change, and thus honor BFD notification in this case.
Regards, Anil On Tue, Aug 25, 2015 at 8:57 PM, Les Ginsberg (ginsberg) <ginsb...@cisco.com > wrote: > https://www.rfc-editor.org/rfc/rfc5882.txt Section 4.3 is relevant here. > > > > Les > > > > > > *From:* OSPF [mailto:ospf-boun...@ietf.org] *On Behalf Of *Acee Lindem > (acee) > *Sent:* Tuesday, August 25, 2015 7:54 AM > *To:* Anil Raj; OSPF WG List > *Subject:* Re: [OSPF] OSPF GR and BFD operability > > > > Hi Anil, > > > > OSPF and OSPFv3 graceful restart pre-dated BFD so this wasn’t explicitly > covered. However, given that the intension is that the data plane is > preserved during restart, an implementation could interpret this as a > topology change and terminate helper mode as documented in section 3.2 of > RFC 3623. > > Hope this helps, > > Acee > > > > > > > > *From: *OSPF <ospf-boun...@ietf.org> on behalf of Anil Raj < > anilra...@gmail.com> > *Date: *Tuesday, August 25, 2015 at 10:19 AM > *To: *OSPF WG List <ospf@ietf.org> > *Subject: *[OSPF] OSPF GR and BFD operability > > > > Hi, > > > > I need clarification on the behavior when BFD notifies remote inactivity > for a OSPF session, when OSPF neighbor is undergoing Graceful restart? OSPF > router in helper mode will ideally inactivate the restarting neighbor only > after grace period, and if BFD notifies neighbor down to OSPF, should the > adjacency be terminated? If not, will it cause a blackhole for the entire > grace period if the neighbor is actually down? > > > > Appreciate if you can help here. > > > > Regards, > > Anil > >
_______________________________________________ OSPF mailing list OSPF@ietf.org https://www.ietf.org/mailman/listinfo/ospf
