NAME

  C_RFC3315_21.4.4.1_SendSolicit.seq - Sending Solicit (with a Rapid) message

TARGET

  Client

SYNOPSIS

   C_RFC3315_21.4.4.1_DelayedAuthProto.seq [-tooloption...]
  -pkt   C_RFC3315_21.4.4.1_DelayedAuthProto.def
  -tooloption : v6eval tool option


  See Also  DHCPv6.def

INITIALIZATION

Network Topology

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

Verification Points

  When the client sends a Solicit message and wishes to use
  authentication, it includes an Authentication option with the desired
  protocol, algorithm and RDM. The client does not include any replay 
  detection or authentication information in the Authentication option.

Configurations

DHCP realm: DHCPv6.TEST.EXAMPLE.COM
Client DUID: ANY
Key id: 1
Shared secret key: TAHITEST_VALID12

`Device Name`	`Device Type`	`Interface`	`Address`	`Link Local Addr`	`MAC Addr`
`Client`	`NUT`	`Link0`		`NUT's Linklocal address`	`NUT's MAC address`
`Server`	`TN`	`Link0`	`3ffe:501:ffff:100:200:ff:fe00:a1a1`	`fe80::200:ff:fe00:a1a1`	`00:00:00:00:a1:a1`

TEST PROCEDURE

       NUT      TN
        |       |
        |       |Initialize NUT (as a DHCPv6 client)
        |       |
        | ----> |Solicit w/ Authentication Option (1*)
        | <---- |Reply w/ Authentication Option
        |       |
        | <---- |Echo Request
        | ----> |Echo Reply (4*)
        |       |

JUDGEMENT

  (1*)PASS: TN receives Solicit w/ Authentication Option from NUT.
  (4*)PASS: NUT should send Echo Reply to TN.

TERMINATION

N/A

REFERENCE

   see also RFC3315
   21.4.4 Client Considerations for Delayed Authentication protocol
   21.4.4.1. Sending Solicit Messages
   22.11 Authentication Option