Robert, You are perfectly entitled to this opinion - however but demoralising Shishio I fail to see what your post achieves ...
I welcome any new implementation of any RFC defined standard. I may not have a use for ruy's but giving others the option can not be a bad thing. Sincerely, Thomas --- from my iPhone > On 7 Aug 2014, at 11:03, Robert Raszuk <[email protected]> wrote: > > Hello Shishio, > > Sorry to ask the messenger, but what Ryu has to do with BMP ? Or for > that matter OpenFlow or OpenStack ? Enhancing Ryu with BMP is like > attaching a flower to the elephant :). > > Is Ryu suffering from such lack of popularity that bad so it is now > trying to enter BGP protocol monitoring space with its overhead ? What > value add Ryu provides to BMP processing or for that matter any > routing protocols ? > > BMP server and parser is just tiny user space code. The best is to > keep it standalone as far as possible from such "frameworks". > > You may find an example of an open source BMP receiver code from Stephen here: > > https://code.google.com/p/bmpreceiver/source/browse/#svn%2Ftags%2Frelease-1.1 > > Best regards, > R. > > >> On Thu, Aug 7, 2014 at 9:35 AM, Shishio Tsuchiya <[email protected]> wrote: >> F.Y.I >> Ishida-san who is NTT R&D announced Ryu has implemented BMPv3 on JANOG ml . >> >> https://github.com/osrg/ryu >> >> It supports BMPv3 and we confirmed interoperability with Cisco ASR1000 and >> Juniper MX960. >> >> Regards, >> -Shishio >> >> _______________________________________________ >> GROW mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/grow > > _______________________________________________ > GROW mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/grow > _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
