[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4ED09DC5.4000501@nicira.com>
Date: Sat, 26 Nov 2011 00:05:25 -0800
From: Martin Casado <casado@...ira.com>
To: Stephen Hemminger <stephen.hemminger@...tta.com>
CC: Jamal Hadi Salim <jhs@...atatu.com>, dev@...nvswitch.org,
Chris Wright <chrisw@...hat.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
Eric Dumazet <eric.dumazet@...il.com>,
netdev <netdev@...r.kernel.org>,
John Fastabend <john.r.fastabend@...el.com>,
David Miller <davem@...emloft.net>
Subject: Re: [ovs-dev] Open vSwitch Design
> Not sure how Openvswitch implementation relates to Openflow specification.
The short answer is that Open vSwitch serves as one of the standard
reference implementations for OpenFlow (in fact, the primary developers
of Open vSwitch were some of the original designers of OpenFlow).
Multiple hardware switches on the market use Open vSwitch as the basis
for their OpenFlow support.
>
> There are a few switches supporting Openflow already:
> http://www.openflow.org/wp/switch-nec/
> http://www-03.ibm.com/systems/x/options/networking/bnt8264/index.html
There are many other ports announced or available from vendors such as
HP, Brocade, Pica8, Extreme, Juniper, and NetGear. Cisco has even
announced support support for OpenFlow on the Nexus 3k
(http://www.lightreading.com/document.asp?doc_id=213545).
.martin
>
> The standard(s) are here:
> http://www.openflow.org/wp/documents/
>
> Good info from recent symposium:
> http://opennetsummit.org/past_conferences.html
> _______________________________________________
> dev mailing list
> dev@...nvswitch.org
> http://openvswitch.org/mailman/listinfo/dev
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Martin Casado
Nicira Networks, Inc.
www.nicira.com
cell: 650-776-1457
~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists