NAME

  S_RFC3315_22.18_InvalidInterfaceIDOP.seq - Checking Invalid Interface option

TARGET

  Server

SYNOPSIS

 S_RFC3315_22.18_InvalidInterfaceIDOP.seq [-tooloption ...]
 -pkt S_RFC3315_22.18_InvalidInterfaceIDOP.def 
 -tooloption: v6eval tool option
See Also  DHCPv6.def 
 

INITIALIZATION

• Network Topology

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

• Verification Points

This option MUST NOT appear in any message except a Relay-Forward or Relay-Reply message.

• Configuration
• The TN's Information-request Message
  
The TN send Information-request Message to request the Interface-Id option [code(18)]

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
        | ----> | Advertise
        | <---- | Request	
        | ----> | Reply		
        |       | 
        | <---- | Information-request	(w/ Option Request option)
        |       | NUT doesn't return any messages	(*1)
        |       | or
        |       | The Reply message doesn't include Interface-Id option

JUDGEMENT

(*1)PASS:  NUT must not return any messages or send Reply message without Interface-Id option.

TERMINATION

REFERENCE

   see also RFC3315
   22.18. Interface-Id Option

SEE ALSO