- Can the IUT interpret a bad option and a good option? - Action: Send a datagram to the IP Implementation Under Test whose option field contains a security option with an invalid security level and a stream ID option. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2040 " or "ICMP PARAMETER PROBLEM id=02040". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2040 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2041 bad security option plus good stream identification option - Can the IUT interpret a bad option and a good option? - Action: Send a datagram to the IP Implementation Under Test whose option field contains a security option with an invalid option length and a stream ID option. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2041 " or "ICMP PARAMETER PROBLEM id=02041". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2041 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2042 ordinary datagram after bad stream ID option tests - Can the IUT send a datagram after processing nastygrams? - Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 2042 " in its 13-byte data field. Success: A reply datagram containing "ident = 2042 ". Failure: Any response other than the display of the requested reply datagram. The actual failure probably occurred during tests 2028-2041. Test 2043 truncated record route option - Can the IUT interpret a truncated record route option? - Action: Send a datagram to the IP Implementation Under Test with an 8-byte option field. The first two bytes are no operation options followed by a truncated record route option. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. -The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2043" or "ICMP PARAMETER PROBLEM id=02043". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2043 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2044 record route option length bumped by 1 - Can the IUT interpret a defective option length? - Action: Send a datagram to the IP Implementation Under Test with an 8-byte option field. The first byte is a no operation option. This is followed by a record route option whose option length has been bumped by 1. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2044 " or "ICMP PARAMETER PROBLEM id=02044". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2044 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2045 record route option one byte too long - Can the IUT interpret a defective option? - Action: Send a datagram to the IP Implementation Under Test with an 8-byte option field. This consists of a record route option that is one byte too long. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2045 "' or "ICMP PARAMETER PROBLEM id=02045". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2045 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2046 record route option one byte too short - Can the IUT interpret a defective option? - Action: Send a datagram to the IP Implementation Under Test with an 8-byte option field. This consists of a record route option that is one byte too short followed by an an end of option list option and one byte of padding. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2046 " or "ICMP PARAMETER PROBLEM id=02046". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2046 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2047 record route option length of 0 - Can the IUT interpret a defective option length? - Action: Send a datagram to the IP Implementation Under Test with an 8-byte option field. This contains a record route option with an option length of 0. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2047 " or "ICMP PARAMETER PROBLEM id=02047". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2047 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2048 record route option length of 377 octal - Can the IUT interpret a defective option length? - Action: Send a datagram to the IP Implementation Under Test with an option field. This contains a record route option with an option length of 377 octal. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2048 " or "ICMP PARAMETER PROBLEM id=02048". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2048 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2049 record route option length of 353 octal - Can the IUT interpret a defective option length? - Action: Send a datagram to the IP Implementation Under Test with an option field. This contains a record route option with an option length of 353 octal. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2049 or "ICMP PARAMETER PROBLEM id=02049". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2049 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2050 record route option length of 177 octal - Can the IUT interpret a defective option length? - Action: Send a datagram to the IP Implementation Under Test with an option field. This contains a record route option with an option length of 177 octal. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2050" or "ICMP PARAMETER PROBLEM id=02050". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2050 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2051 record route option length of 200 octal - Can the IUT interpret a defective option length? - Action: Send a datagram to the IP Implementation Under Test with an option field. This contains a record route option with an option length of 200 octal. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2051 "' or "ICMP PARAMETER PROBLEM id=02051". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2051 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2052 record route option length of 207 octal - Can the IUT interpret a defective option length? - Action: Send a datagram to the IP Implementation Under Test with an option field. This contains a record route option with an option length of 207 octal (sign bit set). The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2052 "' or "ICMP PARAMETER PROBLEM id=02052". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2052 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2053 record route option pointer bumped by 1 - Can the IUT interpret a defective option pointer? - Action: Send a datagram to the IP Implementation Under Test with an option field. This contains a record route option with an option pointer that is one more than it should be. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2053 " or "ICMP PARAMETER PROBLEM id=02053". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2053 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2054 record route option pointer one short - Can the IUT interpret a defective option pointer? - Action: Send a datagram to the IP Implementation Under Test with an option field. This contains a record route option with an option pointer that is one less than it should be. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2054 " or "ICMP PARAMETER PROBLEM id=02054". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2054 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2055 record route option pointer of 300 octal - Can the IUT interpret a defective option pointer? - Action: Send a datagram to the IP Implementation Under Test with an option field. This contains a record route option with an option pointer of 300 octal. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2055 "' or "ICMP PARAMETER PROBLEM id=02055". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2055 ", or nothing. Failure: An IP Tester display of a datagram other than sn ICMP Parameter Problem message or reply datagram. Test 2056 record route option pointer of 174 octal . - Can the IUT interpret a defective option pointer? - Action: Send a datagram to the IP Implementation Under Test with an option field. This contains a record route option with an option pointer of 174 octal. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2056 " or "ICMP PARAMETER PROBLEM id=02056". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2056 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2057 record route option with bad option length and option pointer - Can the IUT interpret a defective record route option? - Action: Send a datagram to the IP Implementation Under Test with an 8-byte option field. This contains a record route option whose option length and option pointer have been bumped by 12. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2057 " or "ICMP PARAMETER PROBLEM id=02057". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2057 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2058 record route option with bad option pointer - Can the IUT interpret a defective option? - Action: Send a datagram to the IP Implementation Under Test with an option field. This contains a record route option with an option pointer that just exceeds its maximum legal value. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2058 " or "ICMP PARAMETER PROBLEM id=02058". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2058 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2059 record route option with bad option pointer - Can the IUT interpret a defective option? - Action: Send a datagram to the IP Implementation Under Test with-an option field. This contains a two address field record route option with an option pointer that just exceeds its maximum legal value. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2059 " or "ICMP PARAMETER PROBLEM id=02059". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2059 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2060 record route option duplicated - Can the IUT interpret a duplicated record route option? - Action: Send a datagram to the IP Implementation Under Test whose option field contains two identical record route options. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2060 " or "ICMP PARAMETER PROBLEM id=02060". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2060 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2061 two record route options - Can the IUT interpret two options of the same type? - Action: Send a datagram to the IP Implementation Under Test whose option field contains two different record route options. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2061 " or "ICMP PARAMETER PROBLEM id=02061". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2061 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2062 ordinary datagram after bad record route option tests - Can the IUT send a datagram after processing nastygrams? - Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 2062 " in its 13-byte data field. Success: A reply datagram containing "ident = 2062 ". Failure: Any response other than the display of the requested reply datagram. The actual failure probably occurred during tests 2043-2061. Test 2063 truncated timestamp option - Can the IUT interpret a truncated timestamp option? - Action: Send a datagram to the IP Implementation Under Test with an 8-byte option field. The first byte is a no operation option followed by a truncated timestamp option. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2063 " or "ICMP PARAMETER PROBLEM id=02063". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2063 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2064 timestamp option length bumped by 1 - Can the IUT interpret a defective option length? - Action: Send a datagram to the IP Implementation Under Test with an 8-byte option field consisting of a timestamp option whose option length has been bumped by 1. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2064 " or "ICMP PARAMETER PROBLEM id=02064". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2064 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2065 timestamp option one byte too long - Can the IUT interpret a defective option? - Action: Send a datagram to the IP Implementation Under Test with a 12-byte option field. This contains a timestamp option that is one byte too long. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2065 " or "ICMP PARAMETER PROBLEM id=02065". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2065 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP-Parameter Problem message or reply datagram. Test 2066 timestamp option one byte too short - Can the IUT interpret a defective option? - Action: Send a datagram to the IP Implementation Under Test with an 8-byte option field. This consists of a timestamp option that is one byte too short followed by an an end of option list option. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2066 " or "ICMP PARAMETER PROBLEM id=02066". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2066 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2067 timestamp option length of 0 - Can the IUT interpret a defective option length? - Action: Send a datagram to the IP Implementation Under Test with an 8-byte option field. This contains a timestamp option with an option length of 0. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2067 " or "ICMP PARAMETER PROBLEM id=02067". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2067 ", or nothing. Failure: An IP Tester display of a datagram other thsn an ICMP Parameter Problem message or reply datagram. Test 2068 timestamp option length of 374 octal - Can the IUT interpret a defective option length? - Action: Send a datagram to the IP Implementation Under Test with an option field. This contains a timestamp option with an option length of 374 octal. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2068 " or "ICMP PARAMETER PROBLEM id=02068". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2068 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2069 timestamp option length of 354 octal - Can the IUT interpret a defective option length? - Action: Send a datagram to the IP Implementation Under Test with an option field. This contains a timestamp option with an option length of 354 octal. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2069 " or "ICMP PARAMETER PROBLEM id=02069". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2069 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2070 timestamp option length of 174 octal - Can the IUT interpret a defective option length? - Action: Send a datagram to the IP Implementation Under Test with an option field. This contains a timestamp option with an option length of 174 octal. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2070 " or "ICMP PARAMETER PROBLEM id=02070". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2070 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2071 timestamp option length of 200 octal - Can the IUT interpret a defective option length? - Action: Send a datagram to the IP Implementation Under Test with an option field. This contains a timestamp option with an option length of 200 octal. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2071 " or "ICMP PARAMETER PROBLEM id=02071". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2071 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2072 timestamp option length of 210 octal - Can the IUT interpret a defective option length? - Action: Send a datagram to the IP Implementation Under Test with an option field. This contains a timestamp option with an option length of 210 octal (sign bit set). The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2072 "' or "ICMP PARAMETER PROBLEM id=02072". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2072 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2073 timestamp option pointer bumped by 1 - Can the IUT interpret a defective option pointer? - Action: Send a datagram to the IP Implementation Under Test with an option field. This contains a timestamp option with an option pointer that is one more than it should be. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2073 " or "ICMP PARAMETER PROBLEM id=02073". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2073 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2074 timestamp option pointer one short - Can the IUT interpret a defective option pointer? - Action: Send a datagram to the IP Implementation Under Test with an option field. This contains a timestamp option with an option pointer that is one less than it should be. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2074 " or "ICMP PARAMETER PROBLEM id=02074". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2074 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2075 timestamp option pointer of 301 octal - Can the IUT interpret a defective option pointer? - Action: Send a datagram to the IP Implementation Under Test with an option field. This contains a timestamp option with an option pointer of 301 octal. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2075 " or "ICMP PARAMETER PROBLEM id=02075". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2075 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2076 timestamp option pointer of 175 octal - Can the IUT interpret a defective option pointer? - Action: Send a datagram to the IP Implementation Under Test with an option field. This contains a timestamp option with an option pointer of 175 octal. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2076 " or "ICMP PARAMETER PROBLEM id=02076". Success: An ICMP Parameter Problem message, a reply datagram containing "ident= 2076 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2077 timestamp option with bad option length and option pointer - Can the IUT interpret a defective timestamp option? - Action: Send a datagram to the IP Implementation Under Test with an 8-byte option field. This contains a timestamp option whose option length and option pointer have been bumped by 12. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2077 " or "ICMP PARAMETER PROBLEM id=02077". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2077 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2078 timestamp option with bad option pointer - Can the IUT interpret a defective option? - Action: Send a datagram to the IP Implementation Under Test with an option field. This contains a timestamp option with an option pointer that just exceeds its maximum legal value. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2078 " or "ICMP PARAMETER PROBLEM id=02078". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2078 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2079 timestamp option with bad option pointer - Can the IUT interpret a defective option? - Action: Send a datagram to the IP Implementation Under Test with -an option field. This contains a two address field timestamp option with an option pointer that just exceeds its maximum legal value. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2079 " or "ICMP PARAMETER PROBLEM id=02079". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2079 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2080 timestamp option duplicated - Can the IUT interpret a duplicated timestamp option? - Action: Send a datagram to the IP Implementation Under Test whose option field contains two identical timestamp options. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2080" or "ICMP PARAMETER PROBLEM id=02080". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2080 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2081 two timestamp options - Can the IUT interpret two options of the same type? - Action: Send a datagram to the IP Implementation Under Test whose option field contains two different timestamp options. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2081 " or "ICMP PARAMETER PROBLEM id=02081". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2081 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2082 timestamp option with bad timestamp option format - Can the IUT interpret a defective option? - Action: Send a datagram to the IP Implementation Under Test with an option field. This contains a timestamp option with an illegal format value. The IUT may discard the datagram amd send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2082 " or "ICMP PARAMETER PROBLEM id=02082". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2082 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2083 truncated timestamp option - Can the IUT interpret a truncated timestamp option? - Action: Send a datagram to the IP Implementation Under Test with a 12-byte option field. The first byte is a no operation option followed by a truncated timestamp and address timestamp option. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2083 " or "ICMP PARAMETER PROBLEM id=02083". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2083 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2084 timestamp option length bumped by 1 - Can the IUT interpret a defective option length? - Action: Send a datagram to the IP Implementation Under Test with a 12-byte option field consisting of a prespecified timestamp option whose option length has been bumped by 1. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2084 " or "ICMP PARAMETER PROBLEM id=02084". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2084 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2085 timestamp option one byte too long - Can the IUT interpret a defective option? - Action: Send a datagram to the IP Implementation Under Test with a 16-byte option field. This contains a timestamp and address timestamp option that is one byte too long. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2085 " or "ICMP PARAMETER PROBLEM id=02085". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2085 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2086 timestamp option four bytes too short - Can the IUT interpret a defective option? - Action: Send a datagram to the IP Implementation Under Test with a 16-byte option field. This consists of a prespecified timestamp option that is 4 bytes too short. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2086 " or "ICMP PARAMETER PROBLEM id=02086". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2086 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2087 timestamp option four bytes too short - Can the IUT interpret a defective option? - Action: Send a datagram to the IP Implementation Under Test with a 16-byte option field. This consists of a timestamp and address timestamp option that is 4 bytes too short. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2087 " or "ICMP PARAMETER PROBLEM id=02087". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2087 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2088 timestamp option length of 374 octal - Can the IUT interpret a defective option length? - Action: Send a datagram to the IP Implementation Under Test with an option field. This contains a prespecified timestamp option with an option length of 374 octal. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2088 " or "ICMP PARAMETER PROBLEM id=02088". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2088 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2089 timestamp option length of 354 octal - Can the IUT interpret a defective option length? - Action: Send a datagram to the IP Implementation Under Test with an option field. This contains a timestamp and address timestamp option with an option length of 354 octal. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2089 " or "ICMP PARAMETER PROBLEM id=02089". Success: An ICMP Parameter Problem message, a reply datagram containing "ide-nt = 2089 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2090 timestamp option length of 174 octal - Can the IUT interpret a defective option length? - Action: Send a datagram to the IP Implementation Under Test with an option field. This contains a prespecified timestamp. option with an option length of 174 octal. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2090 " or "ICMP PARAMETER PROBLEM id=02090". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2090 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2091 timestamp option length of 200 octal - Can the IUT interpret a defective option length? - Action: Send a datagram to the IP Implementation Under Test with an option field. This contains a timestamp and address timestamp option with an option length of 200 octal. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2091 " or "ICMP PARAMETER PROBLEM id=02091". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2091 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2092 timestamp option length of 214 octal - Can the IUT interpret a defective option length? - Action: Send a datagram to the IP Implementation Under Test with an option field. This contains a prespecified timestamp option with an option length of 214 octal (sign bit set). The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2092 " or "ICMP PARAMETER PROBLEM id=02092". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2092 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2093 timestamp option pointer bumped by 4 - Can the IUT interpret a defective option pointer? - Action: Send a datagram to the IP Implementation Under Test with an option field. This contains a timestamp and address timestamp option with an option pointer that is four more than it should be. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagrsm required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2093" or "ICMP PARAMETER PROBLEM id=02093". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2093 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2094 timestamp option pointer four short - Can the IUT interpret a defective option pointer? - Action: Send a datagram to the IP Implementation Under Test with an option field. This contains a prespecified timestamp option with an option pointer that is four less than it should be. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2094" or "ICMP PARAMETER PROBLEM id=02094". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2094 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2095 timestamp option pointer of 305 octal - Can the IUT interpret a defective option pointer? - Action: Send a datagram to the IP Implementation Under Test with an option field. This contains a timestamp and address timestamp option with an option pointer of 305 octal. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2095 " or "ICMP PARAMETER PROBLEM id=02095". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2095 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2096 timestamp option pointer of 175 octal - Can the IUT interpret a defective option pointer? - Action: Send a datagram to the IP Implementstion Under Test with an option field. This contains a prespecified timestamp option with an option pointer of 175 octal. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2096 " or "ICMP PARAMETER PROBLEM id=02096". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2096 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2097 timestamp option with bad option length and option pointer - Can the IUT interpret a defective timestamp option? - Action: Send a datagram to the IP Implementation Under Test with a 12-byte option field. This contains a timestamp and address timestamp option whose option length and option pointer have been bumped by 16. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2097" or "ICMP PARAMETER PROBLEM id=02097". Success: An ICMP Parameter Problem message, a reply datagram containing "ident = 2097 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2098 timestamp option with bad option pointer - Can the IUT interpret a defective option? - Action: Send a datagram to the IP Implementation Under Test with an option field. This contains a prespecified timestamp option with an option pointer that just exceeds its maximum legal value. The IUT may discard the datagram and send an optional ICMP Parameter Problem message. The IUT may pass the datagram to its Remote Driver instead. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: If there is a datagram displayed by the IP Tester, its display ought to contain either "ident = 2098" or "ICMP PARAMETER PROBLEM id=02098". Success: An ICMP Parameter Problem message, a reply datagrsm containing "ident = 2098 ", or nothing. Failure: An IP Tester display of a datagram other than an ICMP Parameter Problem message or reply datagram. Test 2099 ordinary datagram after bad timestamp option tests - Can the IUT send a datagram after processing nastygrams? - Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 2099 " in its 13-byte data field. Success: A reply datagram containing "ident =2099 ". Failure: Any response other than the display of the requested reply datagram. The actual failure probably occurred during tests 2063-2098. Scenario File OptBdTopTest: "Top-down Bad Option Field" datagrams 4000 security option without copy bit set 4001 loose source and record route option without copy bit set 4002 timestamp option without bit 6 set 4003 stream ID option without copy bit set 4004 strict source and record route option without copy bit set 4005 "option" with option type of 77 octal 4006 "option" with option type of 101 octal 4007 "option" with option type of 177 octal 4008 record route option with copy bit set 4009 prespecified timestamp option with copy bit set 4010 end of options list option with copy bit set 4011 no operation option with copy bit set 4012 ordinary datagram after bad option type tests 4013 truncated security option 4014 security option length bumped by 1 4015 security option one byte too long 4016 security option one byte too short 4017 security option length of 0 4018 security option length of 377 octal 4019 security option length of 353 octal 4020 security option length of 177 octal 4021 security option length of 200 octal 4022 security option length of 213 octal 4023 security option duplicated 4024 two security options (unclassified, secret) 4025 two security options (secret, unclassified) 4026 security option with an invalid security level 4027 ordinary datagram after bad security option tests 4028 truncated stream identification option 4029 stream identification option length bumped by 1 4030 stream identification option one byte too long 4031 stream identification option one byte too short 4032 stream identification option length of 0 4033 stream identification option length of 377 octal 4034 stream identification option length of 354 octal 4035 stream identification option length of 177 octal 4036 stream identification option length of 200 octal 4037 stream identification option length of 204 octal 4038 stream identification option duplicated 4039 two different stream identification options 4040 bad security level + good stream identification option 4041 bad security length + good stream identification option 4042 ordinary datagram after bad stream ID option tests 4043 truncated record route option 4044 record route option length bumped by 1 4045 record route option one byte too long 4046 record route option one byte too short 4047 record route option length of 0 4048 record route option length of 377 octal 4049 record route option length of 353 octal 4050 record route option length of 177 octal 4051 record route option length of 200 octal 4052 record route option length of 207 octal 4053 record route option pointer bumped by 1 4054 record route option pointer one short 4055 record route option pointer of 300 octal 4056 record route option pointer of 174 octal 4057 record route option pointer with bad option length and option pointer 4058 record route option with bad option pointer 4059 larger record route option with bad option pointer 4060 record route option duplicated 4061 two different record route options 4062 ordinary datagram after bad record route option tests 4063 truncated timestamp option 4064 timestamp option length bumped by 1 4065 timestamp option one byte too long 4066 timestamp option one byte too short 4067 timestamp option length of 0 4068 timestamp option length of 374 octal 4069 timestamp option length of 354 octal 4070 timestamp option length of 174 octal 4071 timestamp option length of 200 octal 4072 timestamp option length of 210 octal 4073 timestamp option pointer bumped by 1 4074 timestamp option pointer one short 4075 timestamp option pointer of 301 octal 4076 timestamp option pointer of 175 octal 4077 timestamp option pointer with bad option length and option pointer 4078 timestamp option with bad option pointer 4079 larger timestamp option with bad option pointer 4080 timestamp option duplicated 4081 two different timestamp options 4082 timestamp option with bad timestamp option format 4083 truncated timestamp option 4084 timestamp option length bumped by 1 4085 timestamp option one byte too long 4086 timestamp option four bytes too short 4087 timestamp option four bytes too short 4088 timestamp option length of 374 octal 4089 timestamp option length of 354 octal 4090 timestamp option length of 174 octal 4091 timestamp option length of 200 octal 4092 timestamp option length of 214 octal 4093 timestamp option pointer bumped by 4 4094 timestamp option pointer four short 4095 timestamp option pointer of 305 octal 4096 timestamp option pointer of 175 octal 4097 timestamp option pointer with bad option length and option pointer 4098 timestamp option with bad option pointer 4099 ordinary datagram after bad timestamp option tests Test 4000 security option without copy bit set - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 12-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid security option without the copy bit set. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4000 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4001 loose source and record route option without copy bit set - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid loose source and record route option without the copy bit set. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4001 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4002 timestamp option without bit 6 set - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver-should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid timestamp option without bit 6 set. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4002 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4003 stream ID option without copy bit set - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 4-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid stream ID option without the copy bit set. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4003 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4004 strict source and record route option without copy bit set - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with s 12-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid strict source and record route option without the copy bit set. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4004 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4005 "option" with option type of 77 octal - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 4-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid "option" with an option type of 77 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4005 error" in its 181- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4006 "option" with option type of 101 octal - Can She IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 4-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid "option" with an option type of 101 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4006 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4007 "option" with option type of 177 octal - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 4-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid "option" with an option type of 177 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4007 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4008 record route option with copy bit set - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 12-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid record route option with the copy bit set. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4008 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4009 prespecified timestamp option with copy bit set - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 12-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid prespecified timestamp option with the copy bit set. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4009 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4010 end of options list option with copy bit set - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 4-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid end of options list option with the copy bit set. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4010 error" in its 181 byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4011 no operation option with copy bit set - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 4-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid no operation option with the copy bit set. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4011 error" in its 181 byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4012 ordinary datagram after bad option type tests - Can the IUT send a datagram after processing nastygrams? - Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 4012 " in its 13-byte data field. Success: A reply datagram containing "ident = 4012 ". Failure: Any response other than the display of the requested reply datagram. The actual failure probably occurred during tests 4000-4011. Test 4013 truncated security option - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 12-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. The first two bytes of the option field requested to be sent are no operation options. They are followed by a truncated security option. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4013 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4014 security option length bumped by 1 - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 12-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid unclassified security option whose option length has been bumped by 1. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4014 error" in its 181 byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4015 security option one byte too long - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 12-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid unclassified security option that is one byte too long. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4015 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4016 security option one byte too short - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 12-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid unclassified security option that is one byte too short. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4016 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4017 security option length of 0 - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 12-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid unclassified security option whose option length has been set to 0. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4017 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4018 security option length of 377 octal - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 12-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid unclassified security option whose option length has been set to 377 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4018 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4019 security option length of 353 octal - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 12-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid unclassified security option whose option length has been set to 353 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4019 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4020 security option length of 177 octal 1 Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 12-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid unclassified security option whose option length has been set to 177 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4020 error" in its 181 byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4021 security option length of 200 octal - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 12-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid unclassified security option whose option length has been set to 200 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4021 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4022 security option length of 213 octal - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 12-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid unclassified security option whose option length has been set to 213 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4022 error" in its 181 byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4023 security option duplicated - Can the IUT detect an option field that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 32-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains two identical and perfectly legal unclassified security options. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error messsge to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4023 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4024 two security options - Can the IUT detect an option field that isn't well-formed? - Action: Send a datagram to tne IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 32-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains two different and perfectly legal security options. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4024 error" in its 181 byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4025 two security options - Can the IUT detect an option field that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 32-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains two different and perfectly legal security options in reverse order of test 4024. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4025 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4026 security option with an invalid security level - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 12-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid security option whose sole defect is an invalid security level. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4026 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4027 ordinary datagram after bad security option tests - Can the IUT send a datagram after processing nastygrams? - Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 4027 ~n its 13-byte data field. Success: A reply datagram containing "ident = 4027 ". Failure: Any response other than the display of the requested reply datagram. The actual failure probably occurred during tests 4013-4026. Test 4028 truncated stream identification option - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 4-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. The first byte of the option field requested to be sent is a no operation option. This is followed by a truncated stream identification option. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4028 -error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4029 stream identification option length bumped by 1 - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 4-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid stream identification option whose option length has been bumped by 1. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4029 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4030 stream identification option one byte too long - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid stream identification option that is one byte too long. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4030 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4031 stream identification option one byte too short - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 4-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid stream identification option that is one byte too short. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4031 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4032 stream identification option length of 0 - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 4-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid stream identification option whose option length is set to 0. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4032 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4033 stream identification option length of 377 octal - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid stream identification option whose option length is set to 377 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4033 error" in its 18- byte data field. The IP Tester should slso display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4034 stream identification option length of 353 octal - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 4lbyte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid stream identification option whose option length is set to 353 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send sn IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4034 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4035 stream identification option length of 177 octal - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 4-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid stream identification option whose option length is set to 177 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4035 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4036 stream identification option length of 200 octal 1 Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 4-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid stream identification option whose option length is set to 200 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4036 error" in its 181 byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4037 stream identification option length of 204 octal - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 4-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid stream identification option whose option length is set to 204 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4039 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4040 bad security option plus good stream identification option - Can the IUT detect an option field that isn't well-formed: - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 16-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains a security option with an invalid security level and a legal stream ID option. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification- error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4040 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4041 bad security option plus good stream identification option - Can the IUT detect an option field that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 16-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains a security option with an invalid option - Verification: The IP Tester will display the error message datagram that must contain "ident = 4039 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4040 bad security option plus good stream identification option - Can the IUT detect an option field that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 16-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains a security option with an invalid security level and a legal stream ID option. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4040 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4041 bad security option plus good stream identification option - Can the IUT detect an option field that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 16-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains a security option with an invalid option length and a legal stream ID option. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. 1 Verification: The IP Tester will display the error message datagram that must contain "ident = 4041 error" in its 181 byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4042 ordinary datagram after bad stream ID option tests - Can the IUT send a datagram after processing nastygrams? - Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 4042 " in its 13-byte data field. Success: A reply datagram containing "ident = 4042 ". Failure: Any response other than the display of the requested reply datagram. The actual failure probably occurred during tests 4028-4041. Test 4043 truncated record route option - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8lbyte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. The first two bytes of the option field requested to be sent are no operation options. They are followed by a truncated record route option. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4043 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4044 record route option length bumped by 1 - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains a record route option whose option length has been bumped by 1. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4044 error" in its 181 byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4045 record route option one byte too long - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains a record route option that is one byte too long. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4045 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4046 record route option one byte too short 1 Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains a record route option that is one byte too short. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4046 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4047 record route option length of 0 - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains a record route option whose option length is set to 0. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4047 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4048 record route option length of 377 octal 1 Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains a record route option whose option length is set to 377 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4048 error" in its 181 byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4049 record route option length of 353 octal - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains a record route option whose option length is set to 353 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4049 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4050 record route option length of 177 octal - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains a record route option whose option length is set to 177 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4050 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4051 record route option length of 200 octal - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains a record route option whose option length is set to 200 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4051 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4052 record route option length of 207 octal 1 Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains a record route option whose option length is set to 207 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4052 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4053 record route option pointer bumped by 1 - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains a record route option whose option pointer is one more than it should be. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4053 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4054 record route option pointer one short - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains a record route option whose option pointer is one less than it should be. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4054 error" in its 181 byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4055 record route option pointer of 300 octal - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains a record route option whose option pointer is set to 300 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4055 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4056 record route option pointer of 174 octal - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains a record route option whose option pointer is set to 174 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4056 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4057 record route option with bad option length and option pointer - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains a record route option whose option length and option pointer have both been bumped by 12. The IUT is required to inform its Remote Driver that the request is - Verification: The IP Tester will display the error message datagram that must contain "ident = 4055 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4056 record route option pointer of 174 octal - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains a record route option whose option pointer is set to 174 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4056 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4057 record route option with bad option length and option pointer - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains a record route option whose option length and option pointer have both been bumped by 12. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4057 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4058 record route option with bad option pointer - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains a record route option whose option pointer just exceeds its maximum legal value. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4058 error" in its 181 byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4059 record route option with bad option pointer - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 12-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains a two address field record route option whose option pointer just exceeds its maximum legal value. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4059 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4060 record route option duplicated - Can the IUT detect an option field that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 24-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains two identical and perfectly legal record route options. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4060 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4061 two record route options - Can the IUT detect an option field that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 28-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains two perfectly legal but different record route options. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4061 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4062 ordinary datagram after bad record route option tests - Can the IUT send a datagram after processing nastygrams? - Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 4062 " in its 13-byte data field. Success: A reply datagram containing "ident = 4062 ". Failure: Any response other than the display of the requested reply datagram. The actual failure probably occurred during tests 4043-4061. Test 4063 truncated timestamp option - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8lbyte option field. This datagram should be passed by tne IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. The first byte of the option field requested to be sent is a no operation option. It is followed by a truncated Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid timestamp only timestamp option that is one byte too long. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4065 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4066 timestamp option one byte too short - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid timestamp only timestamp option that is one byte too short. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should, then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4066 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4067 timestamp option length of 0 - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid timestamp only timestamp option whose option length is set to 0. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4067 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4068 timestamp option length of 374 octal - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 12-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid timestamp only timestamp option whose option length is set to 374 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4068 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4069 timestamp option length of 354 octal - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid timestamp only timestamp option whose option length is set to 354 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4069 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4070 timestamp option length of 174 octal - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid timestamp only timestamp option whose option length is set to 174 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. 1 Verification: The IP Tester will display the error message datagram that must contain "ident = 4070 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4071 timestamp option length of 200 octal - Can the IUT detect an optiom that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid timestamp only timestamp option whose option length is set to 200 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4071 error" in its 181 byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4072 timestamp option length of 210 octal - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid timestamp only timestamp option whose option length is set to 210 octal (sign bit set). The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4072 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4073 timestamp option pointer bumped by 1 - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid timestamp only timestamp option whose option pointer is one more than it should be. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4073 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4074 timestamp option pointer one short - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid timestamp only timestamp option whose option pointer is one less than it should be. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4074 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4075 timestamp option pointer of 301 octal - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid timestamp only timestamp option whose option pointer is set to 301 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4075 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4076 timestamp option pointer of 175 octal - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid timestamp only timestamp option whose option pointer is set to 175 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4076 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4077 timestamp option with bad option length and option pointer - Can the IUT detect an option that isn't well-formed?- - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains a timestamp only timestamp option whose option length and option pointer have both been bumped by 12. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4077 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4078 timestamp option with bad option pointer - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an 8-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid timestamp only timestamp option whose option pointer just exceeds its maximum legal value. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The LP Tester will display the error message datagram that must contain "ident = 4080 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4081 two timestamp options 1 Can the IUT detect an option field that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 28-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains two perfectly legal but different timestamp only timestamp options. The IUT is required to inform its Remote Driver that the request is invalid. The- Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4081 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4082 timestamp option with bad timestamp option format - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 12-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains a timestamp option with an invalid format value. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4082 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4083 truncated timestamp option - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 12-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. The first byte of the option field requested to be sent is a no operation option. It is followed by a truncated address and timestamp timestamp option. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4083 error" in its 18- byte-data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4084 timestamp option length bumped by 1 - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 12-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid prespecified timestamp option whose option length is one more than it should be. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4084 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4085 timestamp option one byte too long - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 16-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid address and timestamp timestamp option that is one byte too long. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4085 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4086 timestamp option four bytes too short - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 16-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid prespecified timestamp option whose second timestamp field has been removed. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4086 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4087 timestamp option four bytes too short - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 16-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid address and timestamp timestamp option whose second timestamp field has been removed. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4087 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4088 timestamp option length of 374 octal - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 16-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid prespecified timestamp option whose option length is set to 374 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4088 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4089 timestamp option length of 354 octal - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 12-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid address and timestamp timestamp option whose option length is set to 354 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4089 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4090 timestamp option length of 174 octal - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 12-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid prespecified timestamp option whose option length is set to 174 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4090 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4091 timestamp option length of 200 octal - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 12-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid address and timestamp timestamp option whose option length is set to 200 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4091 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4092 timestamp option length of 214 octal - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 12-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid prespecified timestamp option whose option length is set to 214 octal (sign bit set). The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4092 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4093 timestamp option pointer bumped by 4 - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 12-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid address and timestamp timestamp option whose option pointer is four more than it should be. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4093 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4094 timestamp option pointer four short - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 12-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid prespecified timestamp option whose option pointer is four less than it should be. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4094 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4095 timestamp option pointer of 305 octal - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 12-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid address and timestamp timestamp option whose option pointer is set to 305 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4095 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4096 timestamp option pointer of 175 octal - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 12-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid prespecified timestamp option whose option pointer is set to 175 octal. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4096 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4097 timestamp option with bad option length and option pointer - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 12-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid address and timestamp timestamp option whose option length and option pointer have been bumped by 16. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4097 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4098 timestamp option with bad option pointer - Can the IUT detect an option that isn't well-formed? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a 12-byte option field. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. This contains an invalid prespecified timestamp option whose option pointer just exceeds its maximum legal value. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message datagram that must contain "ident = 4098 error" in its 18- byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the error message datagram does not contain the invalid option field in its IP header. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Test 4099 ordinary datagram after bad timestamp option tests - Can the IUT send a datagram after processing nastygrams? - Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 4099 data field. Success: A reply datagram containing "ident = 4099 ". Failure: Any response other than the display of the requested reply datagram. The actual failure probably occurred during tests 4063-4098. Scenario File OptGdBotTest: "Bottom-up Good Option Field" datagrams 1000 end of options list option 1001 no operation option 1002 two no operation options 1003 three no operation options 1004 four no operation options 1005 unclassified security option 1006 confidential security option 1007 EFTO security option 1008 MMMM security option 1009 PROG security option 1010 restricted security option 1011 secret security option 1012 top secret security option 1013 stream ID option with an ID of 0 1014 stream ID option with an ID of 64 1015 stream ID option with an ID of 128 1016 stream ID option with an ID of 255 1017 stream ID option with an ID of 16384 1018 stream ID option with an ID of 16448 1019 stream ID option with an ID of 16512 1020 stream ID option with an ID of 16639 1021 stream ID option with an ID of 32768 1022 stream ID option with an ID of 32832 1023 stream ID option with an ID of 32896 1024 stream ID option with an ID of 33023 1025 stream ID option with an ID of 65280 1026 stream ID option with an ID of 65344 1027 stream ID option with an ID of 65408 1028 stream ID option with an ID of 65535 1029 stream ID option with an ID of 43605 1030 stream ID option with an ID of 21930 1031 mixture of good options 1032 one address record route option 1033 two address record route option 1034 nine address record route option 1035 fragmented datagram with nine address record route option 1036 eight btye timestamp only option 1037 16 byte timestamp only option 1038 44 byte timestamp only option 1039 fragmented datagram with 44 byte timestamp only option 1040 12 byte address timestamp and addressoption 1041 20 byte timestamp and address option 1042 36 byte timestamp and address option 1043 fragmented datagram with 36 byte timestamp and address option 1044 12 byte prespecified timestamp option 1045 20 byte prespecified timestamp option 1046 28 byte prespecified timestamp option 1047 fragmented datagram with 36 byte prespecified timestamp opti Test 1000 end of options list option - Can the IUT receive a datagram with end of options list option - Action: Send a datagram to the IP Implementation Under Test containing an end of options list option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Drive should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1000 " in its 13-byte data field. The IP Tester should also display "HL5" (internet header length is 5 four-octet units long) to indicate that the reply datagram does not contain an option field in its IP header. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1001 no operation option - Can the IUT receive a datagram with a no operation option? - Action: Send a datagram to the IP Implementation Under Test containing a no operation option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1001 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1002 two no operation options - Can the IUT receive a datagram with two no operation options? - Action: Send a datagram to the IP Implementation Under Test containing two no operation options. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1002 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1003 three no operation options - Can the IUT receive a datagram with three no operation options? - Action: Send a datagram to the IP Implementatiom Under Test containing three no operation options. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1003 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1004 four no operation options - Can the IUT receive a datagram with four no operation options? - Action: Send a datagram to the IP Implementation Under Test containing four no operation options. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1004 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1005 unclassified security option - Can the IUT receive a datagram with an unclassified security option? - Action: Send a datagram to the IP Implementation Under Test containing an unclassified security option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1005 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1006 confidential security option - Can the IUT receive a datagram with a confidential security option? - Action: Send a datagram to the IP Implementation Under Test containing a confidential security option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1006 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1007 EFTO security option - Can the IUT receive a datagram with an EFTO security option? - Action: Send a datagram to the IP Implementation Under Test containing an EFTO security option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1007 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1008 MMMM security option - Can the IUT receive a datagram with a MMMM security option? - Action: Send a datagram to the IP Implementation Under Test containing a MMMM security option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1008 " in Its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1009 PROG security option - Can the IUT receive a datagram with a PROG security option? - Action: Send a datagram to the IP Implementation Under Test containing a PROG security option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1009 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1010 restricted security option - Can the IUT receive a datagram with a restricted security option? - Action: Send a datagram to the IP Implementation Under Test containing a restricted security option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1010 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1011 secret security option - Can the IUT receive a datagram with a secret security option? - Action: Send a datagram to the IP Implementation Under Test containing a secret security option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1011 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1012 top secret security option - Can the IUT receive a datagram with a top secret security option? - Action: Send a datagram to the IP Implementation Under Test containing a top secret security option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1012 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1013 stream ID option with an ID of 0 - Can the IUT receive a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a stream lD option whose ID bytes are clear. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1013 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1014 stream ID option with an ID of 64 - Can the IUT receive a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a stream ID option (upper ID byte clear, lower ID byte 100 octal). This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1014 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1015 stream ID option with an ID of 128 - Can the IUT receive a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a stream ID option (upper ID byte clear, lower ID byte sign bit set.) This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1015 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1016 stream ID option with an ID of 255 - Can the IUT receive a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a stream ID option (upper ID byte clear, lower ID byte bits set). This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1016 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1017 stream ID option with an ID of 16384 - Can the IUT receive a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a stream ID option (upper ID byte 100 octal, lower ID byte clear). This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1017 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1018 stream ID option with an ID of 16448 - Can the IUT receive a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a stream ID option whose ID bytes are set to 100 octal. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver - Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1018 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1019 stream ID option with an ID of 16512 - Can the IUT receive a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a stream ID option (upper ID byte 100 octal, lower ID byte sign bit set). This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1019 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1020 stream ID option with an ID of 16639 - Can the IUT receive a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a stream ID option (upper ID byte 100 octal, Lower ID byte bits set). This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1020 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1021 stream ID option with an ID of 32768 - Can the IUT receive a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a stream ID option (upper ID byte sign bit set, lower ID byte clear). This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1021 " in data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1022 stream ID option with an ID of 32832 - Can the IUT receive a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a stream ID option (upper ID byte sign bit set, lower ID byte 100 octal). This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1022 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1023 stream ID option with an ID of 32896 - Can the IUT receive a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a stream ID option whose ID bytes have their sign bits set. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1023 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1024 stream ID option with an ID of 33023 - Can the IUT receive a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a stream ID option (upper ID byte sign bit set, lower ID byte bits set.) This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1024 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1025 stream ID option with an ID of 65280 - Can the IUT receive a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a stream ID option (upper ID byte bits set, lower ID byte clear). This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1025" in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1026 stream ID option with an ID of 65344 - Can the IUT receive a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a stream ID option (upper ID byte bits set, lower ID byte 100 octal.) This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1026" in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1027 stream ID option with an ID of 65408 - Can the IUT receive a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a stream ID option (upper ID byte bits set, lower ID byte sign bit set). This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1027 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1028 stream ID option with an ID of 65535 - Can the IUT receive a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a stream ID option whose ID bytes have all their bits set. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1028 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1029 stream ID option with an ID of 43605 - Can the IUT receive a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a stream ID option with alternating ID bits set. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. Verification: The IP Tester will display the reply datagram that must contain "ident = 1029 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1030 stream ID option with an ID of 21930 - Can the IUT receive a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a stream ID option with alternating ID bits set. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1030 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1031 mixture of good options - Can the IUT receive a datagram with a mixture of options? - Action: Send a datagram to the IP Implementation Under Test containing an unclassified security option, a no operation option, and a stream ID option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1031" in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1032 one address record route option - Can the IUT receive a datagram with a record route option? - Action: Send a datagram to the IP Implementation Under Test containing a perfectly legal one address field record route option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the lP Remote Driver Specification to the lP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1032" in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1033 two address record route option - Can the IUT receive a datagram with a record route option? - Action: Send a datagram to the IP Implementation Under Test containing a perfectly legal two address field record route option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1033." in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1034 nine address record route option - Can the IUT receive a datagram with a record route option? - Action: Send a datagram to the IP Implementation Under Test containing a perfectly legal nine address field record route option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the-reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1034 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1035 fragmented datagram with nine address record route option - Can the IUT reassemble a datagram with a record route option? - Action: Send a fragmented datagram to the IP Implementation Under Test containing a perfectly legal nine address field record route option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP-Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1035 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1036 eight byte timestamp only option - Can the IUT receive a datagram with a timestamp option? - Action: Send a datagram to the IP Implementation Under Test containing a perfectly legal eight byte timestamp only timestamp option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1036 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1037 12 byte timestamp option - Can the IUT receive a datagram with a timestamp option? - Action: Send a datagram to the IP Implementation Under Test containing a perfectly legal 12 byte timestamp only timestamp option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1037 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1038 44 byte timestamp option - Can the IUT receive a datagram with a timestamp option? - Action: Send a datagram to the IP Implementation Under Test containing a perfectly legal 44 byte field timestamp only timestamp option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1038 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1039 fragmented datagram with 44 byte timestamp only option - Can the IUT reassemble a datagram with a timestamp option? - Action: Send a fragmented datagram to the IP Implementation Under Test containing a perfectly legal timestamp only timestamp option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1039 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1040 12 byte timestamp and address option - Can the IUT receive a datagram with a timestamp option? - Action: Send a datagram to the IP Implementation Under Test containing a perfectly legal 12 byte timestamp and address option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1040 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1041 20 byte timestamp and address - Can the IUT receive a datagram with a timestamp option? - Action: Send a datagram to the IP Implementation Under Test containing a perfectly legal 20 byte timestamp and address option. This datagram should be passed,by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1041 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1042 36 byte timestamp and address option - Can the IUT receive a datagram with a timestamp option? - Action: Send a datagram to the IP Implementation Under Test containing a perfectly legal 36 byte timestamp and address option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1042 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1043 fragmented datagram with 36 byte timestamp and address option - Can the IUT reassemble a datagram with a timestamp option? - Action: Send a fragmented datagram to the IP Implementation Under Test containing a perfectly legal 36 byte timstamp and address option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1043 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1044 12 byte prespecified timestamp option - Can the IUT receive a datagram with a timestamp option? - Action: Send a datagram to the IP Implementation Under Test containing a perfectly legal 12 byte field prespecified timestamp option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 1044 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 1045 20 byte prespecified option - Can the IUT receive a datagram with a timestamp option? - Action: Send a datagram to the IP Implementation Under Test containing a perfectly legal 20 bytes prespecified timestamp option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. 3028 stream ID option with an ID of 65535 3029 stream ID option with an ID of 43605 3030 stream ID option with an ID of 21930 3031 mixture of good options 3032 one address record route option 3033 two address record route option 3034 nine address record route option 3035 fragmented datagram with nine address record route option 3036 eight byte timestamp only option 3037 16 byte timestamp only option 3038 44 byte timestamp only option 3039 fragmented datagram with 44 byte timestamp only option 3040 12 byte timestamp only option 3041 20 byte timestamp option 3042 36 byte timestamp option 3043 fragmented datagram with 36 byte timestamp option 3044 12 byte prespecified timestamp option 3045 20 byte prespecified timestamp option 3046 36 byte prespecified timestamp option 3047 fragmented datagram with 36 byte prespecified timestamp option Test 3000 end of options list option - Can the IUT send a datagram with end of options list option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an end of options list option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3000 in data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3001 no operation option - Can the IUT send a datagram with a no operation option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a no operation option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3001 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3002 two no operation options - Can the IUT send a datagram with two no operation options? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with two no operation options. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IF Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3002 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other tham the display of the reply datagram. Test 3003 three no operation options - Can the IUT send a datagram with three no operation options? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with three no operation options. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3003 " in its 13=byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3004 four no operation options - Can the IUT send a datagram with four no operation options? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with four no operation options. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3004 " in its 13-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3005 unclassified security option - Can the IUT send a datagram with an unclassified security option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an unclassified security option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3005 " in its 13-byte data field. The display should also contain "SEC UNCL comp=00000 hand=hh tcc=tcc". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3006 confidential security option - Can the IUT send a datagram with a confidential security option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a confidential security option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3006 " in its 13-byte data field. The display should also contain "SEC CONF comp=00000 hand=hh tcc=tcc". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3007 EFTO security option - Can the IUT send a datagram with an EFTO security option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an EFTO security option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. -Verification: The IP Tester will display the reply datagram that must contain "ident = 3007 " in its 13-byte data field. The display should also contain "SEC EFTO comp=00000 hand=hh tcc=tcc". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3008 MMMM security option - Can the IUT send a datagram with a MMMM security option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a MMMM security option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3008 " in its 13-byte data field. The display should also contain "SEC MMMM comp=00000 hand=hh tcc=tcc". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3009 PROC security option - Can the IUT send a datagram with a PROC security option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a PROG security option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3009 " in its 13-byte data field. The display should also contain "SEC PROC comp=00000 hand=hh tcc=tcc". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3010 restricted security option - Can the IUT send a datagram with a restricted security option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a restricted security option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3010 " in its 13-byte data field. The display should also contain "SEC REST comp=00000 hand=hh tcc=tcc". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3011 secret security option - Can the IUT send a datagram with a secret security option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a secret security option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3011 " in its 13-byte data field. The display should also contain "SEC SECT comp=00000 hand=hh tcc=tcc". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3012 top secret security option - Can the IUT send a datagram with a top secret security option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a top secret security option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3012 " in its 13-byte data field. The display should also contain "SEC TSEC comp=00000 hand=hh tcc=tcc". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3013 stream ID option with an ID of 0 - Can the IUT send a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a stream ID option whose ID bytes are clear. This datagram should be passed by the IUT to its. Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3013 " in its 13-byte data field. The display should also contain "STREAM 00000". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3014 stream ID option with an ID of 64 - Can the IUT send a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a stream ID option (upper ID byte clear, lower ID byte 100 octal). This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3014 " in its 13 byte data field. The display should also contain "STREAM 00064". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3015 stream ID option with an ID of 128 - Can the IUT send a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a stream ID option (upper ID byte clear, lower ID byte sign bit set). This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3015 " in its 13-byte data field. The display should also contain "STREAM 00128". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3016 stream ID option with an ID of 255 - Can the IUT send a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a stream ID option (upper ID byte clear, lower ID byte bits set). This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3016 " in its 13-byte data field. The display should also contain "STREAM 00255". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3017 stream ID option with an ID of 16384 - Can the IUT send a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a stream ID option (upper ID byte 100 octal, lower ID byte clear.) This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3017 " in its 13-byte data field. The display should also contain "STREAM 16384". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3018 stream ID option with an ID of 16448 - Can the IUT send a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a stream ID option whose ID bytes are set to 100 octal. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3018 " in its 13-byte data field. The display should also contain "STREAM 16448". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3019 stream ID option with an ID of 16512 - Can the IUT send a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a stream ID option (upper ID byte 100 octal, lower ID byte sign bit set). This datagram should be passed by the IUT to its Remote Driver. The IUTs Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3019 " in its 13-byte data field. The display should also contain "STREAM 16512". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3020 stream ID option with an ID of 16639 - Can the IUT send a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a stream ID option (upper ID byte 100 octal, lower ID byte bits set). This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3020 " in its 13-byte data field. The display should also contain "STREAM 16639". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3021 stream ID option with an ID of 32768 - Can the IUT send a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a stream ID option (upper ID byte sign bit set, lower ID byte clear). This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3021 " in its 13-byte data field. The display should also contain "STREAM 32768". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3022 stream ID option with an ID of 32832 - Can the IUT send a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a stream ID option (upper ID byte sign bit set, lower ID byte 100 octal). This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3022 " in its 13-byte data field. The display should also contain "STREAM 32832". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3023 stream ID option with an ID of 32896 - Can the IUT send a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a stream ID option whose ID bytes have their sign bits set. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3023 " in its 13-byte data field. The display should also contain "STREAM 32896". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3024 stream ID option with an ID of 33023 - Can the IUT send a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a stream ID option (upper ID byte sign bit set, lower ID byte bits set). This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3024 " in its 13-byte data field. The display should also contain "STREAM 33023". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3025 stream ID option with an ID of 65280 - Can the IUT send a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a stream ID option (upper ID byte bits set, lower ID byte clear). This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3025 " in its 13-byte data field. The display should also contain "STREAM 65280". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3026 stream ID option with an ID of 65344 - Can the IUT send a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a stream ID option (upper ID byte bits set, lower ID byte 100 octal). This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the repIy datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3026 " in its 13-byte data field. The display should also contain "STREAM 65344". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3027 stream ID option with an ID of 65408 - Can the IUT send a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a stream ID option (upper ID byte bits set, lower ID byte sign bit set.) This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3027 " in its 13-byte data field. The display should also contain "STREAM 65408". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3028 stream ID option with an ID of 65535 - Can the IUT send a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a stream ID option whose ID bytes have all their bits set. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3028 " in its 13-byte data field. The display should also contain "STREAM 65535". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3029 stream ID option with an ID of 43605 - Can the IUT send a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a stream ID option with alternating ID bits set. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3029 " in its 13-byte data field. The display should also contain "STREAM 43605". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3030 stream ID option with an ID of 21930 - Can the IUT send a datagram with a stream ID option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a stream ID option with alternating ID bits set. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3030 " in its 13-byte data field. The display should also contain "STREAM 21930". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3031 mixture of good options - Can the IUT send a datagram with a mixture of options? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with an unclassified security option, a no operation option, and a stream ID option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3031 " in its 13-byte data field. The display should also contain "SEC UNCL comp=00000 hand=hh tcc=tcc" followed by "STREAM 21930". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3032 one address record route option - Can the IUT send a datagram with a record route option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a perfectly legal one address field record route option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3032 " in its 13-byte data field. The display should also contain "ROUTE len=007 ptr=004 00000000000". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3033 two address record route option - Can the IUT send a datagram with a record route option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a perfectly legal two address field record route option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3033 " in its 13-byte data field. The display should also contain "ROUTE len=011 ptr=004 00000000000 00000000000,. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3034 nine address record route option - Can the IUT send a datagram with a record route option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a perfectly legal nine address field record route option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3034 ." in its 13-byte data field. The display should also contain "ROUTE len=039 ptr=004 00000000000 00000000000 00000000000 00000000000 00000000000 00000000000 00000000000 00000000000 00000000000,. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3036 eight byte timestamp only option - Can the IUT send a datagram with a timestamp option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a perfectly legal eight byte timestamp only timestamp option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3036 " in its 13-byte data field. The display should also contain "TIMESTAMP len=008 ptr=005 ovr=00 TIMSO 00000000000". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3037 12 byte timestamp only option - Can the IUT send a datagram with a timestamp option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a perfectly legal two timestamp field timestamp only timestamp option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3D37 " in its 13-byte data field. The display should also contain "TIMESTAMP len=012 ptr=005 ovr=00 TIMSO 00000000000000000000000,. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3038 44 byte timestamp only option - Can the IUT send a datagram with a timestamp option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a perfectly Iegal 44 byte field timestamp only timestamp option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3038 " in its 13-byte data field. The display should also contain "TIMESTAMP len=040 ptr=005 ovr=00 TIMSO 00000000000 00000000000 00000000000 00000000000 00000000000 00000000000 00000000000 00000000000 00000000000,. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3040 12 byte timestamp and address option - Can the IUT send a datagram with a timestamp option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a perfectly legal 12 byte option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3040 " in its 13-byte data field. The display should also contain "TIMESTAMP len=012 ptr=005 ovr=00 ALLGT 00000000000 00000000000". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3041 20 byte timestamp and address option - Can the IUT send a datagram with a timestamp option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a perfectly legal 20 byte timestamp and address option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3041 " in its 13-byte data field. The display should also contain "TIMESTAMP len=020 ptr=005 ovr=00 ALLOT 00000000000 00000000000 00000000000 00000000000,. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3042 44 byte tinestamp and address option - Can the IUT send a datagram with a timestamp option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a perfectly legal four timestamp field address and timestamp timestamp option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3042 " in its 13-byte data field. The display should also contain "TIMESTAMP len=036 ptr=005 ovr=00 ALLGT 00000000000 00000000000 00000000000000000000000 00000000000 00000000000 00000000000 00000000000,. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3044 12 byte prespecified timestamp option - Can the IUT send a datagram with a timestamp option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a perfectly legal 12 byte prespecified timestamp option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3044 " in its 13-byte data field. The display should also contain "TIMESTAMP len=012 ptr=005 ovr=00 MATCM 01200200001 00000000000". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3045 two timestamp timestamp option - Can the IUT send a datagram with a timestamp option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a perfectly legal 20 byte prespecified timestamp option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3045 " in its 13-byte data field. The display should also contain "TIMESTAMP len=020 ptr=005 ovr=00 MATCH 01200200001 00000000000 00700200002 00000000000,. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 3046 28 byte prespecified option - Can the IUT send a datagram with a timestamp option? - Action: Send a datagram to the IP Implementation Under Test containing a Remote Driver command request for the IUT to send a datagram with a perfectly legal 36 byte prespecified timestamp option. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 3046 " in its 13-byte data field. The display should also contain "TIMESTAMP 1en=028 ptr=005 ovr=00 MATCH 00701400002 00000000000 01200200001 00000000000 00700200002 00000000000". Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Scenario File PrecBotTest: "Bottom-up Precedence Test" datagrams WARNING: This test depends on the IMPs to deliver a successive datagram with a lower precedence than a preceding datagram after the preceding datagram. A failure of the network to deliver the datagrams as indicated is primarily a reflection of the quality the network and not of the IUT. The IUT is only required to accept all eight datagrams and send eight reply datagrams. As of the date this was written, this test has never failed to deliver the indicated results. 200 precedence 7 201 precedence 6 202 precedence 5 203 precedence 4 204 precedence 3 205 precedence 2 206 precedence 1 207 precedence 0 Test 200 precedence 7 - Can the IUT receive a datagram with precedence 7? - Action: Send a datagram to the IP Implementation Under Test with a precedence of 7. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 200 " in its 12-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 201 precedence 6 - Can the IUT receive a datagram with precedence 6? - Action: Send a datagram to the IP Implementation Under Test with a precedence of 6. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 201 " in its 12-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 202 precedence 5 - Can the IUT receive a datagram with precedence 5? - Action: Send a datagram to the IP Implementation Under Test with a precedence of 5. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 202 " in its 12-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 203 precedence 4 - Can the IUT receive a datagram with precedence 4? - Action: Send a datagram to the IP Implementation Under Test with a precedence of 4. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 203 " in its 12-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 204 precedence 3 - Can the IUT receive a datagram with precedence 3? - Action: Send a datagram to the IP Implementation Under Test with a precedence of 3. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 204 " in its 12-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 205 precedence 2 - Can the IUT receive a datagram with precedence 2? - Action: Send a datagram to the IP Implementation Under Test with a precedence of 2. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 205 " in its 12-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 206 precedence 1 - Can the IUT receive a datagram with precedence 1? - Action: Send a datagram to the IP Implementation Under Test with a precedence of 1. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 206 " in its 12-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 207 precedence 0 - Can the IUT receive a datagram with precedence 0? - Action: Send a datagram to the IP Implementation Under Test with a precedence of 0. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 207 " in its 12-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Scenario File PrecEffTest: "Precedence Effect Test" datagrams NOTICE: The race conditions introduced by precedence are to be considered desirable. The more out of order the reply datagrams are, the better the system is 216 precedence effect Test 216 precedence effect - Can the IUT take advantage of network precedence? - Action: The IP Tester will send eight datagrams in order of increasing precedence to the IUT. The IUT should pass each one to its Remote Driver that should send each reply datagram required by the IP Remote Driver Specification at the same precedence as each datagram received by the IUT. - Verification: The IP Tester will display each reply datagram as it arrives at the IP Tester. If their 12-byte data fields are displayed in the order "ident = 223", "ident = 222", "ident = 221", "ident = 220", "ident = 219", "ident = 218", "ident = 217", "ident = 216", the test was highly successful. If displayed by order of their "ident" number, the test was marginally successful. The summation of the absolute value of the "ident" value of the Nth datagram sent minus the "ident" value of the Nth datagram received in reply by the IP Tester may be used to derive a figure of merit. The best figure is 32 and the worst figure is 0. Success: Display of reply datagrams. Failure: Any response other than the display of the reply datagrams in any order. Scenario File PrecMxdTest: "Mixed Precedence Test" datagrams NOTICE: This test scenario has been dropped because it's useless. Scenario File PrecTopTest: "Top-down Precedence Test" datagrams WARNING: This test depends on the IMPs to deliver a successive datagram with a lower precedence than a preceding datagram after the preceding datagram. A failure of the network to deliver the datagrams as indicated is primarily a reflection of the quality the network and not of the IUT. The IUT is only required to accept all eight datagrams and send eight reply datagrams. As of the date this was written, this test has never failed to deliver the indicated results. 208 precedence 7 209 precedence 6 210 precedence 5 211 precedence 4 212 precedence 3 213 precedence 2 214 precedence 1 215 precedence 0 Test 208 precedence 7 - Can the IUT send a datagram with precedence 7? - Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram at precedence 7 to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 208 prec = 7 " in its 21-byte data field. The display must contain the string "V4HL5P7" to indicate that the datagram was sent at precedence 7. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 209 precedence 6 - Can the IUT send a datagram with precedence 6? - Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram at precedence 6 to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 209 prec = 6 " in its 21-byte data field. The display must contain the string "V4HL5P6" to indicate that the datagram was sent at precedence 6. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 210 precedence 5 - Can the IUT send a datagram with precedence 5? - Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram at precedence 5 to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 210 prec = 5 " in its 21-byte data field. The display must contain the string "V4HL5P5" to indicate that the datagram was sent at precedence 5. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 211 precedence 4 - Can the IUT send a datagram with precedence 4? - Action: Send a datagram to the IP Implementation Under Test. This datagram shouId be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram at precedence 4 to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 211 prec = 4 " in its 21-byte data field. The display must contain the string "V4HL5P4" to indicate that the datagram was sent at precedence 4. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 212 precedence 3 - Can the IUT send a datagram with precedence 3? - Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram at precedence 3 to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 212 prec = 3 " in its 21-byte data field. The display must contain the string "V4HL5P3" to indicate that the datagram was sent at precedence 3. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 213 precedence 2 - Can the IUT send a datagram with precedence 2? - Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram at precedence 2 to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 213 prec = 2 " in its 21-byte data field. The display must contain the string "V4HL5P2" to indicate that the datagram was sent at precedence 2. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 214 precedence 1 - Can the IUT send a datagram with precedence 1? - Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram at precedence 1 to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 214 prec = 1 " in its 21-byte data field. The display must contain the string "V4HL5P1" to indicate that the datagram was sent at precedence 1. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 215 precedence 0 - Can the IUT send a datagram with precedence 0? - Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram at precedence 0 to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 215 prec = 0 " in its 21-byte data field. The display must contain the string "V4HL5PO" to indicate that the datagram was sent at precedence 0. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Scenario File ReasMustTest: "Basic Reassembly Test" datagrams 500 two fragments 501 three fragments 502 four fragments 503 four fragments with middle fragments out of order 504 four fragments in reverse order 505 set and restart reassembly timeout timer 506 set and properly check reassembly timeout timer 507 duplicated header fragment 508 duplicated middle fragment 509 duplicated tail fragment 510 missing header fragment 511 missing middle fragment 512 missing tail fragment 513-514 reassemble two datagrams at once 515-516 fragmented datagram with missing tail fragment + good fragmented datagram 517 identification separation 518 protocol separation 519 middle fragment only 520 reassemble a 576-byte datagram fragmented on 8-octet boundaries 521 reassemble a 576-byte datagram fragmented on 16-octet boundaries 522 reassemble a 576-byte datagram fragmented on 32-octet boundaries 523 reassemble a 576-byte datagram fragmented on 64-octet boundaries 524 reassemble a 576-byte datagram fragmented on 128-octet boundaries 525 reassemble a 576-byte datagram fragmented on 256-octet boundaries Test 500 two fragments - Can the IUT reassemble a datagram split into two fragments? --Action: Send a datagram split into two fragments to the IP Implementation Under Test. This datagram should be reassembled by the IUT and passed to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the lP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 500 " in its 12-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 501 three fragments - Can the IUT reassemble a datagram split into three fragments? - Action: Send a datagram split into three fragments to the IP Implementation Under Test. This datagram should be reassembled by the IUT and passed to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 501 reliab = 1 " in its 23 byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 502 four fragments - Can the IUT reassemble a datagram split into four fragments? - Action: Send a datagram split into four fragments to the IP Implementation Under Test. This datagram should be reassembled by the IUT and passed to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 502 datalen = 42 ident = 502 datal" in its 42-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 503 four fragments with middle fragments out of order - Can the IUT reassemble fragments received out of order? - Action: Send a fragmented datagram to the IP Implementation Under Test with the second and third fragments out of order. This datagram should be reassembled by the IUT and passed to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 503 datalen = 43 ident = 503 datale" in its 43-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 504 four fragments in reverse order - Can the IUT reassemble fragments received out of order? - Action: Send a fragmented datagram to the IP Implementation Under Test with fragments in reverse order. This datagram should be reassembled by the IUT and passed to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 504 datalen = 44 ident = 504 datalen" in its 44-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 505 set and restart reassembly timeout timer - Can the LUT manage its reassembly timeout timer? - Action: Send a fragmented datagram to the IP Implementation Under Test. The first fragment is sent with a time to live value of 70 seconds. The IP Test Controller will wait for 55 seconds before sending the next fragment with a time to live of 60 seconds. Since the reassembly timer should be down to around 14 seconds, it should be restarted. The IP Test Controller will wait for 45 seconds before sending the final fragment. The datagram should then be reassembled by the IUT and passed to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 505 datalen = 45 ident = 505 datalen " in its 45-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 506 set and properly check reassembly timeout timer - Can the IUT manage its reassembly timeout timer? - Action: Send a fragmented datagram to the IP Implementa- tion Under Test. The first fragment is sent with a time to live value of 20 seconds. The IP Test Controller will wait for 6 seconds before sending the next fragment with a time to live of 2 seconds. Since the reassembly timer should be down to around 13 seconds, it should not be restarted. The IP Test Controller will wait for 3 seconds before sending the final fragment. The datagram should then be reassembled by the IUT and passed to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 506 datalen = 46 ident = 506 datalen =" in its 46-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 507 duplicated header fragment - Can the IUT handle a duplicated header fragment? - Action: Send a fragmented datagram to the IP Implementation Under Test whose header fragment has been duplicated. This datagram should be reassembled by the IUT and passed to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 507 datalen = 47 ident = 507 datalen = " in its 47-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 508 duplicated middle fragment - Can the IUT handle a duplicated middle fragment? - Action: Send a fragmented datagram to the IP Implementation Under Test whose middle fragment has been duplicated. This datagram should be reassembled by the IUT and passed to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 508 datalen = 48 ident = 508 datalen = 4" in its 48-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 509 duplicated tail fragment - Can the IUT handle a duplicated tail fragment? - Action: Send a fragmented datagram to the IP Implementa- tion Under Test whose tail fragment has been duplicated. Both tail fragments are delivered out of order. This datagram should be reassembled by the IUT and passed to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 509 datalen = 59 ident = 509 datalen = 59 ident = 5" in its 59-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 510 missing header fragment - Can the IUT handle a missing header fragment? - Action: Send a fragmented datagram to the IP Implementation Under Test whose header fragment is missing. The IUT's reassembly timeout timer should expire. The IUT may send an ICMP reassembly timeout message to the IP Tester. - Verification: If there is an IP Tester datagram display, it must contain "ICMP TIME EXCEEDED id=00510 REAS". Success: Display of optional ICMP reassembly timeout message. NOTICE: If there is a display of an ICMP reassembly timeout message, the IUT does not conform to RFC792. Failure: Any response other than the display of the ICMP reassembly timeout message or nothing. Test 511 missing middle fragment - Can the IUT handle a missing middle fragment? - Action: Send a fragmented datagram to the IP Implementation Under Test whose middle fragment is missing. The IUT's reassembly timeout timer should expire. The IUT may send an ICMP reassembly timeout message to the IP Tester. - Verification: If there is an IP Tester datagram display, it must contain "ICMP TIME EXCEEDED id=00511 REAS". Success: Display of optional ICMP reassembly timeout message. Failure: Any response other than the display of the ICMP reassembly timeout message or nothing. Test 512 missing tail fragment - Can the IUT handle a missing tail fragment? - Action: Send a fragmented datagram to the IP Implementation Under Test whose tail fragment is missing. The IUT's reassembly timeout timer should expire. The IUT may send an ICMP reassembly timeout message to the IP Tester. - Verification: If there is an IP Tester datagram display, it must contain "ICMP TIME EXCEEDED id=00512 REAS". Success: Display of optional ICMP reassembly timeout message. Failure: Any response other than the display of the ICMP reassembly timeout message or nothing. Test 513 reassemble two datagrams at once - Can the IUT reassemble two datagrams at once? - Action: Send two fragmented datagrams to the IP Implementation Under Test. Each fragment of the first datagram is followed by a fragment from the second datagram. Each datagram should be reassembled by the IUT and passed to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagrams required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the first reply datagram that must contain "ident = 513 datalen = 43 ident = 513 datal" in its 43-byte data field. This should be followed by the IP Tester display the second reply datagram that must contain "ident = 514 datalen = 44 ident = 514 datale" in its 44-byte data field. Success: Display of reply datagrams. Failure: Any response other than the display of the reply datagrams. Test 515 fragmented datagram with missing tail fragment + good fragmented datagram - Can the IUT handle two datagrams independently? - Action: Send a fragmented datagram to the IP Implementation Under Test whose tail fragment is missing. These are intermixed with a complete set of fragments for a second datagram also sent to the IUT. The second datagram should be reassembled and passed to the IUT's Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. The IUT's reassembly timeout timer for the incomplete set of fragments should expire later. The IUT may send an ICMP reassembly timeout message to the IP Tester. - Verification: The IP Tester will display the first reply datagram that must contain "ident = 516 datalen = 46 ident = 516 datalen " in its 46-byte data field. This may be followed by an IP Tester datagram display containing "ICMP TIME EXCEEDED id=00515 REAS". Success: Display of reply datagram and optional ICMP reassembly timeout message. Failure: Any response other than the reply datagram and optional ICMP reassembly timeout message display. Test 517 identification separation - Can the IUT handle two datagrams independently? - Action: Send fragments to the IP Implementation Under Test that would be sufficient to reassembIe a datagram if their identification fields were identical. The IUT is required to treat these fragments as parts of two separate datagrams in accordance with section 9.4.1. The IUT's reassembly timeout timer for each reassembly should expire later. The IUT may send an ICMP reassembly timeout message to the IP Tester for each. - Verification: The IP Tester will display each ICMP reassembly timeout message that the IUT may send. They must contain "ICMP TIME EXCEEDED. id=00517 REAS" or "ICMP TIME EXCEEDED id=00001 REAS" and may appear in either order or alone. Neither may be duplicated. Success: Display of optional ICMP reassembly timeout message(s). Failure: Any response other than the optional ICMP reassembly timeout message(s). Test 518 protocol separation - Can the IUT handle two datagrams independently? - Action: Send fragments to the IP Implementation Under Test that would be sufficient to reassemble a datagram if their protocol fields were identical. The IUT is required to treat these fragments as parts of two separate datagrams in accordance with section 9.4.1. The IUT's reassembly timeout timer for each reassembly should expire later. The IUT may send an ICMP reassembly timeout message to the IP Tester for each. - Verification: The IP Tester will display each of the two ICMP reassembly timeout messages that the IUT may send. They must contain "ICMP TIME EXCEEDED id=00518 REAS". Success: Display of optional ICMP reassembly timeout message(s). NOTICE: If there is a display of two ICMP reassembly timeout messages, the IUT does not conform to RFC792. Failure: Any response other than the optional ICMP reassembly timeout message(s). Test 519 middle fragment only - Can the IUT handle missing header and tail fragments? - Action: Send a fragment from the middle of a datagram to the IP Implementation Under Test. The IUT's reassembly timeout timer should expire. The IUT may send an ICMP reassembly timeout message to the IP Tester. - Verification: If there is an IP Tester datagram display, it must contain "ICMP TIME EXCEEDED id=00519 REAS". Success: Display of optional ICMP reassembly timeout message. NOTICE: If there is a display of an ICMP reassembly timeout message, the IUT does not conform to RFC792. Failure: Any response other than the display of the ICMP reassembly timeout message or nothing. Test 520 reassemble a 576-byte datagram fragmented on 8-octet boundaries - Can the IUT reassemble a fragmented 576 byte datagram? Test 520 reassemble a 576-byte datagram fragmented on 8-octet boundaries - Can the IUT reassemble a fragmented 576 byte datagram? - Action: Send a 576-byte datagram fragmented on 8-octet boundaries to the IP Implementation Under Test. This datagram should be reassembled by the IUT and passed to its Remote Driver. The IUT's Remote Driver should then request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 520 datalen = 48 ident = 520 datalen = 4" in its 48-byte data field. . Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 521 reassemble a 576-byte datagram fragmented on 16-octet boundaries - Can the IUT reassemble a fragmented 576-byte datagram? - Action: Send a 576-byte datagram fragmented on 16-octet boundaries to the IP Implementation Under Test. This datagram should be reassembled by the IUT and passed to its Remote Driver. The IUT's Remote Driver should then request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 521 datalen = 48 ident = 521 datalen = 4" in its 48-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 522 reassemble a 576-byte datagram fragmented on 32-octet boundaries - Can the IUT reassemble a fragmented 576-byte datagram? - Action: Send a 576-byte datagram fragmented on 32-octet boundaries to the IP Implementation Under Test. This datagram should be reassembled by the IUT and passed to its Remote Driver. The IUT's Remote Driver should then request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 522 datalen = 48 ident 522 datalen = 4" in its 48-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 523 reassemble a 576-byte datagram fragmented on 64-octet boundaries - Can the IUT reassemble a fragmented 576-byte datagram? - Action: Send a 576-byte datagram fragmented on 64-octet boundaries to the IP Implementation Under Test. This datagram should be reassembled by the IUT and passed to its Remote Driver. The IUT's Remote Driver should then request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 523 datalen = 48 ident = 523 datalen = 4" in its 48-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 524 reassemble a 576-byte datagram fragmented on 128-octet boundaries - Can the IUT reassemble a fragmented 576-byte datagram? - Action: Send a 576-byte datagram fragmented on 128-octet boundaries to the IP Implementation Under Test. This datagram should be reassembled by the IUT and passed to its Remote Driver. The IUT's Remote Driver should then request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 524 datalen = 48 ident = 524 datalen = 4" in its 48-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 525 reassemble a 576-byte datagram fragmented on 256-octet boundaries ident = 1024 datalen = 1004 ident = 1024 datalen = 1004 ident = 1024 datalen = 1004 ident = 1024 datalen = 1004 ident = 1024 datalen = 1004 ident = 1024 datalen = 1004 ident = 1024 datalen = 1004 ident = 1024 datalen = 1" in a 1004 byte data field or "ident = 1024 notimpl" in a 20-byte data field. The 1004-data byte reply datagram may arrive in fragments that will also be displayed. Success: Display of reply datagram or not implemented message. Failure: Any response other than the display of the reply datagram or not implemented message. Scenario File Send1144Test: "Send 1144-Byte Datagram Test" 1144 transmission of 1144-byte datagram Test 1144 transmission of 1144-byte datagram - Can the IUT send an 1144-byte datagram? - Action: Send datagram to the IP Implementation Under Test. The IUT should pass this datagram to its Remote Driver. The IUT's Remote Driver should then request the IUT to send the 1144-byte reply datagram required by the IP Remote Driver Specification to the IP Tester. If the IUT can't send it, it should inform its Remote Driver so the Remote Driver can request the IUT to send an IP Remote Driver not implemented message instead. - Verification: The IP Tester will display the reply datagram that may contain either: "ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 ident = 1144 datalen = 1124 iden" in a 1124 byte data field or "ident = 1144 notimpl" in a 20-byte data field. The 1124-data byte reply datagram may arrive in fragments that will also be displayed. Success: Display of reply datagram or not implemented message. Failure: Any response other than the display of the reply datagram or not implemented message. Scenario File Send576Test: "Send 576-Byte Datagram Test" 576 transmission of 576-byte datagram Test 576 transmission of 576-byte datagram - Can the IUT send an 576-byte datagram? - Action: Send datagram to the IP Implementation Under Test. The IUT should pass this datagram to its Remote Driver. The IUT's Remote Driver should then request the IUT to send the 576 byte reply datagram required by the IP Remote Driver Specification to the IP Tester. If the IUT can't send it, it should inform its Remote Driver so the Remote Driver can request the IUT to send an IP Remote Driver not implemented message instead. - Verification: The IP Tester will display the reply datagram that may contain either: "ident = 576 datalen = 556 ident = 576 datalen = 556 ident = 576 datalen = 556 ident = 576 datalen = 556 ident = 576 datalen = 556 ident = 576 datalen = 556 ident = 576 datalen = 556 ident = 576 datalen = 556 ident = 576 datalen = 556 ident = 576 datalen = 556 ident = 576 datalen = 556 ident = 576 datalen = 556 ident = 576 datalen = 556 ident = 576 datalen = 556 ident = 576 datalen = 556 ident = 576 datalen = 556 ident = 576 datalen = 556 ident = 576 datalen = 556 ident = 576 datalen = 556 ident = 576 datalen = 556 The 556-data byte reply datagram may arrive in fragments that will also be displayed. Success: Display of reply datagram or not implemented message. Failure: Any response other than the display of the reply datagram or not implemented message. Scenario File Send68Test: "Send 68-Byte Datagram Test" Test 68 transmission of 68-byte datagram Test 68 transmission of 68-byte datagram - Can the IUT send an 68-byte datagram? - Action: Send datagram to the IP Implementation Under Test. The IUT should pass this datagram to its Remote Driver. The IUT's Remote Driver should then request the lUT to send the 68-byte reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 68 datalen = 48 dontfrag = 1 ident = 68" in a 48-byte data field. The display must also contain "F00000" to indicate that the datagram wasn't fragmented. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Scenario File TOS BitBotTest: "Bottom-up Type of Service Test" datagrams 300 type of service bits clear 301 reliability bit set 302 throughput bit set 303 delay bit set 304 reliability + throughput bits set 305 reliability + delay bits set 306 throughput + delay bits set 307 reliability + throughput + delay bits set 304 reliability + throughput bits set 305 reliability + delay bits set 306 throughput + delay bits set 307 reliability + throughput + delay bits set Test 300 type of service bits clear - Can the IUT receive a datagram with its type of service bits clear? - Action: Send a datagram to the IP Implementation Under Test with its type of service bits clear. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 300 " in its 12-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 301 reliability bit set - Can the IUT receive a datagram with its reliability bit set? - Action: Send a datagram to the IP Implementation Under Test with its reliability bit set. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 301 " in its 12-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 302 throughput bit set - Can the IUT receive a datagram with its throughput bit set? - Action: Send a datagram to the IP Implementation Under Test with its throughput bit set. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 302 " in its 12-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 303 delay bit set - Can the IUT receive a datagram with its delay bit set? - Action: Send a datagram to the IP Implementation Under Test with its delay bit set. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 303 " in its 12-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 304 reliability + throughput bits set - Can the IUT receive a datagram with its reliability and throughput bits set? - Action: Send a datagram to the IP Implementation Under Test with its reliability and throughput bits set. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply data- gram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 304 " in its 12-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 305 " in its 12-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 306 throughput + delay bits set - Can the IUT receive a datagram with its throughput and delay bits set? - Action: Send a datagram to the IP Implementation Under Test with its throughput and delay bits set. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 306 " in its 12-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 307 reliability + throughput + delay bits set - Can the IUT receive a datagram with its reliability, throughput, delay bits set? - Action: Send a datagram to the IP Implementation Under Test with its reliability, throughput, and delay bits set. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 307 " in its 12-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Scenario File TOS BitMxdTest: "Mixed Type of Service Test" datagrams NOTICE: This test scenario has been dropped because it's useless. Scenario File TOS BitTopTest: "Top-Down Type of Service Test" datagrams 308 reliability + throughput + delay bits set 309 throughput + delay bits set 310 reliability + delay bits set 311 reliability + throughput bits set 312 delay bit set 313 throughput bit set 314 reliability bit set 315 type of service bits clear Test 308 reliability + throughput + delay bits set - Can the IUT send a datagram with its reliability, throughput, and delay bits set? - Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram with its reliability, throughput, and delay bits set to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 308 reliab = 1 throu = 1 delay = 1 " in its 43-byte data field. The display must contain the string "V4HL5PODTR" to indicate that the datagram was sent with its reliability, throughput, and delay bits set. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 309 throughput + delay bits set - Can the IUT send a datagram with its throughput and delay bits set? - Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram with its throughput and delay bits set to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 309 throu = 1 delay = 1 " in its 32 byte data field. The display must contain the string "V4HL5PODT " to indicate that the datagram was sent with its throughput and delay bits set. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 310 reliability + delay bits set - Can the IUT send a datagram with its reliability and delay bits set? - Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram with its reliability and delay bits set to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 310 reliab = 1 delay = 1 " in its 33 byte data field. The display must contain the string "V4HL5POD R" to indicate that the datagram was sent with its reliability and delay bits set. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 311 reliability + throughput bits set - Can the IUT send a datagram with its reliability and throughput bits set? - Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram with its reliability and throughput bits set to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 311 reliab = 1 throu = 1 " in its 33-byte data field. The display must contain the string "V4HL5PO TR" to indicate that the datagram was sent with its reliability and throughput bits set. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 312 delay bit set - Can the IUT send a datagram with its delay bit set? - Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram with its delay bit set to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 312 delay = 1 " in its 22-byte data field. The display must contain the string "V4HL5POD " to indicate that the datagram was sent with its delay bit set. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 313 throughput bit set - Can the IUT send a datagram with its throughput bit set? - Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram with its throughput bit set to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 313 throu = 1 " in its 22-byte data field. The display must contain the string "V4HL5PO T " to indicate that the datagram was sent with its throughput bit set. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 314 reliability bit set - Can the IUT send a datagram with its reliability bit set? -- Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram with its reliability bit set to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 314 reliab = 1 " in its 23-byte data field. The display must contain the string "V4HL5PO R" to indicate that the datagram was sent with its reliability bit set. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 315 type of service bits clear - Can the IUT send a datagram with its type of service bits clear? - Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram with its type of service bits clear to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 315 " in its 12-byte data field. The display must contain the string "V4HL5PO" to indicate that the datagram was sent with its type of service bits clear. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Scenario File TOS GateTest: "Gateway Type of Service Test" datagrams 400 low delay + high reliability 401 low delay + high throughput 402 maximum precedence + high reliability 403 maximum precedence + high reliability + low delay 404 maximum precedence + high throughput 405 maximum precedence + high throughput + high reliability 406 low precedence + low delay 407 low precedence + low delay + high reliability 408 very low precedence + low delay + high reliability + high throughput 409 high precedence + low delay + high reliability + high throughput 410 maximum precedence + low delay + high reliability + high throughput Test 400 low delay + high reliability - Can the IUT forward a datagram which should be sent with low delay and high reliability? - Action: Send a datagram to the gateway IUT that should be forwarded to the host IP with low delay and high reliability. It should then be passed by the host IP to its Remote Driver. The host IP's Remote Driver should request the host IP to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 400" in its data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 401 low delay + high throughput - Can the IUT forward a datagram which should be sent with low delay and high throughput? - Action: Send a datagram to the gateway IUT that should be forwarded to the host IP with low delay and high throughput. It should then be passed by the host IP to its Remote Driver. The host IP's Remote Driver should request the host IP to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 401 " in its data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 402 maximum precedence + high reliability - Can the IUT forward a datagram which should be sent with maximum precedence and high reliability? - Action: Send a datagram to the gateway IUT that should be forwarded to the host IP with maximum precedence and high reliability. It should then be passed by the host IP to its Remote Driver. The host IP's Remote Driver should request the host IP to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 402 " in its data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 403 maximum precedence + high reliability + low delay - Can the IUT forward a datagram which should be sent with maximum precedence, high reliability, and low delay? - Action: Send a datagram to the gateway IUT that should be forwarded to the host IP with maximum precedence, high reliability, and low delay. It should then be passed by the host IP to its Remote Driver. The host IP's Remote Driver should request the host IP to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 403 " in its data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 404 maximum precedence + high throughput - Can the IUT forward a datagram which should be sent with maximum precedence and high throughput? - Action: Send a datagram to the gateway IUT that should be forwarded to the host IP with maximum precedence and high throughput. It should then be passed by the host IP to its Remote Driver. The host IP's Remote Driver should request the host IP to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 404 " in its data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 405 maximum precedence + high throughput + high reliability - Can the IUT forward a datagram which should be sent with maximum precedence, high throughput, and high reliability? - Action: Send a datagram to the gateway IUT that should be forwarded to the host IP with maximum precedence, high throughput, and high reliability. It should then be passed by the host IP to its Remote Driver. The host IP's Remote Driver should request the host IP to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 405 " in its data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 406 low precedence + low delay - Can the IUT forward a datagram which should be sent with low precedence and low delay? - Action: Send a datagram to the gateway IUT that should be forwarded to the host IP with low precedence and low delay. It should then be passed by the host IP to its Remote Driver. The host IP's Remote Driver should request the host IP to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 406 " in its data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 407 low precedence + low delay + high reliability - Can the IUT forward a datagram which should be sent with low precedence, low delay, and high reliability? - Action: Send a datagram to the gateway IUT that should be forwarded to the host IP with low precedence, low delay, and high reliability. It should then be passed by the host IP to its Remote Driver. The host IP's Remote Driver should request the host IP to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 407 " in its data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 408 very low precedence + low delay + high reliability + high throughput - Can the IUT forward a datagram which should be sent with very low precedence, low delay, high reliability, and high throughput? - Action: Send a datagram to the gateway IUT that should be forwarded to the host IP with very low precedence, low delay, high reliability, and high throughput. It should then be passed by the host IP to its Remote Driver. The host IP's Remote Driver should request the host IP to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 408 " in its data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 409 high precedence + low delay + high reliability + high throughput - Can the IUT forward a datagram which should be sent with high precedence, low delay, high reliability, and high throughput? - Action: Send a datagram to the gateway IUT that should be forwarded to the host IP with high precedence, low delay, high reliability, and high throughput. It should then be passed by the host IP to its Remote Driver. The host IP's Remote Driver should request the host IP to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 409 " in its data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 410 maximum precedence + low delay + high reliability + high throughput - Can the IUT forward a datagram which should be sent with maximum precedence, low delay, high reliability, and high throughput? - Action: Send a datagram to the gateway IUT that should be forwarded to the host IP with maximum precedence, low delay, high reliability, and high throughput. It should then be passed by the host IP to its Remote Driver. The host IP's Remote Driver should request the host IP to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 410 " in its data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Scenario File TTLBdDotTest: "Bad Time to Live Bottom-up Test" datagrams 607 time to live of 0 608 time to live of 1 Test 607 time to live of 0 - Can the IUT detect a bad time to live ? - Action: Send a datagram from the IP Tester to the IP Implementation Under Test whose sole defect is a time to live that is illegally small. This error should be caught by the IUT. The IUT may send an IGMP time to live exceeded message to the IP Tester. - Verification: If there is a response datagram displayed by the IP Tester, its display should contain the string "ICMP TIME EXCEEDED ID=00607 TTLE". The string "ident = 607 " should not appear in the display of the response datagram because this would indicate that the datagram was passed by the IUT to its Remote Driver. Success: An ICMP Parameter Problem message displayed by the IP Tester. The total lack of an IP Tester response datagram display is also an acceptable response. NOTICE: The IUT does not appear to receive datagrams sent with a time to live of 0. Decause the author doesn't have a line analyser, it is not clear what the problem is. The author "remembers" that the test used to function. Failure: A response datagram whose IP Tester display contains the string "ident = 607 ". Test 608 time to live of 1 - Can the IUT detect a bad time to live ? - Action: Send a datagram from the IP Tester to the IP Implementation Under Test whose sole defect is a time to live that is too small. This error should bs caught by the IUT. The IUT may send an ICMP time to live exceeded message to the IP Tester. - Verification: If there is a response datagram displayed by the IP Tester, its display should contain the string "ICMP TIME EXCEEDED ID=00608 TTLE". The string "ident = 608 should not appear in the display of the response datagram because this would indicate that the datagram was passed by the IUT to its Remote Driver. Success: An ICMP Parameter Problem message displayed by the IP Tester. The total lack of an IP Tester response datagram display is also an acceptable response. Failure: A response datagram whose IP Tester display contains the string "ident = 608 Scenario File TTLDdTopTest: "Bad Time to Live Top-down Test" datagrams 616 time to live of 1 617 time to live of 0 Test 616 time to live of 1 - Can the IUT send a datagram with time to live of 1? - Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram with a time to live of 1 to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 616 ipttl = 1 " in its 22 byte data field. The IP Tester will also display the string "bad time to live" to indicate that a MIL=STD-1777 IP will not accept the datagram. Success: Display of reply datagram and the "bad time to live" string. Failure: Any response other than the display of the reply datagram and "bad time to live" string. Test 617 time to live of 0 - Can the IUT send a datagram with time to live of 0? - Action: Send a datagram to the IP Implementation Under Test. This datagram shouId be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram with a time to live of 0 to the IP Tester. The IUT is required to inform its Remote Driver that the request is invalid. The Remote Driver should then request the IUT to send an IP Remote Driver Specification error message to the IP Tester. - Verification: The IP Tester will display the error message that must contain "ident = 617 error" in its 17-byte data field. Success: Display of error message datagram. Failure: Any response other than the display of the error message datagram. Scenario File TTLGdBotTest: "Good Time to Live Bottom-up Test" datagrams 600 time to live 255 601 time to live 129 602 time to live 128 603 time to live 127 604 time to live 20 605 time to live 85 606 time to live 170 Test 600 time to live 255 - Can the IUT receive a datagram with a time to live of 255? - Action: Send a datagram to the IP Implementation Under Test with a time to live of 255. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 600 " in its 12-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 601 time to live 129 - Can the IUT receive a datagram with a time to live of 129? - Action: Send a datagram to the IP Implementation Under Test with a time to live of 129. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 601 " in its 12-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 602 time to live 128 - Can the IUT receive a datagram with a time to live of 128? - Action: Send a datagram to the IP Implementation Under Test with a time to live of 128. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 602 " in its 12-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 603 time to live 127 - Can the IUT receive a datagram with a time to live of 127? - Action: Send a datagram to the IP Implementation Under Test with a time to live of 127. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 603 " in its 12-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 604 time to live 20 - Can the IUT receive a datagram with a time to live of 20? - Action: Send a datagram to the IP Implementation Under Test with a time to live of 20. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 604 " in its 12-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 605 time to live 85 - Can the IUT receive a datagram with a time to live of 85? - Action: Send a datagram to the IP Implementation Under Test with a time to live of 85. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 605 " in its 12-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 606 time to live 170 - Can the IUT receive a datagram with a time to live of 170? - Action: Send a datagram to the IP Implementation Under Test with a time to live of 170. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 606 " in its 12-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Scenario File TTLGdTopTest: "Good Time to Live Top-down Test" datagrams 609 time to live 255: 610 time to live 129 611 time to live 128 612 time to live 127 613 time to live 20 614 time to live 85 615 time to live 170 Test 609 time to live 255 - Can the IUT send a datagram with a time to live of 255? - Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram with a time to live of 255 to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 609 ipttl = 255 " in its 24-byte data field. The display must contain the string "TTL255" to indicate that the datagram was sent with a time to live of 255. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 610 time to live 129 - Can the IUT send a datagram with a time to live of 129? - Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram with a time to live of 129 to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 610 ipttl = 129 " in its 24 byte data field. The display must contain the string "TTL129" to indicate that the datagram was sent with a time to live of 129. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 611 time to live 128 - Can the IUT send a datagram with a time to live of 128? - Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram with a time to live of 128 to the IP Tester. -- Verification: The IP Tester will display the reply datagram that must contain "ident = 611 ipttl = 128 " in its 24-byte data field. The display must contain the string "TTL128" to indicate that the datagram was sent with a time to live of 128. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 612 time to live 127 - Can the IUT send a datagram with a time to live of 127? - Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram with a time to live of 127 to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 612 ipttl = 127 " in its 24-byte data field. The display must contain the string "TTL127" to indicate that the datagram was sent with a time to live of 127. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 613 time to live 20 - Can the IUT send a datagram with a time to live of 20? - Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram with a time to live of 20 to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 613 ipttl = 20 " in its 23-byte data field. The display must contain the string "TTL020" to indicate that the datagram was sent with a time to live of 20. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 614 time to live 85 - Can the IUT send a datagram with a time to live of 85? - Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram with a time to live of 85 to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 614 ipttl = 85 " in its 23-byte data field. The display must contain the string "TTL085" to indicate that the datagram was sent with a time to live of 85. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Test 615 time to live 170 - Can the IUT send a datagram with a time to live of 170? - Action: Send a datagram to the IP Implementation Under Test. This datagram should be passed by the IUT to its Remote Driver. The IUT's Remote Driver should request the IUT to send the reply datagram with a time to live of 170 to the IP Tester. -- Verification: The IP Tester will display the reply datagram that must contain "ident = 615 ipttl = 170 " in its 24-byte data field. The display must contain the string "TTL170" to indicate that the datagram was sent with a time to live of 170. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram. Scenario File Whole576Test: "Accept 576-Byte Datagram Test" 576 accept 576-byte datagram Test 576 accept 576-byte datagram - Can the IUT accept a 576 byte datagram? - Action: Send an unfragmented 576-byte datagram to the IP Implementation Under Test. The IUT should pass this datagram to its Remote Driver. The IUT's Remote Driver should then request the IUT to send the reply datagram required by the IP Remote Driver Specification to the IP Tester. - Verification: The IP Tester will display the reply datagram that must contain "ident = 576 datalen = 048 datalen = 048 datalen " in a 48-byte data field. Success: Display of reply datagram. Failure: Any response other than the display of the reply datagram.