NAME

  S_RFC3315_BasicInfoReqRep.seq - Basic Infomation-request/Reply Messages Exchange

TARGET

  Server

SYNOPSIS

 S_RFC3315_BasicInfoReqRep.seq [-tooloption ...]
 -pkt S_RFC3315_BasicInfoReqRep.def 
 -tooloption: v6eval tool option
See Also  DHCPv6.def

INITIALIZATION

Network Topology

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

Verification Points

Reply Message Format
      msg-type
          REPLY(7)
      transaction-id
	  Any

Configuration

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)
        |       | 
        | <---- | Information Request 
        | ----> | Reply   (*1)
        |       |

JUDGEMENT

<PRE> (*1) PASS: TN receives Reply Message (not checking the options in Reply Message) </PRE>

TERMINATION

N/A

REFERENCE

   see also RFC3315
   5.3. DHCP Message Types   [Page 14 Line 748]
   6. Client/Server Message Formats

`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`