NAME

  C_RFC3315_21.5.3_ReconfigAuthInfoRepInvalid.seq - Information-Request/Reply Exchange finished, Receiving Reconfigure Message and validation test is failed 

TARGET

  Client

SYNOPSIS

   C_RFC3315_21.5.3_ReconfigAuthInfoRepInvalid.seq [-tooloption...] -pkt   C_RFC3315_21.5.3_ReconfigAuthInfoRepInvalid.def -tooloption : v6eval tool option


  See Also  DHCPv6.def  

INITIALIZATION

• Network Topology

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

• Verification Points



   The client will receive a Reconfigure Key from the server in the
   initial Reply message from the server.  The client records the
   Reconfigure Key for use in authenticating subsequent Reconfigure
   messages.
   

   To authenticate a Reconfigure message, the client computes an
   HMAC-MD5 over the DHCP Reconfigure message, using the Reconfigure Key
   received from the server.  If this computed HMAC-MD5 matches the
   value in the Authentication option, the client accepts the
   Reconfigure message. 
    

• Configurations



    Enable Reconfigure Key Authenticaion Protocol Service
    

    

    

    
Device Name
    
Device Type
    
Interface
    
Assigned Prefix
    
Link Local Addr
    
MAC Addr
    
    

    
Client
    
NUT
    
Link0
    
3ffe:501:ffff:101::/64
    
NUT's Linklocal address
    
NUT's MAC address
    
    

    
Server
    
TN
    
Link0
    
3ffe:501:ffff:101::/64
    
fe80::200:ff:fe00:a1a1
    
00:00:00:00:a1:a1
    
    
    

TEST PROCEDURE

       NUT     TN
        |       | 
        |       | Initialize NUT (as a DHCPv6 client)
        |       | 
        | ----> | Information-Request w/Authentication Accept Option
        |       | and Option Request Option(Preference Option)(*1)
        | <---- | Reply with Authentication Option and Preference Option(10)
        |       | 
        |       | Preference changed from 10 to 20
        |       | Reload server configuration 
        |       | 
        | <---- | Reconfigure with w/Invalid Authentication Option(Value field is invalid)
        |       | w/Reconfigure Message Option(msg-type=11) 
        |       | 
        | --> X | Information-Request with Option Request Option(Preference Option) (*4)
        |       | 

JUDGEMENT

 (*1) PASS: TN receive Information-Request message with Authenticaion Accept option and 
            Option Request Option(Preference Option).
 (*4) PASS: TN does not receive Information-Request with Option Request Option(Preference Option).

TERMINATION

  N/A

REFERENCE

   see also RFC3315
   19.4.2. Creation and Transmission of Renew Messages
   21.5. Reconfigure Key Authentication Protocol
   21.5.3. Client considerations for Reconfigure Key protocol

SEE ALSO

  perldoc  V6evalTool