ExaBGP 'back to school' release

This release only fixes two issues with 3.2.5

• a bug in the collision detection code (where both side would tear their TCP session and not the same)
• a fix to prevent the re-announcement of identical routes

ExaBGP 'github' release

This is the first release using github since we migrated from Google Code .... yesterday !

This version is still considered experimental and is not yet recommended for production use. However the code has been massively improved since the last 3.1 release and is passing all ever written regression test.

RFC implemented / completed

• draft-ietf-idr-flowspec-redirect-ip-00.txt
• complete RFC 5575 by :
  • providing support for flow-vpn
  • adding DCSP marking
  • adding traffic-action
• draft-raszuk-idr-flow-spec-v6-03

New features include

• An external program to announce a service only if it works correctly ( Thank you Vincent ! )
• ExaBGP can accept incoming connections ( not production ready ! )
• ExaBGP can decode incoming Flow routes
• using "next-hop self" is supported via the API
• new update code generation can group multiple NLRI, from different families, in one update packet
• NOTIFICATION message generation using the API
• API message control (limit diffusion to a subset of peers)
• better --decode option to find out what a hex dump of a route mean
• many small fixes, see the full CHANGELOG
• many many more test to prevent regressions
• new internals ... many, including
  • large rewrite of non-optimal code
  • new non-blocking reactor
  • new Adj-RIB-In and Adj-RIB-Out with scalable watchdog feature
• and more ....

Enjoy !