[Resending this post to the list as well]
Henk Uijterwaal (RIPE NCC) wrote:
Paragraph 4.7 currently does not take 32 bit ASN into account. However,
as of 1/1/2007, these will start to show up in the routing table. To make
this work, I suggest to add 2 new subtypes to the TABLE_DUMP type:
[...]
A couple more points:
1. I think we also need to provide a format to log BGP state changes
with 32-bit AS numbers. Since the AFI field in the state change
message comes after the AS field, we need a new subtype.
2. The BGP4MP_ENTRY subtype has a similar problem. Here, both the AFI
and SAFI fields are present so it seems that the intention is to
store the BGP AFI and SAFI values in the header. If that's the case,
the AFI field cannot be overloaded to indicate whether the entry uses
32-bit AS numbers or not, so we need a new subtype here as well.
So we could do the following:
0 BGP4MP_STATE_CHANGE
1 BGP4MP_MESSAGE
2 BGP4MP_ENTRY
3 BGP4MP_SNAPSHOT
4 BGP4MP_STATE_CHANGE_32BIT_AS
5 BGP4MP_ENTRY_32BIT_AS
6 BGP4MP_MESSAGE_32BIT_AS
Or we could just define a new type, BGP4MP_32BIT_AS, which would have
the same subtypes as BGP4MP. This would probably be simpler and more
elegant to implement, but requires more extensive changes to the draft
(I can help with those though).
Cheers,
Lorenzo
--
Lorenzo Colitti [EMAIL PROTECTED]
Network Engineer +31-20-5354471
RIPE NCC www.ripe.net
_________________________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
web archive: http://darkwing.uoregon.edu/~llynch/grow/
