NAME

  S_RFC3736_Creation-Transmission_Reply.seq - Reply message transmission

TARGET

  Server

SYNOPSIS

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

INITIALIZATION

• Network Topology

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

• Verification Points

Destination address set to TN's unicast address same as the Information-request message's source adderess


    

Reply Message Format
    
msg-type
    REPLY(7)
    
transaction-id
    same as Information-request's transaction-id
    
options
    
Server ID option
        Any
    
Client ID option
    same as Information-request's Client ID
    
    

• 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 stateless DHCPv6 Server)
        |       | 
        | <---- | Information-request(w/ Option Request option(DNS Recursive Name Server option))
        | ----> | Reply (*1)
        |       | 
        |       | 

JUDGEMENT

(*1)PASS:  NUT returns the Reply message that is same as the description of verification points.

TERMINATION

REFERENCE

   See also RFC3315 
   17.2.3 and 18.2   See also RFC3646 
   3 and 4   see also RFC3736
   5.1. 5.2 adn 5.3

SEE ALSO