NAME

  S_RFC3315_22.2_ClientIdentifierOP.seq - Checking Client Identifier Option


TARGET

  Server


SYNOPSIS

 S_RFC3315_22.2_ClientIdentifierOP.seq [-tooloption ...]
 -pkt S_RFC3315_22.2_ClientIdentifierOP.def 
 -tooloption: v6eval tool option
See Also  DHCPv6.def 
 


INITIALIZATION

          TN(Client1)  
             |
Link0 -------+-----------+--------------- 3ffe:501:ffff:100::/64
                         |
                       NUT(Server1)
  
Device Name Device Type I/F Assigned Prefix Link Local Addr MAC Addr
Server1 NUT Link0 3ffe:501:ffff:100::/64 NUT's Linklocal address NUT's MAC address
Client1 TN Link0 3ffe:501:ffff:100::/64 fe80::200:ff:fe00:a2a2 00:00:00:00:a2:a2


TEST PROCEDURE

       NUT      TN
        |       | 
        |       | initialize NUT (as a DHCPv6 Server)
        |       | 
        | <---- | Solicit
        | ----> | Advertise   (w/ Client ID) (*1)
        |       | 


JUDGEMENT

(*1) PASS: The Advertise message must include Client ID option(DUID same as the Solicit Message.).
           And the format of options must be based on the RFC's description.
           (see the above Verification Points )


TERMINATION

N/A


REFERENCE

   see also RFC3315
   22.2. Client Identifier Option


SEE ALSO

perldoc V6evalTool