NAME

  S_RFC3315_21.4.5.1_SolAdv.seq - Receiving solicit messages and sending advertise messages

TARGET

  Server

SYNOPSIS

  S_RFC3315_21.4.5.1_SolAdv.seq [-tooloption ...] -pkt S_RFC3315_21.4.5.1_SolAdv.def  -tooloption: v6eval tool option
See Also  DHCPv6.def 
 

INITIALIZATION

• Network Topology

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

• Verification Points

  The server selects a key for the client and includes authentication
  information in the Advertise message returned to the client as
  specified in section 21.4.  The server MUST record the identifier of
  the key selected for the client and use that same key for validating
  subsequent messages with the client.
  

• Configuration



Enable Delayed Authenticaion Protocol Service
Authenticaion parameter:
• DHCP realm: DHCPv6.TEST.EXAMPLE.COM
• Client DUID: 00:01:00:01:00:04:93:e0:00:00:00:00:a2:a2
• Key id: 1
• Shared secret key: TAHITEST_VALID12



Device Name	Device Type	I/F	Assigned Prefix	Link Local Addr	MAC Addr
Server1	NUT	Link0	3ffe:501:ffff:100::/64	NUT's Linklocal address	NUT's MAC address
Client1	TN	Link0	3ffe:501:ffff:100::/64	fe80::200:ff:fe00:a2a2	00:00:00:00:a2:a2

TEST PROCEDURE

       NUT     TN
        |       | 
        |       | initialize NUT (as a DHCPv6 Server)
        |       | 
        | <---- | Solicit w/ Authtication Option
        | ----> | Advertise w/ Authtication Option
        | <---- | Request w/ Authtication Option
        | ----> | Reply w/ Authtication Option using key as same as Advertise (*1)
        |       | 

JUDGEMENT

  (*1) PASS: NUT MUST use that same key for validating subsequest messages with the client.

TERMINATION

REFERENCE

  see also RFC3315
  21.4.5 Server Considerations for Delayed Authentication protocol
  21.4.5.1. Receiving Solicit Messages and Sending Advertise Messages
  22.11 Authentication Option

SEE ALSO