AsconfDupNoCached.seq - ASCONF chunk is received with duplicate Peer Sequence Number but no cached ASCONF-ACK is outstanding
To chech that if ASCONF chunk is received with duplicate Peer Sequence
Number and not cached ASCONF-ACK response exists then the endpoint should
skip the ASCONF Chunk and not include ASCONF-ACK Chunk for that chunk.
./AsconfDupNoCached.seq [-tooloption ...] -pkt ./AsconfDupNoCached.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 duplicate Peer 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 duplicate Peer
Sequence Number but no cached ASCONF-ACK is outstanding.
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:
E2) If the value found in the Sequence Number is less than the
('Peer- Sequence-Number' + 1), simply skip to the next ASCONF,
and include in the outbound response packet any previously
cached ASCONF-ACK response that was sent and saved that matches
the Sequence Number of the ASCONF. Note: It is possible that no
cached ASCONF-ACK Chunk exists. This will occur when an older
ASCONF arrives out of order. In such a case, the receiver
should skip the ASCONF Chunk and not include ASCONF-ACK Chunk
for that chunk.