Erik Romijn wrote:
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?
Yes, something like that.
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?
Perhaps, I wasn't clear. I was asking whether we need
to include the local (collector's) IP and AS number in addition
to the peer's IP and AS number. This information is included
in the BGP4MP_ENTRY type. I suspect this information is
not really needed and would simply bloat the dump files further.
Below is a proposed TABLE_DUMP_NEW type. The
View and Status fields have been dropped and the sequence
number field is expanded to 32-bits (as almost all dumps
contain more the 65,536 entries). The MRT Subtype field would
use bitfields to indicate peer IP type (IPv4 or IPv6), peer AS
size (16 or 32 bit), and NLRI type (IPv4-Unicast or
multi-protcol). If the NLRI type is IPv4-Unicast, the Prefix
Length and Prefix fields are included. If the NLRI type
is multi-protocol, the Prefix Length and Prefix fields are
omitted and the NLRI information is contained in the
MP_REACH_NLRI attribute.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originated Time |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer IP address (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer AS (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Prefix (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Attribute Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BGP Attributes... (variable)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
_______________________________________________
GROW mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/grow
