[dev] BGP Link State code

[olivier.dugeon at orange.com]

Dear all,

Many of you are interested by our very old code about BGP Link State.
So, I decided to publish it, but ***AS IS*** more as a proof of concept rather
than a running code.

It is based on a old version of Quagga. I don't know if it compiles, if it runs ...
As the code was unfortunately not versioned, I try to patch what seems
the Quagga version from which the code was written to produce the git commit.
But, I have not the time to check if the result compiles and if it is running.
*Please, d**on't ask me for that*.

As an old code, it is using old style. So, only new files are following FRR style.

The repo is here: https://github.com/Orange-OpenSource/Quagga-TE/tree/BGP-LS

The implementation is made of new files:

 - BGP-LS TLV definition: bgpd/bgp_ls.h
 - New Link State NLRI: bgpd/bgp_bgpls_nlri.c
 - Parser/Serializer: bgpd/bgp_ls_bgpls.c
 - BGP-LS Database: bgpd/bgp_lsdb.[c,h]
 - BGP API for OSPF-API: bgpd/bgp_api.[c,h], bgpd/bgp_ls_ospf.h
 - BGP Link State transcodage: bgpd/bgp_transcode.c
 - BGP to OSPF-API connection: bgpd/bgp_zbusclient.[c,h]

At least the NLRI, TLV definition, parser / serializer and LSDB could be
re-use easily. Of course all interaction with OSPF through OSPF API must
be replaced by the new ZAPI Opaque message.

And following files have been patched for integration:

 - bgpd/bgp_advertise.c, bgpd/bgp_aspath.c,
   bgpd/bgp_attr.|c,h], bgpd/bgp_btoa.c, bgpd/bgp_clist.c,
   bgpd/bgp_community.[c,h], bgpd/bgp_dump.c, bgpd/bgp_fsm.c, bgpd/bgp_main.c,
   bgpd/bgp_mplsvpn.c, bgpd/bgp_nexthop.c, bgpd/bgp_open.c, bgpd/bgp_packet.c,
   bgpd/bgp_route.c, bgpd/bgp_routemap.c, bgpd/bgp_table.c, bgpd/bgp_vty.c,
   bgpd/bgp_zebra.c, bgpd/bgpd.c, bgpd/bgpd.h

Where takes place the huge part of difficulties in order to merge them into FRR.

King regards

Olivier


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.