*** 20_questions.txt	Sun May 27 21:41:04 2007
--- 20_questions.txt.orig	Mon May 28 10:57:43 2007
***************
*** 57,68 ****
    device.  However, the plan is to integrate both the /dev/lo0 device and
    the ipnet component, at the same time.
  
  - What is its current status?
  
!   The /dev/lo0 component and the ipnet device have both been released on
!   Opensolaris.
  
  4. Are there related projects in Sun?  
  
     We will be using the new netinfo(9f) interfaces provided by the "Packet
     Filtering Hooks API" case (PSARC/2005/334). Currently the interfaces
--- 57,69 ----
    device.  However, the plan is to integrate both the /dev/lo0 device and
    the ipnet component, at the same time.
  
  - What is its current status?
  
!   The /dev/lo0 component has been released on Open Solaris as part of the
!   Clearview early access bits. The ipnet component is in development though
!   most of the major functionality is complete and is in a usable state.
  
  4. Are there related projects in Sun?  
  
     We will be using the new netinfo(9f) interfaces provided by the "Packet
     Filtering Hooks API" case (PSARC/2005/334). Currently the interfaces
***************
*** 560,572 ****
    will occur once there are devices in /dev/ipnet/ and unregister with the
    ip module in the event there are no IP interfaces configured and thus no
    devices in /dev/ipnet/.  In the ip module the registered callback
    functions are stored in a list, when a hook is run each callback will be
    called and data passed back to the caller. Both ipnet and /dev/lo0 will
!   process these messages using a taskq to avoid blocking the ip module.
!   The callback interfaces will be Project Private. The devices unregister
!   with the ip module by calling ip_unregister_cb().
  
    Given the simplicity of the callbacks this project plans on adding there
    should be nothing to prevent them been re-implemented using PEF (packet
    event framework) should it ever become available or another more generic
  
--- 561,573 ----
    will occur once there are devices in /dev/ipnet/ and unregister with the
    ip module in the event there are no IP interfaces configured and thus no
    devices in /dev/ipnet/.  In the ip module the registered callback
    functions are stored in a list, when a hook is run each callback will be
    called and data passed back to the caller. Both ipnet and /dev/lo0 will
!   process these messages from within their srv(9E) routines to avoid
!   blocking the ip module.  The callback interfaces will be Project Private.
!   The devices unregister with the ip module by calling ip_unregister_cb().
  
    Given the simplicity of the callbacks this project plans on adding there
    should be nothing to prevent them been re-implemented using PEF (packet
    event framework) should it ever become available or another more generic
  
***************
*** 679,690 ****
  
  - What is the impact on overall system performance?  What is the
    average working set of this component?  How much of this is
    shared/sharable by other apps?
  
!   In the case where the devices are not been used we expect no performance
!   impact.
  
  - Does this application "wake up" periodically?  How often and under
    what conditions?  What is the working set associated with this behavior?  
  
    N/A
--- 680,690 ----
  
  - What is the impact on overall system performance?  What is the
    average working set of this component?  How much of this is
    shared/sharable by other apps?
  
!   In the case where the devices are not been used we expect no performance impact.
  
  - Does this application "wake up" periodically?  How often and under
    what conditions?  What is the working set associated with this behavior?  
  
    N/A