NAME

  C_RFC3315_18_1_1_ReqRetransRT.seq - Check RT of Request

TARGET

  Client

SYNOPSIS

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


  See Also  DHCPv6.def

INITIALIZATION

Network Topology

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

Verification Points

   The client transmits the message using the following parameters:

   IRT   REQ_TIMEOUT

   MRT   REQ_MAX_RT

   MRC   REQ_MAX_RC

   MRD   0

   The RT should comforms to the following.
		      
      RT = IRT + RAND*IRT

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 (3*)
        |       |
        |       |Waiting until retransmitted Request arrives
        |       |
        | ----> |Request (4*)
        |       |

JUDGEMENT

  (3*)PASS: TN receives the first Request from NUT.
  (4*)PASS: TN receives the second retransmitted Request from NUT.
            And the interval conforms to Verification Points.

TERMINATION

N/A

REFERENCE

  Also see RFC3315

  
  18.1.1. Creation and Transmission of Request Messages