NAME

  S_RFC3315_22.3_ServerIdentifierOP.seq - Checking Server Identifier Option

TARGET

  Server

SYNOPSIS

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

INITIALIZATION

• Network Topology

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

• Verification Points

Reply Message Format
      
msg-type
          REPLY(7)
      
transaction-id
	  Any
      
Server ID option

option-code
OPTION_SERVERID (2).
option-len
Any Length of DUID in octets.
DUID
          
The DUID for the server.

Client ID option

option-code
OPTION_CLIENTID (1).
option-len
Any Length of DUID in octets.
DUID
          
The DUID same as the Solicit Message.

• Configuration

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 (w/ Rapid Commit option)
        | ----> | Reply   (w/ Client ID and Server ID) (*1)
        |       | 

JUDGEMENT

(*1) PASS: The Reply message must include Server ID option & Client ID option.
           And the format of options must be based on the RFC's description.
           (see the above Verification Points )

TERMINATION

REFERENCE

   see also RFC3315
   22.3. Server Identifier Option

SEE ALSO