NAME

  C_RFC3315_SolReply.seq - Check the case of Solicit-Reply Exchange

TARGET

  Client

SYNOPSIS

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


  See Also  DHCPv6.def

INITIALIZATION

Network Topology

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

Verification Points

   In this case, the client sends a Solicit message to the All_DHCP_Relay
   _Agents_and_Servers requesting the assignment of addresses.This message
   includes an Rapid commit option to indicate that the client is willing
   to accept an immediate Reply message from the server.The server that is
   willing to commit the assignment of addresses to the client immediately
   responds with a Reply message. 

   In order to test whether NUT has accepted the assignment of Server,TN 
   sends Echo Request to NUT. And soon, NUT sends Echo Reply to TN.

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/Rapid commit option 
        |       |
        | <---- |Echo Request 
        | ----> |Echo Reply (4*)
        |       |

JUDGEMENT


  
  (1*)PASS: TN receives Solicit from NUT.
  (4*)PASS: NUT sends Echo Reply to TN.

TERMINATION

N/A

REFERENCE

  Also see RFC3315