IAM
======
Name:           Crossbow - Network Virtualization and Resource Management
Submitter:      Kais Belgaied
Owner:          Kais Belgaied
Intern:         Michael Speer
Interest:
Status:         preinception scheduled 06/04/2008
Exposure:       open


SUMMARY
=======

Crossbow is a network virtualization technology that greatly
improves resource control, performance and network utilization needed to
achieve true OS virtualization, utility computing and server consolidation.
Crossbow will be the foundation for future innovation in network
security (DDOS, IDM, etc.), consolidated appliances, and end-to-end
resource control.


ISSUES
======
#ident "@(#)issues      1.5 08/06/04 SAC"

djr-01  how do flows relate to squeues, if they do? Do they share squeues or?
  

djr-02  the materials mention configuring "many interfaces" - how does this
        scale? O(N), O(N^2) or...?

djr-03  what are the plans for providing observability to the switch engine?

djr-04  are there any plans for dtrace sdt probes?
======> Yes

djr-05  will statistics be provided through kstats as well as flowadm?
======> 

djr-06  why is libdladm the only library associated with flowadm?
        what connection does a flow defined using layer 3 or 4 or
        both have to do with the datalink layer? - if that is managed
        through libdladm, if it isn't then why isn't there a seperate
        library in the diagram?
======> The libraries are not exposed.

djr-07  layer3/4 classification in layer2 (MAC) seems like an architectural
        mistake (from a purist perspective)

seb-01  Is there a technical reason why removing the "PPA hack" support
        from GLDv3 is being done as part of this project?  Is implicit
        link creation at open(9e) time generally harder to do with the
        Crossbow architecture?

======> Talk offline with project team. 
        Opinion should note this.

ged-01  What is the interaction between this project and ndd(1M), if any?
======>	Use Brussels project to add properties. There is no dependency.
	Man pages list the properties.


THE NEXT STEP
=============
Project team must recode APIs in Nevada today. 
Project team requests, people using APIs specific to MAC interfaces -
Direct them to the project team. 

Committee suggests creating a README in the case file and in the Nevada macinfo.x. If you are looking to use this structure...refer to this /
We anticipate this file will become obsolete.

In inception materials include diff file of headers.