On Mon, Jan 15, 2007 at 10:46:36AM -0500, Larry J. Blunk wrote: > Erik Romijn wrote: > > > >What we propose to be included in the draft: > > > >- A new MRT routing information type: TABLE_DUMP_32BIT_AS. > > A current implementation in the library is to encode the 32bit AS flag > > into the address family field of the TABLE_DUMP, but this doesn't seem > > very nice. > > TABLE_DUMP_32BIT_AS would be the same as TABLE_DUMP, except with a > > 32bit field for the Peer AS. > > > My assumption is that implementations would move to > using the BGP4MP_ENTRY type for table dumps as it was meant > to replace the TABLE_DUMP type. The BGP4MP_ENTRY header > does not encode an AS number in the header and is transparent to > 32-bit AS numbers. I guess I could either create a new > TABLE_DUMP_32BIT_AS type or add text referring to the > BGP4MP_ENTRY type for 32-bit AS support.
I am in favour of TABLE_DUMP_32BIT_AS. I don't see any real advantage to moving to BGP4MP_ENTRY and do see significant extra work to modify software. Also, it wouldn't hurt to add TABLE_DUMP_32BIT_AS, would it? regards, -- Erik Romijn RIPE NCC jr. software engineer http://www.ripe.net/ Information Services dept.
pgpJcNBmYs1Qd.pgp
Description: PGP signature
_______________________________________________ GROW mailing list [email protected] https://www1.ietf.org/mailman/listinfo/grow
