Minimum Requirements for Supporting Header-Data Split
This topic summarizes the minimum requirements that a provider must meet to support header-data split. For a complete listing of the rules that apply to splitting Ethernet frames, see Splitting Ethernet Frames.
The following list contains the minimum requirements for header-data split support:
Providers must not split frames that the Cases Where Header-Data Split Is Not Used topic describes.
Providers must move virtual LAN (VLAN) tags to the NET_BUFFER_LIST structure OOB data. For more information about VLAN requirements, see Receive Indications with Header-Data Split.
Providers must support splitting IPv4 frames without options. For more information about splitting IPv4 frames, see Splitting IPv4 Frames.
Providers must support splitting IPv6 frames without extension headers. For more information about splitting IPv6 frames, see Splitting IPv6 Frames.
Providers must support splitting TCP frames at the TCP payload with no TCP options and with only the timestamp option. For more information about splitting TCP frames, see Splitting Frames at the TCP Payload.
Providers must support splitting UDP frames at the UDP payload. For more information about splitting UDP frames, see Splitting Frames at the UDP Payload.
Providers must support the header-data split initialization attributes. For more information about these attributes, see Initializing a Header-Data Split Provider.
Providers must support the header-data split receive indication requirements, including setting the header-data split flags in the NblFlags member of the NET_BUFFER_LIST structures, header size requirements, and data backfill requirements. For more information about receive requirements, see Receive Indications with Header-Data Split.
Providers must support the OID_GEN_HD_SPLIT_PARAMETERS OID, the OID_GEN_HD_SPLIT_CURRENT_CONFIG OID, the NDIS_STATUS_HD_SPLIT_CURRENT_CONFIG status indication, and registry settings. For more information about header-data split parameters and settings, see Header-Data Split Administration and Configuration.
For more information about header-data split requirements for protocol drivers and filter drivers, see Supporting Header-Data Split in Protocol Driver and Filter Drivers.
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for