NAME

  C_RFC3315_17_1_4_InvalidReplyWORapidCommit.seq - Test when Reply without Rapid commit option

TARGET

  Client

SYNOPSIS

   C_RFC3315_17_1_4_InvalidReplyWORapidCommit.seq [-tooloption...] 
  -pkt   C_RFC3315_17_1_4_InvalidReplyWORapidCommit.def 
  -tooloption : v6eval tool option


  See Also  DHCPv6.def

INITIALIZATION

Network Topology

          NUT(Client)
          |           
          |                        
Link0   --+--------+------------------------ 3ffe:501:ffff:100::/64
                   |
                   |          
                   TN(Server)

Verification Points

   If the client includes a Rapid Commit option in the Solicit message,
   it will expect a Reply message that includes a Rapid Commit option in
   response.  The client discards any Reply messages it receives that do
   not include a Rapid Commit option.

Configurations

`Device Name`	`Device Type`	`Interface`	`Assigned Prefix`	`Link Local Addr`	`MAC Addr`
`Client`	`NUT`	`Link0`	`3ffe:501:ffff:100::/64`	`NUT's Linklocal address`	`NUT's MAC address`
`Server`	`TN`	`Link0`	`3ffe:501:ffff:100::/64`	`fe80::200:ff:fe00:a1a1`	`00:00:00:00:a1:a1`

TEST PROCEDURE



       NUT      TN
        |       |
        |       |Initialize NUT(as a DHCPv6 client)
        |       |
        | ----> |Solicit w/ Rapid commit option (1*)
        |       |
        | <---- |Reply w/o Rapid commit option 
        |       |
        |       |waiting until DHCPv6 Message arrives
        |       |
        | ----> |Solicit (3*)
        |       |

JUDGEMENT


  
  (1*)PASS: NUT sends Solicit with Rapid commit option.
  (3*)PASS: NUT sends Solicit.

TERMINATION

N/A

REFERENCE

  Also see RFC3315


  17.1.4. Receipt of Reply Message