AsconfWithLargeSeq.seq - ASCONF chunk is received with Sequence Number greater than next expected Sequence Number
To chech that if ASCONF chunk is received with Sequence Number greater
than next expected Sequence Number then the endpoint should discarded
the ASCONF Chunk.
./AsconfWithLargeSeq.seq [-tooloption ...] -pkt ./AsconfWithLargeSeq.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 date
in endpoint A such that ASCONF chunk with Sequence Number greater
than next expected Sequence Number is sent to endpoint B.
Endpoint A Endpoint B ULP
(ESTABLISHED) (ESTABLISHED)
ASCONF -----------------> Discard
(duplicate Peer Sequence Number)
TEST DESCRIPTION:
1. Send ASCONF-ACK chunk from endpoint A to B with Sequence Number
greater than next expected Sequence Number.
2. Check A: ASCONF chunk should be discarded at endpoint B and no
ASCONF-ACK chunk can be received at endpoint A.
None
RFC 5061
5.2. Upon Reception of an ASCONF Chunk
After identification and verification of the association, the
following should be performed to properly process the ASCONF Chunk:
E5) Otherwise, the ASCONF Chunk is discarded since it must be either
a stale packet or from an attacker. A receiver of such a packet
MAY log the event for security purposes.
E6) When all ASCONF Chunks are processed for this SCTP packet, send
back the accumulated single response packet with all of the
ASCONF-ACK Chunks. The destination address of the SCTP packet
containing the ASCONF-ACK Chunks MUST be the source address of
the SCTP packet that held the ASCONF Chunks.