[dev] BFD daemon is now part of master

[Jia Chen]

Thank you very much!
Jay

From: dev <dev-bounces at lists.frrouting.org> on behalf of JR Rivers <jrrivers at cumulusnetworks.com>
Date: Tuesday, August 14, 2018 at 7:08 AM
To: Donald Sharp <sharpd at cumulusnetworks.com>
Cc: FRRouting-Dev <dev at lists.frrouting.org>
Subject: Re: [dev] BFD daemon is now part of master

Thanks!!!!!

On Tue, Aug 14, 2018 at 5:58 AM, Donald Sharp <sharpd at cumulusnetworks.com<mailto:sharpd at cumulusnetworks.com>> wrote:
Rafael -

Thanks for doing this work and driving this effort.  I know a whole
bunch of people have been asking for this integration into FRR.

donald

On Tue, Aug 14, 2018 at 8:50 AM, Rafael Zalamena
<rzalamena at opensourcerouting.org<mailto:rzalamena at opensourcerouting.org>> wrote:
> Hi all,
>
> Today the BFD daemon (`bfdd`) got merged into master. It implements
> the Bidirectional Forwarding Detection protocol and its main purpose
> is to detect link failures to notify services. The daemon is
> automatically built on standard distribution on all platforms.
>
> Currently the following FRR daemons support BFD:
>
> * bgpd;
> * ospfd;
> * ospf6d;
> * pimd;
>
> ---
>
> Background:
>
> The BFD daemon was implemented re-using some Cumulus implementation,
> but it was extracted from another service (
> https://github.com/CumulusNetworks/ptm/blob/master/src/ptm_bfd.c<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_CumulusNetworks_ptm_blob_master_src_ptm-5Fbfd.c&d=DwMFaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=yetdj-aXQpuqTCJGs-93hOpK3740MIRXowfUNLByeos&m=i0IYQ0dF_62kioFL5Ja_jwF9XSQJR_V5FQyYpg5tvuc&s=I5Sg1cPUtGeNOB73hFoRV1ypqcwoWLyfl1t6prQwzdk&e=> ).
> The code went through the following changes:
>
> * it became a stand alone daemon;
> * added new configuration interfaces: vtysh and control socket (using JSON);
> * replaced uthash.h with FRR's hash implementation;
> * added compatibility code to run on *BSDs;
> * changed event manager with FRR's;
> * minor code/protocol fixes;
>
> Related RFCs:
>
> * RFC 5880 (protocol description);
> * RFC 5881 (single hop IPv4/IPv6 implementation);
> * RFC 5883 (multi hop implementation);
>
> Thanks to everyone that helped reviewing the code!
>
> Rafael
>
> _______________________________________________
> dev mailing list
> dev at lists.frrouting.org<mailto:dev at lists.frrouting.org>
> https://lists.frrouting.org/listinfo/dev<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.frrouting.org_listinfo_dev&d=DwMFaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=yetdj-aXQpuqTCJGs-93hOpK3740MIRXowfUNLByeos&m=i0IYQ0dF_62kioFL5Ja_jwF9XSQJR_V5FQyYpg5tvuc&s=5eCT6Z0mzU6398siopJ4Ch3E4FKDJyf-tGkV5B34cRY&e=>

_______________________________________________
dev mailing list
dev at lists.frrouting.org<mailto:dev at lists.frrouting.org>
https://lists.frrouting.org/listinfo/dev<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.frrouting.org_listinfo_dev&d=DwMFaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=yetdj-aXQpuqTCJGs-93hOpK3740MIRXowfUNLByeos&m=i0IYQ0dF_62kioFL5Ja_jwF9XSQJR_V5FQyYpg5tvuc&s=5eCT6Z0mzU6398siopJ4Ch3E4FKDJyf-tGkV5B34cRY&e=>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frrouting.org/pipermail/dev/attachments/20180814/9115099f/attachment-0001.html>