The closest comparison to a flow table might be access list or rout map. It is a list of one or more entries, and each entry has a match condition, action to take on any packets that match, and possibly an accounting function to count how many matches have occurred.
OpenFlow match structures are built using a Type/Length/Value (TLV) format, which makes changing or expanding match parameters between versions much easier.
OpenFlow match conditions fall into one of three categories:
OpenFlow match structures are built using a Type/Length/Value (TLV) format, which makes changing or expanding match parameters between versions much easier.
OpenFlow match conditions fall into one of three categories:
- Flow Match
- Header Match
- Pipeline Match
- Experimenter Flow Match
Flow Match
A flow is usually identified by a combination of parameters such as incoming port, L2 and L3 source and destination address, Class of Service bits, and upper layer ports.
Header Match
In addition to flows, a flow entry can match specific packets based on the contents of its Layer 2, 3, and 4 header. Header Match fields is almost the same list as Flow Match. But, the difference is packet-independent parameters such as ingress port, metedata, or tunnel IDs
Pipeline Match
Pipeline match fields are the information attached to a packet, other than the packet header, for pipline processing.
Experimenter Flow Match
Experimenter Flow Match is an optional category that, as you might guess, support experimentation.
No comments:
Post a Comment