GetConfigReq - GetConfigRes - SetConfig

The sequence of messages is used to query and set the fragmentation handling properties of the packet processing pipeline. Should packets that are fragmented be: matched as-is, dropped, reassembled and matched, etc. Additionally, this message helps determine how much of a packet will be shared with the controller. GetConfigReq is an acknowledged message (GetConfigRes) and is only initiated by the controller. The controller may alter this state with a SetConfig message. SetConfig can only be initiated by the controller, and is unacknowledged.
Initiator
Controller
Acknowledged
GetConfigReq

Structure

A GetConfigReq consists of just the OpenFlow header. The GetConfigRes and SetConfig messages consist of the header followed by two 16 bit fields: flags, and miss_send_length. The flags indicate either which fragment handling operations are active (GetConfigRes) or which operations to use (SetConfig). The miss_send_length field indicates the amount of bytes of a packet to capture for sending with a PacketIn message.

Message Structure

Name Bits Byte Ordering Constraints
flags 16 MSBF See below
miss_send_len 16 MSBF none

Message Constraints

Field Name Value Comments
Flags FRAG_NORMAL 0x0000 Match packets, regardless of state
FRAG_DROP 0x0001 Drop fragmented packets
FRAG_REASM 0x0002 Reassemble fragmented packets
FRAG_MASK 0x0003 Mask for fragmentation

References

OpenFlow Switch Specification 1.0.0, pages 28-29

Structure

A GetConfigReq consists of just the OpenFlow header. The GetConfigRes and SetConfig messages consist of the header followed by two 16 bit fields: flags, and miss_send_length. The flags indicate either which fragment handling operations are active (GetConfigRes) or which operations to use (SetConfig). The miss_send_length field indicates the amount of bytes of a packet to capture for sending with a PacketIn message.

Message Structure

Name Bits Byte Ordering Constraints
flags 16 MSBF See below
miss_send_len 16 MSBF none

Message Constraints

Field Name Value Comments
Flags FragNormal 0x0000 Match packets, regardless of state
FragDrop 0x0001 Drop fragmented packets
FragReasm 0x0002 Reassemble fragmented packets
FragMask 0x0003 Mask for fragmentation
InvalidTTLtoController 0x0004 Drop or forward with PacketIn Message

References

OpenFlow Switch Specification 1.1.0, page 37

Structure

A GetConfigReq consists of just the OpenFlow header. The GetConfigRes and SetConfig messages consist of the header followed by two 16 bit fields: flags, and miss_send_length. The flags indicate either which fragment handling operations are active (GetConfigRes) or which operations to use (SetConfig). The miss_send_length field indicates the amount of bytes of a packet to capture for sending with a PacketIn message. A value of 0xffff indicates that the entire packet is being captured.

Message Structure

Name Bits Byte Ordering Constraints
flags 16 MSBF See below
miss_send_len 16 MSBF none

Message Constraints

Field Name Value Comments
Flags FragNormal 0x0000 Match packets, regardless of state
FragDrop 0x0001 Drop fragmented packets
FragReasm 0x0002 Reassemble fragmented packets
FragMask 0x0003 Mask for fragmentation
InvalidTTLtoController 0x0004 Drop or forward with PacketIn Message

References

OpenFlow Switch Specification 1.2.0, pages 45-46

Structure

A GetConfigReq consists of just the OpenFlow header. The GetConfigRes and SetConfig messages consist of the header followed by two 16 bit fields: flags, and miss_send_length. The flags indicate either which fragment handling operations are active (GetConfigRes) or which operations to use (SetConfig). The miss_send_length field indicates the amount of bytes of a packet to capture for sending with a PacketIn message. A value of 0xffff indicates that the entire packet is being captured.

Message Structure

Name Bits Byte Ordering Constraints
flags 16 MSBF See below
miss_send_len 16 MSBF none

Message Constraints

Field Name Value Comments
Flags FragNormal 0x0000 Match packets, regardless of state
FragDrop 0x0001 Drop fragmented packets
FragReasm 0x0002 Reassemble fragmented packets
FragMask 0x0003 Mask for fragmentation

References

OpenFlow Switch Specification 1.3.0, page 54

Structure

A GetConfigReq consists of just the OpenFlow header. The GetConfigRes and SetConfig messages consist of the header followed by two 16 bit fields: flags, and miss_send_length. The flags indicate either which fragment handling operations are active (GetConfigRes) or which operations to use (SetConfig). The miss_send_length field indicates the amount of bytes of a packet to capture for sending with a PacketIn message. A value of 0xffff indicates that the entire packet is being captured.

Message Structure

Name Bits Byte Ordering Constraints
flags 16 MSBF See below
miss_send_len 16 MSBF none

Message Constraints

Field Name Value Comments
Flags FragNormal 0x0000 Match packets, regardless of state
FragDrop 0x0001 Drop fragmented packets
FragReasm 0x0002 Reassemble fragmented packets
FragMask 0x0003 Mask for fragmentation

References

OpenFlow Switch Specification 1.3.1, page 62

Structure

A GetConfigReq consists of just the OpenFlow header. The GetConfigRes and SetConfig messages consist of the header followed by two 16 bit fields: flags, and miss_send_length. The flags indicate either which fragment handling operations are active (GetConfigRes) or which operations to use (SetConfig). The miss_send_length field indicates the amount of bytes of a packet to capture for sending with a PacketIn message. A value of 0xffff indicates that the entire packet is being captured.

Message Structure

Name Bits Byte Ordering Constraints
flags 16 MSBF See below
miss_send_len 16 MSBF none

Message Constraints

Field Name Value Comments
Flags FragNormal 0x0000 Match packets, regardless of state
FragDrop 0x0001 Drop fragmented packets
FragReasm 0x0002 Reassemble fragmented packets
FragMask 0x0003 Mask for fragmentation

References

OpenFlow Switch Specification 1.3.2, page 64

Structure

A GetConfigReq consists of just the OpenFlow header. The GetConfigRes and SetConfig messages consist of the header followed by two 16 bit fields: flags, and miss_send_length. The flags indicate either which fragment handling operations are active (GetConfigRes) or which operations to use (SetConfig). The miss_send_length field indicates the amount of bytes of a packet to capture for sending with a PacketIn message. A value of 0xffff indicates that the entire packet is being captured.

Message Structure

Name Bits Byte Ordering Constraints
flags 16 MSBF See below
miss_send_len 16 MSBF none

Message Constraints

Field Name Value Comments
Flags FragNormal 0x0000 Match packets, regardless of state
FragDrop 0x0001 Drop fragmented packets
FragReasm 0x0002 Reassemble fragmented packets
FragMask 0x0003 Mask for fragmentation

References

OpenFlow Switch Specification 1.3.3, pages 67-68

Structure

A GetConfigReq consists of just the OpenFlow header. The GetConfigRes and SetConfig messages consist of the header followed by two 16 bit fields: flags, and miss_send_length. The flags indicate either which fragment handling operations are active (GetConfigRes) or which operations to use (SetConfig). The miss_send_length field indicates the amount of bytes of a packet to capture for sending with a PacketIn message. A value of 0xffff indicates that the entire packet is being captured.

Message Structure

Name Bits Byte Ordering Constraints
flags 16 MSBF See below
miss_send_len 16 MSBF none

Message Constraints

Field Name Value Comments
Flags FragNormal 0x0000 Match packets, regardless of state
FragDrop 0x0001 Drop fragmented packets
FragReasm 0x0002 Reassemble fragmented packets
FragMask 0x0003 Mask for fragmentation

References

OpenFlow Switch Specification 1.4.0, pages 70-71