NAME

Client_transmit_Renew_02 - Creation and Transmission of Renew Messages (fail) #2

TARGET

Host

TOPOLOGY

           CLIENT0       NUT        SERVER0
              |           |           |
Link0 --------+-----------+-----------+-----+
                                            |
                                          RELAY0
                                            |
                                            +-------+--------------+-------Link1
                                                    |              |
                                                 CLIENT1         SERVER1

Link0	3ffe:501:ffff:100::/64
Link1	3ffe:501:ffff:101::/64
CLIENT0	3ffe:501:ffff:100:200:ff:fe00:a6a6	fe80::200:ff:fe00:a6a6	00:00:00:00:a6:a6
CLIENT1	3ffe:501:ffff:101:200:ff:fe00:a7a7	fe80::200:ff:fe00:a7a7	00:00:00:00:a7:a7
SERVER0	3ffe:501:ffff:100:200:ff:fe00:a2a2	fe80::200:ff:fe00:a2a2	00:00:00:00:a2:a2
SERVER1	3ffe:501:ffff:101:200:ff:fe00:a3a3	fe80::200:ff:fe00:a3a3	00:00:00:00:a3:a3
RELAY0 (Link0)	3ffe:501:ffff:100:200:ff:fe00:a4a4	fe80::200:ff:fe00:a4a4	00:00:00:00:a4:a4
RELAY0 (Link1)	3ffe:501:ffff:101:200:ff:fe00:a5a5	fe80::200:ff:fe00:a5a5	00:00:00:00:a5:a5

TEST PROCEDURE

Creation and Transmission of Renew Messages (fail) #2

       NUT    SERVER0
        |       | 
        |       | initialize NUT (as a DHCPv6 Client)
        |       | 
        | ----> | Solicit (*1)
        | <---- | Advertise 
        |       | 
        | ----> | Request (*2)
        | <---- | Reply (IA_NA, preferred lifetime=60)
        |       | 
        | <---- | Echo Request
        | ----> | Echo Reply (to assigned address) (*3)
        |       | 
        |       | wait 60 sec
        |       | 
        | ----> | Renew (*4)
        | <---- | Reply (IA_NA, StatusCode=NoBinding)
        |       | 
        | ----> | Request (*5)
        | <---- | Reply (IA_NA, preferred lifetime=60)

        1. initialize NUT as a dhcpv6 server
        2. SERVER0 receives Solicit Message from NUT
        3. SERVER0 sends Advertise Message to NUT
        4. SERVER0 receives Request Message from NUT
        5. SERVER0 sends Reply Message to NUT
        6. SERVER0 sends Echo Request
        7. SERVER0 receives Echo Reply
        8. NUT reboots
        9. SERVER0 receives Renew Message from NUT
        10. SERVER0 sends Reply Message to NUT
        11. SERVER0 receives Request Message from NUT
        12. SERVER0 sends Reply to NUT

JUDGEMENT

(*1) PASS: SERVER0 receives Solicit Message  (not checking the options in Solicit Message)
(*2) PASS: SERVER0 receives Request Message  (not checking the options in Request Message)
(*3) PASS: SERVER0 receives Echo Reply
(*4) PASS: SERVER0 receives Renew Message
(*5) PASS: SERVER0 receives Request Message

REFERENCE

<draft-ietf-dhc-dhcpv6-28.txt>

18.1.3. Creation and Transmission of Renew Messages

   To extend the valid and preferred lifetimes for the addresses
   associated with an IA, the client sends a Renew message to the server
   from which the client obtained the addresses in the IA containing
   an IA option for the IA. The client includes IA Address options in
   the IA option for the addresses associated with the IA. The server
   determines new lifetimes for the addresses in the IA according to the
   administrative configuration of the server.  The server may also add
   new addresses to the IA. The server may remove addresses from the IA
   by setting the preferred and valid lifetimes of those addresses to
   zero.

   The server controls the time at which the client contacts the server
   to extend the lifetimes on assigned addresses through the T1 and T2
   parameters assigned to an IA.

   At time T1 for an IA, the client initiates a Renew/Reply message
   exchange to extend the lifetimes on any addresses in the IA. The
   client includes an IA option with all addresses currently assigned to
   the IA in its Renew message.

   If T1 or T2 is set to 0 by the server (for an IA_NA) or there are no
   T1 or T2 times (for an IA_TA), the client may send a Renew or Rebind
   message, respectively, at the client's discretion.

   The client sets the "msg-type" field to RENEW. The client generates a
   transaction ID and inserts this value in the "transaction-id" field.

   The client places the identifier of the destination server in a
   Server Identifier option.

   The client MUST include a Client Identifier option to identify
   itself to the server.  The client adds any appropriate options,
   including one or more IA options.  The client MUST include the list
   of addresses the client currently has associated with the IAs in the
   Renew message.

   The client MUST include an Option Request option (see section 22.7)
   to indicate the options the client is interested in receiving.  The
   client MAY include options with data values as hints to the server
   about parameter values the client would like to have returned.

   The client transmits the message according to section 14, using the
   following parameters:

      IRT   REN_TIMEOUT

      MRT   REN_MAX_RT

      MRC   0

      MRD   Remaining time until T2

   The message exchange is terminated when time T2 is reached (see
   section 18.1.4), at which time the client begins a Rebind message
   exchange.

18.1.8. Receipt of Reply Messages

   When the client receives a NoBinding status in an IA from the server
   in response to a Renew message or a Rebind message, the client sends
   a Request to reestablish an IA with the server.