NAME

  S_RFC3646_3_DNSOP_for_Reply.seq - Reply message in response to Request message with ORO (DNS Recursive Name Server option)

TARGET

  Server

SYNOPSIS

 S_RFC3646_3_DNSOP_for_Reply.seq [-tooloption ...]
 -pkt S_RFC3646_3_DNSOP_for_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 Request message's source adderess


Reply Message
        
msg-type
        REPLY(7)
        
transaction-id
        Same as the Request Message
        
Server Identifier option
        Any
        
Client Identifier option
        Same as the Request Message
        
DNS Recursive Name Server option 

      
option-code
      OPTION_DNS_SERVERS (23)
      
option-len
      Length of the list of DNS recursive name servers in octets; 
      must be a multiple of 16
      
DNS-recursive-name-server
      Any(IPv6 address of DNS recursive name server)
    
      

• Configuration

      TN send Request message with Option Request option
      
option-code
      OPTION_ORO(6)
      
request-option-code
      OPTION_DNS_SERVERS (23)
      

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/ Option Request option)
        | ----> | Advertise
        | <---- | Request
        | ----> | Reply (*1)
        |       | 

JUDGEMENT

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

TERMINATION

REFERENCE

   see also RFC3646
   3. DNS Recursive Name Server option

   RFC 3315
   Section 17.2.3

SEE ALSO