[ovs-discuss] Why no-flood is not supported in later openflow versions?

Jianfeng Tan v.tan.jianfeng at gmail.com
Mon Jan 29 03:52:34 UTC 2018


>On Sun, Jan 28, 2018 at 11:39:29PM +0800, Jianfeng Tan wrote:
>> Hi,
>>
>> In the openflow, we set no-flood PodMod operation through openflow 1.0;
for
>> later openflow versions, no-flood is dropped.
>> We can refer to below two macro definitions.
>>
>>     #define OFPPC10_ALL (OFPPC_PORT_DOWN | OFPPC10_NO_STP |
OFPPC_NO_RECV |
>> \
>>                          OFPPC10_NO_RECV_STP | OFPPC10_NO_FLOOD |
>> OFPPC_NO_FWD | \
>>                          OFPPC_NO_PACKET_IN)
>>
>>     #define OFPPC11_ALL \
>>         (OFPPC_PORT_DOWN | OFPPC_NO_RECV | OFPPC_NO_FWD |
>> OFPPC_NO_PACKET_IN)
>>
>> Would like to know why no-flood is not one of the common flags? Or do we
>> have any other BKM to supersede such port config?
>
>The OpenFlow 1.1 and later specifications don't have a "no flood" bit.

Thank you for the reply.

We also notice that it's the OpenFlow protocol (later version) does not
support
this bit. But we wonder why it's removed from the protocol? It's useless? Or
we have an alternative to cover this.

Thanks,
Jianfeng
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-discuss/attachments/20180129/5cf43bf9/attachment-0001.html>


More information about the discuss mailing list