yasu at nttv6.jp
Tue Dec 18 20:01:08 EST 2018
BMP is similar with MRT dump framework so the injection points
would be right next to the MRT functions. For now, I think the pthread
is too much to do, and I will do it without the dedicated pthread
(probably keeping the future pthread-enabled design in mind).
I will copy the route table stanpshot for the BMP initial stage, and the
BGP updates it gets while processing BMP initial downloading part.
In order not to block the normal BGP operations, the BMP green thread
will yield before it finishes his process; in this way the BGP view
is consistent and the BMP would not block other threads.
Each BMP sessions will have the dedicated route table(s) and the
BGP update queue that serves as the pointer in the BMP data processing.
The BMP session processing (listen and accept) is similar to the
vty and so we can put the access-list on it for security.
I've already started the work and have done the listen-accept part,
but let me take some more time to clear my company's approval
to make the code open.
Meanwhile we can discuss the additional issues that I'm missing.
I hope that I can share the first draft implementation
before mid January.
From: François <francois.serman at corp.ovh.com>
Subject: Re: [dev] BMP
Date: Mon, 17 Dec 2018 15:26:28 +0100
Message-ID: <20181217142628.GE23115 at desk826773.desk.int.gns.ovh.net>
> On Tue, Dec 12, 2018 at 10:05:55AM +0900, Yasuhiro Ohara wrote:
>> I am open to any requests for the BMP feature.
> How do you plan to proceed?
> I might be interested in that topic ;)
> dev mailing list
> dev at lists.frrouting.org
More information about the dev