On Mon, Feb 12, 2007 at 03:50:27PM -0500, Larry Blunk wrote: > Erik Romijn wrote: > >> 2 IPV4_UNICAST > > > >One possibly stupid, certainly not all too relevant, question: why is > >this called IPV4_UNICAST, while it also stores IPv6 entries? > > IPV6 RIB entries would be stored in the MULTIPROTOCOL subtype. > The IPV4_UNICAST subtype is only for IPv4 Unicast RIB entries, > so there is no need to specify AFI and SAFI values (basically > saving you the 3 bytes needed to specify these).
OK, that makes good sense. Most of the routes in a dump will be IPv4. But if we're going for space savings, it might be beneficial to add IPV6_UNICAST at a later time, when the average dump also contains loads of IPv6 entries. Assuming no further comments arise, will a new version of the draft be published, with the TABLE_DUMP_V2 and BGP_STATE_CHANGE_AS4 types? It would be nice to have something to refer RIS rawdata users to.* * I know it's a bad thing(tm) to use a draft as a standard or refer to it for documentation, but I doubt I have any other option. cheers, -- Erik Romijn RIPE NCC jr. software engineer http://www.ripe.net/ Information Services dept.
pgp4k2Bz7JTDX.pgp
Description: PGP signature
_______________________________________________ GROW mailing list [email protected] https://www1.ietf.org/mailman/listinfo/grow
