PartialChunkTooShort.seq - Partial Chunk is received with chunk length less than 4-bytes
To check that if partial chunk is received with chunk length less than
4-bytes, the endpoint should drop the chunk.
./PartialChunkTooShort.seq [-tooloption ...] -pkt ./PartialChunkTooShort.def
-tooloption : v6eval tool option
See Also: ../common/STD_PKT_COMMON.def
../common/SCTP_COMMON.def
Association is established between endpoint A and B. Arrange
data in endpoint A such that DATA chunk is sent to endpoint
B with chunk length less than 4-bytes.
Endpoint A Endpoint B ULP
(ESTABLISHED) (ESTABLISHED)
DATA -----------------> Discard DATA
(chunk length less than 4-bytes)
TEST DESCRIPTION:
1. Send DATA message from endpoint A to B with chunk length less than
4-bytes.
Record the message sequence using a signal emulator.
2. Check A: ABORT message is discarded and no other actions are taken.
3. Check B: Was the message sequence as above.
None
RFC 4960
6.10. Bundling
Partial chunks MUST NOT be placed in an SCTP packet. A partial chunk
is a chunk that is not completely contained in the SCTP packet; i.e.,
the SCTP packet is too short to contain all the bytes of the chunk as
indicated by the chunk length.
An endpoint MUST process received chunks in their order in the
packet. The receiver uses the Chunk Length field to determine the
end of a chunk and beginning of the next chunk taking account of the
fact that all chunks end on a 4-byte boundary. If the receiver
detects a partial chunk, it MUST drop the chunk.