DHCPv6 Message Format
 
   
  The DHCPv6 message format varies from the DHCPv4 message format. This section describes the events that occur when a DHCPv6 client sends a Solicit message to locate DHCPv6 servers. 
  
		
Note   
The 
show ipv6 dhcp relay
				statistics command does not display the packet count in the statistics for
			DHCPv6 Advertise and Reconfigure messages, because it is sent from the DHCPv6 server to
			DHCPv6 client directly, not through the relay server. 
 
		
			
				- Solicit (1)
 
				- A DHCPv6 client sends a Solicit message to locate DHCPv6 servers. 
 
			
			
				- Advertise (2)
 
				- A server sends an Advertise message to indicate that it is available for DHCP
					service, in response to a Solicit message received from a client.
 
			
			
				- Request (3)
 
				- A client sends a Request message to request configuration parameters, including
					IP addresses or delegated prefixes, from a specific server.
 
			
			
				- Confirm (4)
 
				- A client sends a Confirm message to any available server to determine whether
					the addresses it was assigned are still appropriate to the link to which the
					client is connected. This could happen when the client detects either a
					link-layer connectivity change or if it is powered on and one or more leases are
					still valid. The confirm message confirms whether the client is still on the
					same link or whether if it has been moved. The actual leases are not validated,
					only the prefix portion of the addresses or delegated prefixes.
 
			
			
				- Renew (5)
 
				- A client sends a Confirm message to any available server to determine whether
					the addresses it was assigned are still appropriate to the link to which the
					client is connected. This could happen when the client detects either a
					link-layer connectivity change or if it is powered on and one or more leases are
					still valid. The confirm message confirms whether the client is still on the
					same link or whether it has been moved. The actual leases are not validated,
					only the prefix portion of the addresses or delegated prefixes.
 
			
			
				- Rebind (6)
 
				- A client sends a Rebind message to any available server to extend the lifetimes
					on the addresses assigned to the client and to update other configuration
					parameters. This message is sent after a client receives no response to a Renew
					message. 
 
			
			
				- Reply (7)
 
				- A server sends a Reply message containing assigned addresses and configuration
					parameters in response to a Solicit, Request, Renew, or Rebind message received
					from a client. A server sends a Reply message containing configuration
					parameters in response to an Information-request message. A server sends a Reply
					message in response to a Confirm message confirming or denying that the
					addresses assigned to the client are appropriate to the link to which the client
					is connected. A server sends a Reply message to acknowledge receipt of a Release
					or Decline message. 
 
			
			
				- Release (8)
 
				- A client sends a Release message to the server that assigned addresses to the
					client to indicate that the client is not using one or more of the assigned
					addresses. 
 
			
			
				- Decline (9)
 
				- A client sends a Decline message to a server to indicate that the client has
					determined that one or more addresses assigned by the server are already in use
					on the link to which the client is connected.
 
			
			
				- Reconfigure (10)
 
				- A server sends a Reconfigure message to a client to inform the client that the
					server has new or updated configuration parameters. The client needs to initiate
					a Renew/Reply or Information-request/Reply transaction with the server in order
					to receive the updated information.
 
			
			
				- Information-request (11)
 
				- A client sends an Information-request message to a server to request
					configuration parameters without the assignment of any IP addresses to the
					client. 
 
			
			
				- Relay-forward (12)
 
				- A relay agent sends a Relay-forward message to relay messages to servers, either
					directly or through another relay agent. The received message, either a client
					message or a Relay-forward message from another relay agent, is encapsulated in
					an option in the Relay-forward message. 
 
			
			
				- Relay-reply (13)
 
				- A server sends a Relay-reply message to a relay agent containing a message that
					the relay agent delivers to a client. The Relay-reply message may be relayed by
					other relay agents for delivery to the destination.
 
			
		
 
	 Table 1. DHCPv4 message versus DHCPv6 messageThe table lists the DHCPv4 and DHCPv6 message types: 
	  
		   
			 | DHCPv6 message type 
			  |  
			 DHCPv4 message type 
			  |  
		  
 
		   
			 | Solicit (1) 
			  |  
			 DHCPDISCOVER 
			  |  
		  
 
		   
			 | Advertise (2) 
			  |  
			 DHCPOFFER 
			  |  
		  
 
		   
			 | Request (3), Renew (5), Rebind (6) 
			  |  
			 DHCPREQUEST 
			  |  
		  
 
		   
			 | Reply (7) 
			  |  
			 DHCPPACK/DHCPNAK 
			  |  
		  
 
		   
			 | Release (8) 
			  |  
			 DHCPRELEASE 
			  |  
		  
 
		   
			 | Information-Request (11) 
			  |  
			 DHCPINFORM 
			  |  
		  
 
		   
			 | Decline (9) 
			  |  
			 DHCPDECLINE 
			  |  
		  
 
		   
			 | Confirm (4) 
			  |  
			 None 
			  |  
		  
 
		   
			 | Reconfigure (10) 
			  |  
			 DHCPFORCERENEW 
			  |  
		  
 
		   
			 | Relay-Forward(12), Relay-Reply (13) 
			  |  
			 None 
			  |