BundledAsconfAckAndOther.seq - ASCONF-ACK chunk is received bundled with other chunk as the first chunk
To check that if ASCONF-ACK chunk is received bundled with other chunk as the
first chunk then the endpoint should accept both of the messages.
./BundledAsconfAckAndOther.seq [-tooloption ...] -pkt ./BundledAsconfAckAndOther.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 DATA)
<----------------- SACK
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 DATA chunk as the first
chunk from endpoint A to B.
3. Check A: Endpoint B should consider the address part of the
existing association and SACK chunk should be received to
response the DATA 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.