InitBadSuppAddrType.seq - INIT chunk is received with Supported Address Type which the receiver is incapable of using
To check that if INIT chunk is received with Supported Address Type which
the receiver is incapable of using then the endpoint should acceptable
the address type which is indicated in Supported Address Types parameter.
./InitBadSuppAddrType.seq [-tooloption ...] -pkt ./InitBadSuppAddrType.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 the
data in endpoint A such that INIT chunk with Supported Address Field
containing Bad Address type is sent in to endpoint B.
Endpoint A Endpoint B ULP
(CLOSED) (CLOSED)
INIT ----------------->
(with Bad Supported Address Field)
<----------------- INIT-ACK
COOKIE-ECHO ----------------->
<----------------- COOKIE-ACK
TEST DESCRIPTION:
1. Attempt to make an association from endpoint A to B. Send INIT
message with Bad Supported Address field.
Record the message sequence using a signal emulator.
2. Check A: Association is established between endpoint A and B.
None
RFC 4960
5.1.2. Handle Address Parameters
The sender of INIT may include a 'Supported Address Types' parameter
in the INIT to indicate what types of address are acceptable. When
this parameter is present, the receiver of INIT (initiate) MUST
either use one of the address types indicated in the Supported
Address Types parameter when responding to the INIT, or abort the
association with an "Unresolvable Address" error cause if it is
unwilling or incapable of using any of the address types indicated by
its peer.