> That's true. There's also an architectural distinction between the two > sets of functions. One set of function allows a consumer access to IP > packets. The other set of functions helps the provider implement access > to these IP packets for the consumers. > > Let's just include them, I don't really care which project-private > functions appear in these materials, to be honest.
OK. > > > That is because the rest of the netinfo API is Committed. > > > > I find that a weak justification. Just because part of an API is > > Committed doesn't mean all parts of it need to be. > > That's true, but I also don't have a good justification for providing > access to interface flags and zoneid's, but making it private while > every other aspect of the API is Committed. Is there a particular > concern? Two concerns: (1) I don't like bolting down APIs we have limited experience with and (2) I'm always uncomfortable bolting down more lif-related stuff. -- meem
