Hi Nitish, Irrespective of any IPR discussions, BFD is inherently a P2P protocol and, consequently, I would vote for P2P peer table.
Thanks, Acee From: rtgwg <[email protected]<mailto:[email protected]>> on behalf of "Nitish Gupta (nitisgup)" <[email protected]<mailto:[email protected]>> Date: Thursday, August 31, 2017 at 1:51 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, Routing WG <[email protected]<mailto:[email protected]>> Cc: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "Aditya Dogra (addogra)" <[email protected]<mailto:[email protected]>> Subject: Re: draft-nitish-vrrp-bfd Hi Thibault, Thanks for the interest in the Draft, appreciate it. Please review the draft and let us know if you have any comments, suggestions. Hi RTGWG/RTGBFD, There were two solutions proposed in the draft. One pertains to making a peer table in VRRP and uses p2p BFD. The second solution pertains to p2mp BFD. While we were working on the draft there was an IPR associated to the DRAFT and the WG felt that we need to wait until we can see the IPR and what its associated to. We can see that the IPR is available for us to view and we can see that the IPR is associated to p2mp BFD. https://www.google.com/patents/US20170005915 We are going to submit a draft with the p2p BFD so that we can continue working on the Draft. There was lot of interest last time as well, just because of the IPR claim we had stopped the work. Thanks, Nitish From: Greg Mirsky <[email protected]<mailto:[email protected]>> Date: Tuesday, August 29, 2017 at 11:01 AM To: TABANI Thibault <[email protected]<mailto:[email protected]>> Cc: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "Nitish Gupta (nitisgup)" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: draft-nitish-vrrp-bfd Resent-From: <[email protected]<mailto:[email protected]>> Resent-To: <[email protected]<mailto:[email protected]>>, <[email protected]<mailto:[email protected]>>, <[email protected]<mailto:[email protected]>>, <[email protected]<mailto:[email protected]>>, <[email protected]<mailto:[email protected]>> Resent-Date: Tuesday, August 29, 2017 at 11:01 AM Hi Thibault, thank you for your interest in the draft, much appreciated. Please don't be discouraged that it lapsed, we can fix it easily. I think that authors had similar to your idea when we've started thinking about BFD supporting VRRP. And like you we haven't found any reference in existing documents, hence this draft draft-nitish-vrrp-bfd. Would be much obliged if you review and share your comments, suggestion regarding solutions proposed in the draft. Regards, Greg On Tue, Aug 29, 2017 at 9:20 AM, TABANI Thibault <[email protected]<mailto:[email protected]>> wrote: Hello, I am working at improving VRRP convergence time. (target a few 100’s of milliseconds) It appears that VRRP supports BFD health monitoring which might be a better option than tuning VRRP aggressive timers. Unfortunately I cannot find any active RFC where VRRP supports BFD. The only document I found is your draft document: Fast failure detection in VRRP with BFD draft-nitish-vrrp-bfd-04 Unfortunately date expires of this document. As BFD support for VRRP is implemented on most routers, I suppose that an active RFC might exist on that specific BFD implementation within VRRP. (new backup advertisement messages….peer table….) br Thibault TABANI architect Altran Connected Solutions Altran France [id:[email protected]] 1, Impasse Charles Trenet 44800 Saint-Herblain France Tel. : +33 2 40 67 62 62<tel:+33%202%2040%2067%2062%2062> Mob. : +33 6 79 06 33 63<tel:+33%206%2079%2006%2033%2063> [email protected]<mailto:[email protected]> www.altran.fr<http://www.altran.fr/> [escription : Description : cid:[email protected]]<http://facebook.com/AltranFrance>[escription : Description : cid:[email protected]]<http://twitter.com/AltranFrance>[escription : Description : LinkedIn_signatureMail]<http://linkedin.com/company/altran-france>[escription : Description : pictog_viadeo]<http://www.viadeo.com/fr/company/altran>
