NAME

  C_RFC3315_17_1_4_ValidReplyWRapidCommit.seq - Test when Reply with Rapid commit option

TARGET

  Client

SYNOPSIS

   C_RFC3315_17_1_4_ValidReplyWRapidCommit.seq [-tooloption...] 
  -pkt   C_RFC3315_17_1_4_ValidReplyWRapidCommit.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 receives a valid Reply message that includes a 
    Rapid Commit option, the client will receive the configuration
    in the Reply message.

Configurations

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

TEST PROCEDURE



       NUT      TN
        |       |
        |       |Initialize NUT(as a DHCPv6 client)
        |       |
        | ----> |Solicit w/Rapid commit option (1*)
        |       |
        | <---- |Reply w/Rapid commit option 
        |       |
        | <---- |Echo Request 
        | ----> |Echo Reply (4*) 
        |       |

JUDGEMENT

  (1*)PASS: TN receives Solicit with Rapid commit option
  (4*)PASS: TN receives Echo Reply from NUT.

TERMINATION

N/A

REFERENCE

  Also see RFC3315


  17.1.4. Receipt of Reply Message