ChunkTypeAction11.seq - Unrecognized Chunk Type with higher two bytes are set to 11
To check that if Unrecognized Chunk Type is received with higher two bytes
are set to 11, the endpoint should skip this chunk and continue processing,
but report in an ERROR chunk using the 'Unrecognized Chunk Type' cause of
error.
./ChunkTypeAction11.seq [-tooloption ...] -pkt ./ChunkTypeAction11.def
-tooloption : v6eval tool option
See Also: ../common/STD_PKT_COMMON.def
../common/SCTP_COMMON.def
Association is not established between endpoint A and B. Arrange the data
in endpoint A such that a datagram with reserved chunk type is sent to
endpoint B bundled with DATA chunk in any state and higher two bytes are
set to 11.
Endpoint A Endpoint B ULP
(ESTABLISHED) (ESTABLISHED)
Chunk Type FF ----------------->
(bundled with DATA)
<------------------ ERROR
(Unrecognized Chunk Type)
<------------------ SACK
TEST DESCRIPTION:
1. Send SCTP message from endpoint A to B with higher two bytes
are set to 11, which is bundled with DATA chunk.
Record the message sequence using a signal emulator.
2. Check A: Datgram with reserved chunk type is discarded and ERROR is
also received at endpoint A with cause "Unrecognized Chunk type".
3. Check B: SACK is also received at endpoint A for the DATA chunk.
4. Check C: Association is not disturbed.
None
RFC 4960
3.2. Chunk Field Descriptions
Chunk Types are encoded such that the highest-order 2 bits specify
the action that must be taken if the processing endpoint does not
recognize the Chunk Type.
00 - Stop processing this SCTP packet and discard it, do not
process any further chunks within it.
01 - Stop processing this SCTP packet and discard it, do not
process any further chunks within it, and report the
unrecognized chunk in an 'Unrecognized Chunk Type'.
10 - Skip this chunk and continue processing.
11 - Skip this chunk and continue processing, but report in an
ERROR chunk using the 'Unrecognized Chunk Type' cause of
error.