On Tue, Jun 25, 2013 at 10:27:53AM -0700, Alex Wang wrote:
> Thanks for the answers.
>
>
> On Tue, Jun 25, 2013 at 10:24 AM, Ben Pfaff wrote:
>
> > On Tue, Jun 25, 2013 at 10:22:41AM -0700, Alex Wang wrote:
> > > Looks good to me.
> > >
> > > Curious about what do OFPBAC and ONFBIC stand for?
>
Thanks for the answers.
On Tue, Jun 25, 2013 at 10:24 AM, Ben Pfaff wrote:
> On Tue, Jun 25, 2013 at 10:22:41AM -0700, Alex Wang wrote:
> > Looks good to me.
> >
> > Curious about what do OFPBAC and ONFBIC stand for?
>
> These come from the OpenFlow specification. Presumably they stand for
> "
On Tue, Jun 25, 2013 at 10:22:41AM -0700, Alex Wang wrote:
> Looks good to me.
>
> Curious about what do OFPBAC and ONFBIC stand for?
These come from the OpenFlow specification. Presumably they stand for
"OpenFlow Protocol Bad ACtion" and "Open Networking Foundation Bad
InstruCtion".
Thanks for
Looks good to me.
Curious about what do OFPBAC and ONFBIC stand for?
On Mon, Jun 24, 2013 at 1:58 PM, Ben Pfaff wrote:
> This is a prototype of OpenFlow enhancement proposal EXT-260 "Add error
> code for duplicate instruction." It uses the error code proposed there.
>
> Signed-off-by: Ben Pfa
This is a prototype of OpenFlow enhancement proposal EXT-260 "Add error
code for duplicate instruction." It uses the error code proposed there.
Signed-off-by: Ben Pfaff
---
v3->v4: Fold in change to ofp-actions.at that was (and
incorrectly) in the previous patch in older versions.
lib/ofp-acti
