[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1322520920.6118.42.camel@mojatatu>
Date: Mon, 28 Nov 2011 17:55:20 -0500
From: Jamal Hadi Salim <jhs@...atatu.com>
To: Justin Pettit <jpettit@...ira.com>
Cc: "Fischer, Anna" <anna.fischer@...com>,
"dev@...nvswitch.org" <dev@...nvswitch.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Herbert Xu <herbert@...dor.apana.org.au>,
David Miller <davem@...emloft.net>
Subject: Re: [ovs-dev] Issues with openflow protocol WAS(RE: [GIT PULL v2]
Open vSwitch
On Mon, 2011-11-28 at 10:44 -0800, Justin Pettit wrote:
> I realize you chair an IETF standard with overlapping goals with
> OpenFlow (ForCES), so you may have strong opinions about its design.
Yes, I do have strong opinions not really related to ForCES more towards
Linux. If i was to put ForCES in Linux (it is purely user space driven)
it would work with zero or small changes.
And my non-Linux opinions are driven because I have implemented some of
the things you folks are doing and look at them as advise more than
anything else.
> However, that's not relevant to this discussion, since OpenFlow's design
> has nothing to do with the discussion being held here in regards to Open
> vSwitch. OpenFlow is just a bullet point--although an important one--in
> a large set of features that Open vSwitch provides. Its design is such
> that it should be fairly easy to include new control protocols; OpenFlow
> is just a library in Open vSwitch. If you have issues with OpenFlow,
> those would be better directed to the ONF or one of the OpenFlow mailing
> lists.
I am not subscribed to any of those - and besides that the openflow hype
at the moment is so high on that wave nobody will listen ;->
The only reason i keep bringing up openflow is because your architecture
in the minimal evolved from there (the fact you deal with flows and
actions and switches). I could stop talking about it if it is
offensive ;->
cheers,
jamal
--
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