BundledAsconfAckChunks.seq - ASCONF-ACK chunk is received bundled with other ASCONF-ACK chunk
To check that if ASCONF-ACK chunk is received bundled with other ASCONF-ACK
chunk then the endpoint should process the next ASCONF-ACK chunk after
processing the first ASCONF-ACK chunk.
./BundledAsconfAckChunks.seq [-tooloption ...] -pkt ./BundledAsconfAckChunks.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 B such that ASCONF chunk with Add IP Address Parameter
is sent to endpoint A.
Endpoint A Endpoint B ULP
(ESTABLISHED) (ESTABLISHED)
<----- Asconf
<----------------- ASCONF
ASCONF-ACK ----------------->
(Bunding with illegal ASCONF-ACK)
<----------------- ABORT
TEST DESCRIPTION:
1. Sending ASCONF message with Delete IP Address Parameter from
endpoint B to A.
Record the message sequence using a signal emulator.
2. Send ASCONF-ACK message bundled with illegal ASCONF-ACK from
endpoint A to B.
3. Check A: Endpoint B process the next ASCONF-ACK chunk after
processing the first ASCONF-ACK chunk and ABORT chunk should
be received to response the illegal ASCONF-ACK chunk at
endpoint A.
None
RFC 5061
5.1.1. Congestion Control of ASCONF Chunks
In defining the ASCONF Chunk transfer procedures, it is essential
that these transfers MUST NOT cause congestion within the network.
To achieve this, we place these restrictions on the transfer of
ASCONF Chunks:
C2) An ASCONF Chunk may be bundled with any other chunk type
including other ASCONF Chunks. If bundled with other ASCONF
Chunks, the chunks MUST appear in sequential order with respect
to their Sequence Number.
C3) An ASCONF-ACK Chunk may be bundled with any other chunk type
including other ASCONF-ACK Chunks. If bundled with other
ASCONF-ACK Chunks, the chunks MUST appear in sequential order
with respect to their Sequence Number.