On Tue, Nov 26, 2019 at 04:17:46PM -0800, Ayaka Koshibe wrote:
> Currently, we assume that OpenFlow 1.3 set_field actions can contain
> multiple header match fields (OXMs). According to specification, a
> set_field action contains exactly one OXM, followed by padding to align
> the action field in
On Tue, 26 Nov 2019 16:17:46 -0800, Ayaka Koshibe wrote:
> Currently, we assume that OpenFlow 1.3 set_field actions can contain
> multiple header match fields (OXMs). According to specification, a
> set_field action contains exactly one OXM, followed by padding to align
> the action field in a
Currently, we assume that OpenFlow 1.3 set_field actions can contain
multiple header match fields (OXMs). According to specification, a
set_field action contains exactly one OXM, followed by padding to align
the action field in a OpenFlow message to 64 bits.
This diff changes how we handle
