NAME

  C_RFC3315_10_CltIAIDFormat.seq - Check the consistence of DHCPv6 Client`s IAID

TARGET

  Client

SYNOPSIS

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


  See Also  DHCPv6.def

INITIALIZATION

Network Topology

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

Verification Points

   An "identity-association" (IA) is a construct through which a server
   and a client can identify, group, and manage a set of related IPv6
   addresses.  Each IA consists of an IAID and associated configuration
   information.The IAID uniquely identifies the IA and must be chosen to
   be unique among the IAIDs on the client.  The IAID is chosen by the
   client. For any given use of an IA by the client, the IAID for that IA
   MUST be consistent across restarts of the DHCP client.

   IA_NA option includes IAID. So check the consistence of IAID field of
   IA_NA option after client reboots.
   
    option-code is OPTION_IA_NA(3) 
    IAID is ANY Non-zero number

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 (1*)
        |       | 
        |       |Reboot  NUT
        |       |
        | ----> |Solicit (2*)
        |       |

JUDGEMENT

  (2*)PASS: the value of IAID should be same with that of (1*).

TERMINATION

N/A

REFERENCE

  Also see RFC3315
  10. Identity Association
  22.4. Identity Association for Non-temporary Addresses Option