NAME

  S_RFC3315_17.2.2_Creation-TransmissionOfAdvertiseMsgIfRelayReply.seq - Respond to the Solicit Message in a Relay-forward message (w/ Interface-ID)

TARGET

  Server

SYNOPSIS

 S_RFC3315_17.2.2_Creation-TransmissionOfAdvertiseMsgIfRelayReply.seq [-tooloption ...]
 -pkt S_RFC3315_17.2.2_Creation-TransmissionOfAdvertiseMsgIfRelayReply.def 
 -tooloption: v6eval tool option
See Also  DHCPv6.def 
 

INITIALIZATION

• Network Topology

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

• Verification Points

Packet's destination address
	
unicast to the relay agent's address from the received packet
Relay-reply Message
	
msg-type
	RELAY-REPL(13)
	
Relay Message Option
	With Advertise Message
	
Interface-id option
	Same as the Relay-forward 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
Relay agent1	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)
        |       | 
        | <---- | Relay-forward(include "Socilit"  w/ Interface-id option)
        | ----> | Relay-reply (w/ Advertise message & Interface-id option)(*1)
        |       | 

JUDGEMENT

(*1) PASS:Relay-reply message will be received by TN.
          The Interface-Id value of Relay-reply message is same as the
	  Relay-forward message	  

TERMINATION

REFERENCE

   see also RFC3315
   17.2.3.  Creation and Transmission of Reply Messages 

SEE ALSO