Hi Lee,

<cc'ing networking--discuss also>

Thanks a lot for your feedback. Our current vision for CrossBow is to make the 
virtual NICs appear just like physical NICs. So you should be able to do 
trunking in the same way.

Could you please describe some more what kind of trusted capabilities you mean 
when you talk about rigid separation?

Markus


----- Original Message -----
From: Lee Hepler <[EMAIL PROTECTED]>
Date: Saturday, June 10, 2006 9:20 pm
Subject: Trunking in crossbow
To: [EMAIL PROTECTED]

> Dear Markus,
>
>  Would you please consider doing for networking what
> ZFS has done for storage? 
>  Trunking has previously been a separate product for
> combining several NICs into one virtual NIC.  Would
> you consider adding in the trunking capability to
> enable there to be a pool of NICs available in
> addition to having multiple virtual NICs operating on
> a single NIC?
>  ZFS has implemented the capabilities of several
> separate products into one much more efficient
> application with a vastly simpler management
> interface.  Please give me this capability with its
> improved performance and ease of use into the crossbow
> project.
>  Load balancing and automatic failover implemented in
> crossbow would further differentiate Solaris
> networking capabilities from LINUX and Windoze.
>  One requirement to this that you might not be aware
> of is that each NIC may be on a totally separate
> network that will require rigid separation implemented
> by Trusted Solaris.  I work on 7 separate networks
> that can never be directly interconnected.  But there
> is a requirement to transfer data between these
> networks under very stringent control implemented on
> single systems using Trusted Solaris.  Please also
> include trusted capabilities in the crossbow project.
>
> Thank you for listening,
> Lee Hepler
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>

_______________________________________________
networking-discuss mailing list
[email protected]

Reply via email to