GEN_RestartWithNewAddr.seq - Generation of error cause Restart of an Association with New Addresses
To check that if a INIT chunk is sent with new address parameter
then endpoint should response with an ABORT message with cause
Restart of an Association with New Addresses.
./GEN_RestartWithNewAddr.seq [-tooloption ...] -pkt ./GEN_RestartWithNewAddr.def
-tooloption : v6eval tool option
See Also: ../common/STD_PKT_COMMON.def
../common/SCTP_COMMON.def
Association is not established between endpoint A and B. Arrange
data in endpoint A such that INIT chunk with new address parameter
is sent to endpoint B.
Endpoint A Endpoint B ULP
(ESTABLISHED) (ESTABLISHED)
INIT ----------------->
(with New Addresses)
<----------------- ABORT
(Restart of an Association with New Addresses)
TEST DESCRIPTION:
1. Send INIT chunk from endpoint A to B with new address
parameter.
2. Check A: ABORT should be received at endpoint A.
3. Check B: Error cause in ABORT is set to "Restart of an
Association with New Addresses".
None
RFC 4960
3.3.10.11. Restart of an Association with New Addresses (11)
Cause of error
--------------
Restart of an association with new addresses: An INIT was received on
an existing association. But the INIT added addresses to the
association that were previously NOT part of the association. The
new addresses are listed in the error code. This ERROR is normally
sent as part of an ABORT refusing the INIT (see Section 5.2).
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=11 | Cause Length=Variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ New Address TLVs /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note: Each New Address TLV is an exact copy of the TLV that was found
in the INIT chunk that was new, including the Parameter Type and the
Parameter Length.