NAME

  C_RFC3315_17_1_3_MAdv.seq - Test when receiving mulitple Advertises from mutiple DHCPv6 servers

TARGET

  Client

SYNOPSIS

   C_RFC3315_17_1_3_MAdv.seq [-tooloption...] 
  -pkt  C_RFC3315_17_1_3_MAdv.def 
  -tooloption : v6eval tool option
  See Also  DHCPv6.def

INITIALIZATION

Network Topology

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

Verification Points

   Upon receipt of one or more valid Advertise messages, the client
   selects one or more Advertise messages based upon the following
   criteria.

   -  Those Advertise messages with the highest server preference value
      are preferred over all other Advertise messages. 

   -  Within a group of Advertise messages with the same server
      preference value, a client MAY select those servers whose
      Advertise messages advertise information of interest to the
      client.  For example, the client may choose a server that returned
      an advertisement with configuration options of interest to the
      client.

   -  The client MAY choose a less-preferred server if that server has a
      better set of advertised parameters, such as the available
      addresses advertised in IAs. 

   Once a client has selected Advertise message(s), the client will
   typically store information about each server, such as server
   preference value, addresses advertised, when the advertisement was
   received, and so on. 

   If the client needs to select an alternate server in the case that a
   chosen server does not respond, the client chooses the next server
   according to the criteria given above.

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 w/ Preference option/0 
        |       |
        | <---- |Advertise w/ Preference option/255 
        |       |
        | ----> |Request (4*) 
        |       |
        |       |waiting till the time of retransmission reaches the MRC
        |       |
        | ----> |Request (5*)
        |       |

JUDGEMENT

  (4*)PASS: NUT sends Request to Server with higher Preference.
  (5*)PASS: NUT sends Request to Server with lower Prference.

TERMINATION

N/A

REFERENCE

  Also see RFC3315


  17.1.3. Receipt of Advertise Messages