On Wed, Jan 17, 2007 at 05:28:31PM -0500, Larry J. Blunk wrote: > Given the inconsistent and confusing implementation > support for BGP4MP_ENTRY, I'm tempted to mark it as > deprecated and define a new TABLE_DUMP type that includes > support for 16-bit or 32-bit AS numbers, and includes support > for NLRI other than IPv4 and IPv6.
So basically TABLE_DUMP with a 32-bit AS field and an NLRI field? > The only question I > have is should it include the local (destination) IP adddress and > AS in addition to the peer's IP and AS numbers? For RIS this is essential. When either we (for MySQL database insertion) or someone else reads the dumps they will have to know where a route actually came from. Ofcourse, there are messages somewhere in some dump that contain this information, but that would make things very very complex. Peer AS can be read from the AS path in most cases, but what about route servers that don't add their own AS? cheers, -- Erik Romijn RIPE NCC jr. software engineer http://www.ripe.net/ Information Services dept.
pgpV0EO4talRK.pgp
Description: PGP signature
_______________________________________________ GROW mailing list [email protected] https://www1.ietf.org/mailman/listinfo/grow
