NAME

  R_RFC3646_4_MultiRelayReplyAdvMsg.seq - Relay-Reply Advertise message transmission through the layered Relay agents for DNS Domain Search List option

TARGET

  Relay agent

SYNOPSIS

 R_RFC3646_4_MultiRelayReplyAdvMsg.seq [-tooloption ...]
 -pkt R_RFC3646_4_MultiRelayReplyAdvMsg.def 
 -tooloption: v6eval tool option
 

INITIALIZATION

• Network Topology

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

• Verification Points

Relay-reply Message 2
        

	
msg-type
	RELAY-REPLY
	
hop-count
	0
	
link-address
	Rleay2's address (Link2)       
	
peer-address
	Client1's addess       
	
Relay Message option
	Advertise Message with DNS Domain Search List option
        
       

• Configuration

        Relay-reply Message 1
	
msg-type
		RELAY-REPLY
		
hop-count
		1
		
link-address
		0       
		
peer-address
		Relay2's Global address (Link1) 
		
Relay Message option
		

			
msg-type
			RELAY-REPLY
			
hop-count
			0
			
link-address
			Rleay2's address (Link2)       
			
peer-address
			Client1's addess       
			
Relay Message option
			Advertise Message with DNS Domain Search List option
		
       

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
Relay2(Link1)	TN	Link1	3ffe:501:ffff:101::/64	fe80::200:ff:fe00:a7a7	00:00:00:00:a7:a7
Relay2(Link2)	TN	Link2	3ffe:501:ffff:102::/64	fe80::200:ff:fe00:a8a8	00:00:00:00:a8:a8
Client1	TN	Link2	3ffe:501:ffff:102::/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(NS Domain Search List option)
	        |       | ----->    |              |Relay-forward(Solicit w/ ORO(DNS Domain Search List option))
	        |       |           |  ------->    |Relay-forward(Solicit w/ ORO(DNS Domain Search List option))
	        |       |           |  <------     |Relay-reply Message1(Relay-reply/Advertise w/ DNS Domain Search List option)  (*1)
	        |       | <----     |              |Relay-reply Message2(Advertise w/ DNS Domain Search List option)  (*2)
	        |       |           |              |

JUDGEMENT

 (*1)(*2) PASS: NUT converts the Relay-reply message correctly.

TERMINATION

REFERENCE

  see also RFC3315
  20.3. Construction of  Relay-reply Messages
  see also RFC3646
  3. DNS Recursive Name Server option

SEE ALSO