OpenFlow Switch SpecificationVersion0.8.9(Wire Protocol0x97)December2,2008Current Maintainer:Brandon Heller(brandonh@)1IntroductionThis document describes the requirements of an OpenFlow Switch.We rec-ommend that you read the latest version of the OpenFlow whitepaper before reading this specification.The whitepaper is available on the OpenFlow Con-sortium website().This specification covers the components and the basic functions of the switch,and the OpenFlow protocol to manage an OpenFlow switch from a remote controller.OpenFlow Switches will be of“Type0”or“Type1”,depending on their ca-pabilities.Type0represents the minimum requirements for any conforming OpenFlow Switch.Type1requirements will be a superset of Type0,and re-main to be defined.It is expected that commercial OpenFlow Switches will initially be of Type0,evolving to Type1;and that vendors will support addi-tional features over time.However,all switches are expected to use the same OpenFlow Protocol for communication between switch and controller.For the remainder of this version of the document,unless otherwise specified,all refer-ences to an OpenFlow Switch refer to Type0.Version1.0of this document will be thefirst to specify a Type0switch suit-able for implementation.Versions before Version1.0will be marked“Draft”, and will include the header:“Do not build a switch from this specification!”We hope to generate feedback from versions prior to Version1.0from switch designers and network researchers.2Switch ComponentsAn OpenFlow Switch consists of aflow table,which performs packet lookup and forwarding,and a secure channel to an external controller(Figure1).The con-troller manages the switch over the secure channel using the OpenFlow protocol.1DO NOT BUILD A SWITCH FROM THIS SPECIFICATION!Figure1:An OpenFlow switch communicates with a controller over a secure connection using the OpenFlow protocol.Theflow table contains a set offlow entries(header values to match pack-ets against),activity counters,and a set of zero or more actions to apply to matching packets.All packets processed by the switch are compared against theflow table.If a matching entry is found,any actions for that entry are performed on the packet(e.g.,the action might be to forward a packet out a specified port).If no match is found,the packet is forwarded to the controller over the secure channel.The controller is responsible for determining how to handle packets without validflow entries,and it manages the switchflow table by adding and removingflow entries.3Flow TableThis section describes the components offlow table entries and the process by which incoming packets are matched againstflow table entries.Header Fields Counters ActionsTable1:Aflow entry consists of headerfields,counters,and actions.Eachflow table entry(see Table1)contains:•headerfields to match against packets•counters to update for matching packet•actions to apply to matching packets2DO NOT BUILD A SWITCH FROM THIS SPECIFICATION!3.1Header FieldsIngress PortEthersourceEtherdstEthertypeVLANidIP src IPdstIPprotoTCP/UDPsrcportTCP/UDPdstport Table2:Fields from packets used to match againstflow entries.Table2shows the headerfields an incoming packet is compared against. Each entry contains a specific value,or ANY,which matches any value.If the switch supports subnet masks on the IP source and/or destinationfields,these can more precisely specify matches.Thefields in the OpenFlow10-tuple are listed in Table2and details on the properties of eachfield are described in Table 3.Field Bits When applicable NotesIngress Port(Implementationdependent)All packets Numerical represen-tation of incomingport.Ethernet source ad-dress 48All packets on en-abled portsEthernet destina-tion address 48All packets on en-abled portsEthernet type16All packets on en-abled ports A Type0switch is required to match the type in both standard Ethernet and802.2with a SNAP header and OUI of0x000000. The special value of0x05FF is used to match all802.3 packets without SNAP headers.VLAN id12All packets of Eth-ernet type0x8100IP source address32All IP packets Can be subnetmaskedIP destination ad-dress 32All IP packets Can be subnetmaskedIP protocol8All IP packetsTransport source port/ICMP Type 16All TCP,UDP,andICMP packetsOnly lower8bitsused for ICMPTypeTransport destina-tion port/ICMP Code 16All TCP,UDP,andICMP packetsOnly lower8bitsused for ICMPCodeTable3:Field lengths and the way they must be applied toflow entries.Switch designers are free to implement the internals in any way convenient provided that correct functionality is preserved.For example,while aflow3DO NOT BUILD A SWITCH FROM THIS SPECIFICATION!may have multiple forward actions,each specifying a different port,a switch designer may choose to implement this as a single bitmask within the hardware forwarding table.3.2CountersCounters are maintained per-table,per-flow,and per-port.OpenFlow-compliant counters may be implemented in software and maintained by polling hardware counters with more limited ranges.Table4contains the required set of counters for Type0switches.Duration refers to the number of seconds aflow has been active.The Receive Errors field includes all explicitly specified errors,including frame,overrun,and CRC errors,plus any others.Counter BitsPer TableActive Entries32Packet Lookups64Packet Matches64Per FlowReceived Packets64Received Bytes64Duration32Per PortReceived Packets64Transmitted Packets64Received Bytes64Transmitted Bytes64Receive Drops64Transmit Drops64Receive Errors64Transmit Errors64Receive Frame Alignment Errors64Receive Overrun Errors64Receive CRC Errors64Collisions64Table4:Required list of counters for use in statistics messages.3.3ActionsEachflow entry is associated with zero or more actions that dictate how the switch handles matching packets.Actions need not be executed in the order in which they are specified in theflow entry.If no actions are present,the packet is dropped.A switch is not required to support all action types—just those marked“Re-quired Actions”below.When connecting to the controller,a switch indicates4DO NOT BUILD A SWITCH FROM THIS SPECIFICATION!which of the“Optional Actions”it supports.OpenFlow-compliant switches come in two types:OpenFlow-only,and OpenFlow-enabled.OpenFlow-only switches support only the required actions below,while OpenFlow-enabled switches,routers,and access points may also support the NORMAL action.Either type of switch can also support the FLOOD action.Required Action:Forward.Type0switches must support forwarding the packet to physical ports and the following virtual ones:•ALL:Send the packet out all interfaces,not including the incoming in-terface.•CONTROLLER:Encapsulate and send the packet to the controller.•LOCAL:Send the packet to the switchs local networking stack.•TABLE:Perform actions inflow table.Only for packet-out messages.•IN PORT:Send the packet out the input port.Optional Action:Forward.The switch may optionally support the following virtual ports:•NORMAL:Process the packet using the traditional forwarding path sup-ported by the switch(i.e.,traditional L2,VLAN,and L3processing.)A Type0switch may check the VLANfield to determine whether or not to forward the packet along the normal processing route.If the switch can-not forward entries for the OpenFlow-specific VLAN back to the normal processing route,it must indicate that it does not support this action.•FLOOD:Flood the packet along the minimum spanning tree,not includ-ing the incoming interface.Ideally,a switch will supportflow-entries that can forward packets to any com-bination of the physical and virtual ports.For example,this could be expressed internally in the switch with a bitmap that includes all the physical and virtual ports.However,some switches will not be able to support any combination.There-fore,the requirement is that the switch support sending to any combination of physical ports and the Controller virtual port simultaneously.All other combi-nations are desired,but optional.The controller will only ask the switch to send to multiple physical ports simulta-neously if the switch indicates it supports this behavior in the initial handshake (see section5.3.1).Required Action:Drop.Aflow-entry with no specified action indicates that5DO NOT BUILD A SWITCH FROM THIS SPECIFICATION!all matching packets should be dropped.Optional Action:Modify-Field.While not strictly required,the actions shown in Table5greatly increase the usefulness of an OpenFlow implementation.To aid integration with existing networks,we suggest that VLAN modification ac-tions be supported.3.4MatchingFigure2:The functions performed on a packet as it moves through an OpenFlow switch.As discussed in Section4.5,support for802.1D is optional in Type0 switches.Figure3:Aflow table showing how a packet is matched against aflow entry.On receipt of a packet,an OpenFlow Switch performs the functions shown in Figure2.6DO NOT BUILD A SWITCH FROM THIS SPECIFICATION! Action Associated Data DescriptionSet VLAN ID12bits If no VLAN is present,anew header is added withthe specified VLAN ID andpriority of zero.If a VLAN header alreadyexists,the VLAN ID is re-placed with the specifiedvalue.Set VLAN priority3bits If no VLAN is present,anew header is added withthe specified priority and aVLAN ID of zero.If a VLAN header alreadyexists,the priorityfield isreplaced with the specifiedvalue.Strip VLAN header-Strip VLAN header ifpresent.Modify Ethernet source MAC address 48bits:Value with whichto replace existing sourceMAC addressReplace the existing Eth-ernet source MAC addresswith the new valueModify Ethernet destina-tion MAC address 48bits:Value with which toreplace existing destinationMAC addressReplace the existing Eth-ernet destination MAC ad-dress with the new valueModify IPv4source address32bits:Value with which toreplace existing IPv4sourceaddress Replace the existing IP source address with new value and update the IP checksum(and TCP/UDP checksum if applicable). This action is only applica-ble to IPv4packets.Modify IPv4destination address 32bits:Value with which toreplace existing IPv4desti-nation addressReplace the existing IP des-tination address with newvalue and update the IPchecksum(and TCP/UDPchecksum if applicable).This action is only appliedto IPv4packets.Modify transport source port 16bits:Value with whichto replace existing TCP orUDP source portReplace the existingTCP/UDP source portwith new value and updatethe TCP/UDP checksum.This action is only applica-ble to TCP and UDP pack-ets.Modify transport destina-tion port 16bits:Value with whichto replace existing TCP orUDP destination portReplace the existingTCP/UDP destinationport with new value andupdate the TCP/UDPchecksumThis action is only appliedto TCP and UDP packets.Table5:Field-modify actions.7DO NOT BUILD A SWITCH FROM THIS SPECIFICATION!Theflow table is checked for a matchingflow entry.The headerfields used for the table lookup depend on the packet type as described below(and shown in Figure3).•Rules specifying an ingress port are matched against the physical port that received the packet.•The Ethernet headers as specified in Table2are used for all packets.•If the packet is a VLAN(Ethernet type0x8100),the VLAN ID is used in the lookup.•For IP packets(Ethernet type equal to0x0800),the lookupfields also include those in the IP header.•For IP packets that are TCP or UDP(IP protocol is equal to6or17), the lookup includes the transport ports.•For IP packets that are ICMP(IP prototcol is equal to1),the lookup includes the Type and Codefields.•For IP packets with nonzero fragment offset or More Fragments bit set, the transport ports are set to zero for the lookup.A packet matches aflow table entry if the values in the headerfields used for the lookup(as defined above)match those defined in theflow table.If aflow tablefield has a value of ANY,it matches all possible values in the header.To handle the various Ethernet framing types,matching the Ethernet type is handled in a slightly different manner.If the packet is an Ethernet II frame,the Ethernet type is handled in the expected way.If the packet is an802.3frame with a SNAP header and Organizationally Unique Identifier(OUI)of0x000000, the SNAP protocol id is matched against theflows Ethernet type.Aflow entry that specifies an Ethernet type of0x05FF,matches all Ethernet802.2frames without a SNAP header and those with SNAP headers that do not have an OUI of0x000000.Packets are matched againstflow entries based on prioritization.An entry that specifies an exact match(i.e.,it has no wildcards)is always the highest priority. All wildcard entries have a priority associated with them.Higher priority entries must match before lower priority ones.If multiple entries have the same priority, the switch is free to choose any ordering.Higher numbers have higher priorities. For each packet that matches aflow entry,the associated counters for that entry are updated.If no matching entry can be found for a packet,the packet is sent to the controller over the secure channel.8DO NOT BUILD A SWITCH FROM THIS SPECIFICATION!4Secure ChannelThe secure channel is the interface that connects each OpenFlow switch to a controller.Through this interface,the controller configures and manages the switch,receives events from the switch,and send packets out the switch. Between the datapath and the secure channel,the interface is implementation-specific,however all secure channel messages must be formatted according to the OpenFlow protocol.4.1OpenFlow Protocol OverviewThe OpenFlow protocol supports three message types,controller-to-switch,asyn-chronous,and symmetric,each with multiple sub-types.Controller-to-switch messages are initiated by the controller and used to directly manage or inspect the state of the switch.Asynchronous messages are initiated by the switch and used to update the controller of network events and changes to the switch state. Symmetric messages are initiated by either the switch or the controller and sent without solicitation.The message types used by OpenFlow are described below.4.1.1Controller-to-SwitchController/switch messages are initiated by the controller and may or may not require a response from the switch.Features:Upon SSL session establishment,the controller sends a features request message to the switch.The switch must reply with a features reply that specifies the capabilities supported by the switch.Configuration:The controller is able to set and query configuration parame-ters in the switch.The switch only responds to a query from the controller. Modify-State:Modify-State messages are sent by the controller to manage state on the switches.Their primary purpose is to add/delete and modifyflows in theflow tables and to set switch port properties.Read-State:Read-State messages are used by the controller to collect statis-tics from the switchsflow-tables,ports and the individualflow entries.Send-Packet:These are used by the controller to send packets out of a speci-fied port on the switch.4.1.2AsynchronousAsynchronous messages are sent without solicitation from the switch to the controller and denote a change in switch or network state.The four main asyn-chronous message types are described below.9DO NOT BUILD A SWITCH FROM THIS SPECIFICATION! Packet-in:For all packets that do not have a matchingflow entry,a packet-in event is sent to the controller(or if a packet matches an entry with a“send to controller”action).If the switch has sufficient memory to buffer packets that are sent to the controller,the packet-in events contain some fraction of the packet header(by default128bytes)and a buffer ID to be used by the controller when it is ready for the switch to forward the packet.Switches that do not support internal buffering(or have run out of internal buffering)must send the full packet to the controller as part of the event.Flow Expiration:When aflow entry is added to the switch,an idle time-out value is included that indicates when the entry should be removed due to a lack of activity,as well as a hard timeout value that indicates when the entry should be removed,regardless of activity.In the configuration message,the controller can indicate that it wishes to be informed when aflow expires.If this flag is set,the switch sends aflow expiration event that includes the duration of theflow and the number of packets and bytes sent.Flow expirations are only set when explicitly enabled by the controller,through the configuration message. Port-status:The switch is expected to send port-status messages to the con-troller as port configuration state changes.These events include change in port status(for example,if it was brought down directly by a user)or a change in port status as specified by802.1D(see Section4.5for a description of802.1D support requirements).Error:The switch is able to notify the controller of problems using error mes-sages.4.1.3SymmetricSymmetric messages are sent without solicitation,in either direction.Hello:Hello messages are exchanged between the switch and controller upon connection startup.Echo:Echo request/reply messages can be sent from either the switch or the controller,and must return an echo reply.They can be used to indicate the latency,bandwidth,and/or liveness of a controller-switch connection. Vendor:Vendor messages provide a standard way for OpenFlow switches to offer additional functionality within the OpenFlow message type space.This is a staging area for features meant for future OpenFlow revisions.10DO NOT BUILD A SWITCH FROM THIS SPECIFICATION!4.2Connection SetupThe switch must be able to establish the communication at a user-configurable (but otherwisefixed)IP address,using a user-specified port.Traffic to and from the secure channel is not checked against theflow table.Therefore,the switch must identify incoming traffic as local before checking it against theflow table. Future versions of the protocol specification will describe a dynamic controller discovery protocol in which the IP address and port for communicating with the controller is determined at runtime.When an OpenFlow connection isfirst established,each side of the connection must immediately send an OFPT_HELLO message with the versionfield set to the highest OpenFlow protocol version supported by the sender.Upon receipt of this message,the recipient may calculate the OpenFlow protocol version to be used as the smaller of the version number that it sent and the one that it received.If the negotiated version is supported by the recipient,then the connection pro-ceeds.Otherwise,the recipient must reply with an OFPT_ERROR message with a typefield of OFPET_HELLO_FAILED,a codefield of OFPHFC_COMPATIBLE,and optionally an ASCII string explaining the situation in data,and then terminate the connection.4.3Connection InterruptionIn the case that the switch loses contact with the controller,the default behavior must be to do nothing-to letflows timeout naturally.Other behaviors can be implemented via vendor-specific command line interface or vendor extension OpenFlow messages.4.4EncryptionThe switch and controller communicate through an SSL connection.The SSL connection is initiated by the switch on startup to the controllers server,which is located by default on TCP port6633.The switch and controller mutually au-thenticate by exchanging certificates signed by a site-specific private key.Each switch must be user-configurable with one certificate for authenticating the con-troller(controller certificate)and the other for authenticating to the controller (switch certificate).4.5Spanning TreeType0switches may optionally support802.1D Spanning Tree Protocol.Those switches that do support it are expected to process all802.1D packets locally before performingflow lookup.A switch that implements STP must set the OFPC_STP bit in the’capabilities’field of its OFPT_FEATURES_REPLY message.A11DO NOT BUILD A SWITCH FROM THIS SPECIFICATION!switch that implements STP must make it available on all of its physical ports, but it need not implement it on virtual ports(e.g.OFPP_LOCAL).Port status,as specified by the spanning tree protocol,is then used to limit packets forwarded to the OFP_FLOOD port to only those ports along the span-ning tree.Port changes as a result of the spanning tree are sent to the controller via port-update messages.Note that forward actions that specify the outgoing port or OFP_ALL ignore the port status set by the spanning tree protocol. Switches that do not support802.1D spanning tree must allow the controller to specify the port status for packetflooding through the port-mod messages.4.6Flow Table Modification MessagesFlow table modification messages can have the following types:enum ofp_flow_mod_command{OFPFC_ADD,/*New flow.*/OFPFC_MODIFY,/*Modify all matching flows.*/OFPFC_MODIFY_STRICT,/*Modify entry strictly matching wildcards*/OFPFC_DELETE,/*Delete all matching flows.*/OFPFC_DELETE_STRICT/*Strictly match wildcards and priority.*/};For ADD requests with set wildcardfields,the switch mustfirst check for any already-inserted entries that conflict with the incoming entry(i.e.,same prior-ity and there exists an entry that could match both).If a conflict is found,the switch should refuse the addition and may respond with an OFPEFM_ADD_OVERLAP error message.For valid(non-conflicting)ADD requests,the newflow should be added to the lowest numbered table for which the switch supports all wildcards set in the flow_match struct,and for which the priority would be observed during the matching process.If aflow entry with identical headerfields and priority already resides in any table,then that entry,including its counters, must be removed,and the newflow entry added.For MODIFY requests,if aflow entry with identical headerfields does not current reside in any table,the newflow entry must be inserted with zeroed counters.Otherwise,the actionsfield is changed on the existing entry and its counters and idle timefields are left unchanged.For DELETE requests,if noflow entry matches,no error is recorded,and no flow table modification occurs.If a switch cannotfind any table in which to add the incomingflow entry, the switch should send an OFPT_ERROR_MSG with OFPET_FLOW_MOD_FAILED type and OFPFMFC_ALL_TABLES_FULL type.MODIFY and DELETEflow mod commands have corresponding STRICT12DO NOT BUILD A SWITCH FROM THIS SPECIFICATION! versions.Without STRICT appended,the wildcards are active and allflows that match the description are modified or removed.If STRICT is appended, allfields,including the wildcards and priority,are strictly matched against the entry,and only an identicalflow is modified or removed.For example,if a mes-sage to remove entries is sent that has all the wildcardflags set,the DELETE command would delete allflows from all tables,while the DELETE STRICT command would only delete a rule that applies to all packets at the specified priority.DELETE and DELETE STRICT commands can be optionallyfiltered by out-put port.If the out_portfield contains a value other than OFPP_NONE,it intro-duces a constraint when matching.This constraint is that the rule must contain an output action directed at that port.Thisfield is ignored by ADD,MODIFY, and MODIFY STRICT messages.4.7Flow RemovalEachflow entry has an idle_timeout and a hard_timeout associated with it. If no packet has matched the rule in the last idle_timeout seconds,or it has been hard_timeout seconds since theflow was inserted,the switch removes the entry and sends aflow expiration message.In addition,the controller is able to actively remove entries by sending aflow message with the DELETE or DELETE_STRICT command.Like the message used to add the entry,a removal message contains a description,which may include wild cards.5Appendix A:The OpenFlow ProtocolThe heart of the OpenFlow spec is the set of structures used for OpenFlow Protocol messages.The structures,defines,and enumerations described below are derived from thefile include/openflow/openflow.h,which is part of the standard Open-Flow distribution.All structures are packed with padding and8-byte aligned, as checked by the assertion statements.All OpenFlow messages are sent in big-endian format.5.1OpenFlow HeaderEach OpenFlow message begins with the OpenFlow header:/*Header on all OpenFlow packets.*/struct ofp_header{uint8_t version;/*OFP_VERSION.*/uint8_t type;/*One of the OFPT_constants.*/uint16_t length;/*Length including this ofp_header.*/uint32_t xid;/*Transaction id associated with this packet.Replies use the same id as was in the request13DO NOT BUILD A SWITCH FROM THIS SPECIFICATION!to facilitate pairing.*/};OFP_ASSERT(sizeof(struct ofp_header)==8);The version specifies the OpenFlow protocol version being used.During the current draft phase of the OpenFlow Protocol,the most significant bit will be set to indicate an experimental version and the lower bits will indicate a revision number.The current version is0x97.Thefinal version for a Type0switch will be0x00.The lengthfield indicates the total length of the message,so no additional framing is used to distinguish one frame from the next.The type can have the following values:enum ofp_type{/*Immutable messages.*/OFPT_HELLO,/*Symmetric message*/OFPT_ERROR,/*Symmetric message*/OFPT_ECHO_REQUEST,/*Symmetric message*/OFPT_ECHO_REPLY,/*Symmetric message*/OFPT_VENDOR,/*Symmetric message*//*Switch configuration messages.*/OFPT_FEATURES_REQUEST,/*Controller/switch message*/OFPT_FEATURES_REPLY,/*Controller/switch message*/OFPT_GET_CONFIG_REQUEST,/*Controller/switch message*/OFPT_GET_CONFIG_REPLY,/*Controller/switch message*/OFPT_SET_CONFIG,/*Controller/switch message*//*Asynchronous messages.*/OFPT_PACKET_IN,/*Async message*/OFPT_FLOW_EXPIRED,/*Async message*/OFPT_PORT_STATUS,/*Async message*//*Controller command messages.*/OFPT_PACKET_OUT,/*Controller/switch message*/OFPT_FLOW_MOD,/*Controller/switch message*/OFPT_PORT_MOD,/*Controller/switch message*//*Statistics messages.*/OFPT_STATS_REQUEST,/*Controller/switch message*/OFPT_STATS_REPLY/*Controller/switch message*/};5.2Common StructuresThis section describes structures used by multiple messages.5.2.1Port StructuresPhysical ports are described with the following structure:/*Description of a physical port*/struct ofp_phy_port{uint16_t port_no;uint8_t hw_addr[OFP_ETH_ALEN];14DO NOT BUILD A SWITCH FROM THIS SPECIFICATION!uint8_t name[OFP_MAX_PORT_NAME_LEN];/*Null-terminated*/uint32_t config;/*Bitmap of OFPPC_*flags.*/uint32_t state;/*Bitmap of OFPPS_*flags.*//*Bitmaps of OFPPF_*that describe features.All bits zeroed if*unsupported or unavailable.*/uint32_t curr;/*Current features.*/uint32_t advertised;/*Features being advertised by the port.*/uint32_t supported;/*Features supported by the port.*/uint32_t peer;/*Features advertised by peer.*/};OFP_ASSERT(sizeof(struct ofp_phy_port)==48);The port_nofield is a value the datapath associates with a physical port.The hw_addrfield typically is the MAC address for the port;OFP_MAX_ETH_ALEN is 6.The namefield is a null-terminated string containing a human-readable name for the interface.The value of OFP_MAX_PORT_NAME_LEN is16.The configfield describes spanning tree and administrative settings with the following structure:/*Flags to indicate behavior of the physical port.These flags are*used in ofp_phy_port to describe the current configuration.They are*used in the ofp_port_mod message to configure the port’s behavior.*/enum ofp_port_config{OFPPC_PORT_DOWN=1<<0,/*Port is administratively down.*/OFPPC_NO_STP=1<<1,/*Disable802.1D spanning tree on port.*/OFPPC_NO_RECV=1<<2,/*Drop all packets except802.1D spanningtree packets.*/OFPPC_NO_RECV_STP=1<<3,/*Drop received802.1D STP packets.*/OFPPC_NO_FLOOD=1<<4,/*Do not include this port when flooding.*/OFPPC_NO_FWD=1<<5,/*Drop packets forwarded to port.*/OFPPC_NO_PACKET_IN=1<<6/*Do not send packet-in msgs for port.*/};The port config bits indicate whether a port has been administratively brought down,options for handling802.1D spanning tree packets,and how to handle incoming and outgoing packets.These bits,configured over multiple switches, enable an OpenFlow network to safelyflood packets along either a custom or 802.1D spanning tree.The controller may set OFPPFL_NO_STP to0to enable STP on a port or to 1to disable STP on a port.(The latter corresponds to the Disabled STP port state.)The default is switch implementation-defined;the OpenFlow reference implementation by default sets this bit to0(enabling STP).When OFPPFL_NO_STP is0,STP controls the OFPPFL_NO_FLOOD and OFPPFL_STP_* bits directly.OFPPFL_NO_FLOOD is set to0when the STP port state is Forward-ing,otherwise to1.The bits in OFPPFL_STP_MASK are set to one of the other15。