NAME

  C_RFC3315_6_CltMsgFormat.seq - Check the format of Client DHCPv6 message

TARGET

  Client

SYNOPSIS

   C_RFC3315_6_CltMsgFormat.seq [-tooloption...] 
  -pkt  C_RFC3315_6_CltMsgFormat.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 following diagram illustrates the format of DHCPv6 message form 
   client.
   
       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |    msg-type   |               transaction-id                  |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                                                               |
      .                            options                            .
      .                           (variable)                          .
      |                                                               |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    
    msg-type is SOLICIT(1)
    transaction-id 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*)
        |       | 
        |       |

JUDGEMENT

  (1*)PASS: TN receives Solicit from NUT.

TERMINATION

N/A

REFERENCE

  See also RFC3315


  6 Client/Server Message Formats