NAME

  C_RFC3315_18_1_8_ReqReplyWStatusNotOnLink.seq - Test Reply with status code of NotOnLink

TARGET

  Client

SYNOPSIS

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


  See Also  DHCPv6.def

INITIALIZATION

Network Topology

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

Verification Points

   When the client receives a NotOnLink status from the server in
   response to a Request, the client can either re-issue the Request
   without specifying any addresses or restart the DHCP server discovery
   process.

Configurations

`Device Name`	`Device Type`	`Interface`	`Assigned Prefix`	`Link Local Addr`	`MAC Addr`
`Client`	`NUT`	`Link0`	`3ffe:501:ffff:100::/64`	`NUT's Linklocal address`	`NUT's MAC address`
`Server`	`TN`	`Link0`	`3ffe:501:ffff:100::/64`	`fe80::200:ff:fe00:a1a1`	`00:00:00:00:a1:a1`

TEST PROCEDURE



       NUT      TN
        |       |
        |       |Initialize NUT(as a DHCPv6 client)
        |       |
        | ----> |Solicit
        | <---- |Advertise
        | ----> |Request
        | <---- |Reply w/Status code/NotOnLink
        |       |
        | ----> |Solicit or Request (5*)
        |       |

JUDGEMENT


  
  (5*)PASS: NUT transmits Solicit or Request message.

TERMINATION

N/A

REFERENCE

  Also see RFC3315


  18.1.8. Receipt of Reply Messages