NAME

  C_RFC3315_18_1_1_TransReq.seq - Check message format of Request

TARGET

  Client

SYNOPSIS

   C_RFC3315_18_1_1_TransReq.seq [-tooloption...] 
  -pkt   C_RFC3315_18_1_1_TransReq.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 uses a Request message to populate IAs with addresses and
   obtain other configuration information. 

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

   The client places the identifier of the destination server in a
   Server Identifier option.

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

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 
        | <---- |Advertise 
        | ----> |Request (3*)
        |       |

JUDGEMENT


  
  (3*)PASS: TN receives Request from NUT which meets Verification Points.

TERMINATION

N/A

REFERENCE

  Also see RFC3315


  18.1.1. Creation and Transmission of Request Messages