NAME

  C_RFC3633_12_1_RebWIAPDOpt.seq - Check the format of Rebind with IA_PD option

TARGET

  Client

SYNOPSIS

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


  See Also  DHCPv6.def

INITIALIZATION

Network Topology

          NUT(Requesting router)
          |           
          |                        
Link0   --+--------+------------------------ 3ffe:501:ffff:100::/64
                   |
                   |          
                   TN(Delegating router)

Verification Points

   In some circumstances the requesting router may need verification
   that the delegating router still has a valid binding for the
   requesting router.  Examples of times when a requesting router may
   ask for such verification include:

   o  The requesting router reboots. 

   o  The requesting router's upstream link flaps.

   o  The requesting router is physically disconnected from a wired
      connection.

   If such verification is needed the requesting router MUST initiate a
   Rebind/Reply message exchange.

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 Requesting router)
        |       | 
        | ----> |Solicit w/IA_PD option
        | <---- |Advertise
        | ----> |Request
        | <---- |Reply
        |       |
        |       |Restart NUT
        |       |	
        | ----> |Rebind w/IA_PD option (5*)
        |       |

JUDGEMENT

  (5*)PASS: NUT transmits Rebind message with IA_PD option.

TERMINATION

N/A

REFERENCE

  Also see RFC3633


  12.1.  Requesting router behavior