Thx again both Larry and Mattia, Actually I am more looking for parsing MRT BGP4MP_MESSAGE containing bunch of raw UPDATE messages from peers rather then table dumps.
However libbgpdump seems like a good starting point ... if for nothing else then for parsing common message headers. Many thx, R. On Tue, Nov 27, 2012 at 5:45 PM, Larry Blunk <[email protected]> wrote: > > libbgpdump is available at http://www.ris.ripe.net/source/ and > contains the bgpdump tool which will read and process the table dump > and update files in the Routeviews and RIPE RIS archives. > > -Larry > > > > On 11/27/2012 11:33 AM, Robert Raszuk wrote: >> >> Thx Larry ! >> >> Any pointer to best MRT opensource tools repository for parsing the >> messages and maybe even performing some analysis on them (in >> particular related to BGP) ? >> >> Rgs, >> R. >> >> On Tue, Nov 27, 2012 at 5:28 PM, Larry Blunk <[email protected]> wrote: >>> >>> On 11/27/2012 11:17 AM, Robert Raszuk wrote: >>>> >>>> >>>> Hello, >>>> >>>> Does anyone (in particular cc-ed authors) recall what is the status, >>>> planned update, planned progress to RFC of this document: >>>> >>>> http://tools.ietf.org/id/draft-ietf-grow-mrt-04.txt >>>> >>>> Thx, >>>> R. >>>> >>> >>> It's an RFC now -- >>> >>> http://tools.ietf.org/html/rfc6396 >>> >>> Unfortunately, section 4.3.4 does not match the >>> current Quagga/libbgpdump implementations. The RFC >>> says to omit the AFI/SAFI/NLRI fields in the MP_REACH_NLRI >>> attribute (since that info is already in the MRT >>> RIB Entry Header), but the current implementations >>> simply copy the attribute as-is in the RIB Entry >>> field. >>> >>> Regards, >>> Larry Blunk >>> >>> > _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
