> The ILL never goes up or down, it "just is", it is the > network interface that we consider to have changed state.
I don't know what you mean. An ill with one or more up ipifs is able to send and receive packets of that type (IPv4 or IPv6), and one that has no up ipifs cannot send or receive packets of that type. This is captured in the ill_ipif_up_count field, which is either checked for zero or non-zero. > Further, I don't believe that the names of internal structures > belong in externally visible event names (this interface needs > to become Committed once the we sort out the issues with > multiple hooks and dependencies.) I agree that separation of interface and implementation is important, but simply omitting the object associated with the event (as has been done with "NE_DOWN") does not accomplish that separation -- it just yields a confusing programming interface. > Also, if we were to do away with logical interfaces (a point > I believe you've brought up), then there would be no possible > confusion here. The core issue is whether it is possible to configure an address that is down. If it remains possible (which is probably necessary for backward compatibility), then the need to differentiate an "address up" event from an "interface up" event remains. -- meem _______________________________________________ networking-discuss mailing list [email protected]
