NAME

  R_RFC3646_3_MultiRelayRelayForwardRebMsg.seq - Relay-forward Rebind message transmission through the layered Relay agents for DNS Recursive Name Server option

TARGET

  Relay agent

SYNOPSIS

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

INITIALIZATION

• Network Topology

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

• Verification Points

  Relay-forward Message Format
        
  destination address
            All_DHCP_Servers(FF05::1:3)
        
  msg-type
            RELAY-FORW(12)
        
  hop-count
  	  1
        
  link-address
            0 or global address assigned to the interface on which the message was received
        
  peer-address
            Copied from the Relay-forward Rebind message
        
  options
            Relay Message option
  	  Same as the Message that be relayed
  	  (Relay-forward Rebind message with ORO(DNS Recursive Name Server option))
            

• Configuration

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

TEST PROCEDURE

	    TN(Client1)TN(Relay2) NUT(Relay1) TN(Server1)
	        |       |           |              |
	        | ----> |           |              |Solicit w/ ORO(DNS Recursive Name Server option)
	        |       | ----->    |              |Relay-forward(Solicit w/ ORO(DNS Recursive Name Server option))
	        |       |           |  ------->    |Relay-forward(Solicit w/ ORO(DNS Recursive Name Server option))
	        |       |           |  <------     |Relay-reply Message(Relay-reply/Advertise w/ DNS Recursive Name Server option)
	        |       | <----     |              |Relay-reply Message(Advertise w/ DNS Recursive Name Server option)
	        |       |           |              |
	        | ----> |           |              |Request w/ ORO(DNS Recursive Name Server option)
	        |       | ----->    |              |Relay-forward(Request w/ ORO(DNS Recursive Name Server option))
	        |       |           |  ------->    |Relay-forward(Request w/ ORO(DNS Recursive Name Server option)) 
	        |       |           |  <------     |Relay-reply Message(Relay-reply/Reply w/ DNS Recursive Name Server option)  
	        |       | <----     |              |Relay-reply Message2(Reply w/ DNS Recursive Name Server option)
	        |       |           |              |
	        | ----> |           |              |Rebind w/ ORO(DNS Recursive Name Server option)
	        |       | ----->    |              |Relay-forward(Rebind w/ ORO(DNS Recursive Name Server option))
	        |       |           |  ------->    |Relay-forward(Rebind w/ ORO(DNS Recursive Name Server option))  (*1)
	        |       |           |              |

JUDGEMENT

(*1)PASS: Relay-forward Message is same as the description of verification points.

TERMINATION

REFERENCE

  see also RFC3315
  20.1, 20.1.1 and 20.1.2
  see also RFC3646
  3. DNS Recursive Name Server option

SEE ALSO