NAME

  C_RFC3315_17_1_1_Sol.seq - Check format of Solicit message

TARGET

  Client

SYNOPSIS

   C_RFC3315_17_1_1_Sol.seq [-tooloption...] 
  -pkt  C_RFC3315_17_1_1_Sol.def 
  -tooloption : v6eval tool option
  See Also  DHCPv6.def

INITIALIZATION

Network Topology

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

Verification Points

   The client sets the "msg-type" field to SOLICIT. 
   

   The client generates a transaction ID and inserts this value in the
   "transaction-id" field.
   

   The client MUST include a Client Identifier option to identify itself
   to the server. 
   

   The client includes IA options for any IAs to which it wants the server
   to assign addresses.  
   

   The client MUST NOT include any other options in the Solicit message,
   except as specifically allowed in the definition of individual options.
   

   The client uses IA_NA options to request the assignment of non-
   temporary addresses.

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(1*)
        |       | 
        |       |

JUDGEMENT

  (1*)PASS: Solicit should meets the verification points.

TERMINATION

N/A

REFERENCE

  Also see RFC3315


  17.1.1. Creation of Solicit Messages