[DTS/tests Bug 2045] UDP special checksum cases

[bugzilla at dpdk.org]

https://bugs.dpdk.org/show_bug.cgi?id=2045

            Bug ID: 2045
           Summary: UDP special checksum cases
           Product: DTS
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: Normal
         Component: tests
          Assignee: dts at dpdk.org
          Reporter: mb at smartsharesystems.com
  Target Milestone: ---

RFC 768 says:
If the computed  checksum  is zero,  it is transmitted  as all ones (the
equivalent  in one's complement  arithmetic).   An all zero  transmitted
checksum  value means that the transmitter  generated  no checksum  (for
debugging or for higher level protocols that don't care).

RFC 8200 says:
Unlike IPv4, the default behavior when UDP packets are
originated by an IPv6 node is that the UDP checksum is not
optional.  That is, whenever originating a UDP packet, an IPv6
node must compute a UDP checksum over the packet and the
pseudo-header, and, if that computation yields a result of
zero, it must be changed to hex FFFF for placement in the UDP
header.  IPv6 receivers must discard UDP packets containing a
zero checksum and should log the error.

New test cases:
UDP RX Checksum offload (2 tests)
Send an UDP packet to the DUT with zero in the UDP checksum field, and a
payload where the checksum is non-zero. Such a packet should be reported as
"UDP Checksum GOOD" for IPv4 and "UDP Checksum BAD" for IPv6.

UDP TX Checksum offload (2 tests)
With UDP TX Checksum offload enabled in the DUT, build a packet where the
result of the checksum computation is zero, transmit it, and verify that the
UDP checksum is FFFF in the packet received from the DUT. The result should be
the same for both IPv4 and IPv6.

-- 
You are receiving this mail because:
You are the assignee for the bug.