On Mon, Jul 06, 2009 at 11:09:04PM -0400, Sebastien Roy wrote: > On Mon, 2009-07-06 at 19:43 -0700, Darren Reed wrote: > > Architecturally, I think it would be better to use a function call, > > as Eric suggested, and to provide a list of address family to SAP > > mappings and/or SAP aliases. That allows the interface to grow > > with networking, without being tied to IP. Thoughts? > > True, it's better that way if the MAC-Type API is to be extensible. The > part that feels strange is the Ethertype as input to this mapping > function. Perhaps mac.h could provide an enumeration of well-known SAPs > that it could use as input (SAP_IPV4, SAP_IPV6, SAP_ARP, etc...). >
yes, I would prefer this over adding fields to mactype_register_t. thanks eric
