AsconfAckWithSmallSeq.seq - ASCONF-ACK chunk is received with less than next Sequence Number but no ASCONF Chunk is outstanding
To check that if ASCONF-ACK chunk is received with Sequence Number
less than next Sequence Number but no ASCONF Chunk is outstanding
then the endpoint discard the ASCONF-ACK chunk.
./AsconfAckWithSmallSeq.seq [-tooloption ...] -pkt ./AsconfAckWithSmallSeq.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 the date
in endpoint A such that ASCONF-ACK chunk with Sequence Number less than
the next Sequence Number is sent to endpoint B.
Endpoint A Endpoint B ULP
(ESTABLISHED) (ESTABLISHED)
ASCONF-ACK -----------------> Discard
(Sequence Number equal to next Sequence Number)
TEST DESCRIPTION:
1. Send ASCONF-ACK chunk from endpoint A to B with Sequence Number
equal to next Sequence Number.
2. Check A: ASCONF-ACK chunk should be discarded at endpoint B.
None
RFC 5061
4.3.4. Error Cause: Association Aborted Due to Illegal ASCONF-ACK
This error is to be included in an ABORT that is generated due to the
reception of an ASCONF-ACK that was not expected but is larger than
the current Sequence Number (see Section 5.3, Rule F0 ). Note that a
Sequence Number is larger than the last acked Sequence Number if it
is either the next sequence or no more than 2**31-1 greater than the
current Sequence Number. Sequence Numbers smaller than the last
acked Sequence Number are silently ignored.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cause Code=0x00A3 | Cause Length=4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+