> > > > I'd still like the framework itself to not make assumptions about SAP > > > > space, even if meeting MAC client requirements means that MAC-type > > > > plugins are forced to all use similar SAP spaces. That way, we're not > > > > forcing future projects to re-design the framework over and over > > > > again. :-( > > > > > > True ... though I still think the SAP issue is a hole. > > > > At least from userland, it seems like we could handle this by enhancing > > libdlpi -- e.g., introduce a dlpi_bindproto() or somesuch that takes a > > protocol number and handles the conversion to the appropriate SAP value > > depending on the underlying link type. > > libdlpi seems like a decent home for it, but I'd rather have the > interface allow for handle-less conversion of names to numbers and > numbers to names. SAPs and MAC types can appear in other contexts > besides just DLPI streams, such as snoop capture files.
Understood. -- meem
