DHCPV6 Messages

1. DHCP :: DHCP REQUESTRenewal Messages
This suitecontains testcases for DHCPREQUESTRenewal messages,sent byDHCPclients during theRENEWING state.In this state, theclient's
renewaltimer has expired, indicating thattheclient's IP address leaseis expiring soon. To renew theIP address lease, the clientsends a
DHCPREQUEST Renewalmessageto theserverthat granted thelease,transitions to theREQUESTING state,and waits for a reply from that
server.
A DHCPREQUESTRenewalmessagecontains theserveridentifier (hostname, domainname, or IPaddress) ofthe DHCP server that granted the
leaseand a RequestedIP Address option thatspecifies theIPaddress currentlyassignedto the client. Themessagecan also contain other
options,such as anIP Address LeaseTimeoption thatspecifies the number ofseconds theclientis requesting for thelease duration.For a valid
DHCPREQUEST Renewalmessage, thereceiving DHCPserver eitherrenews theclient's IP address lease andsends a DHCPACK
(acknowledgement) reply, orrefuses to renew the lease andsends a DHCPNAK (negativeacknowledgement) reply.
DHCP :: DHCP REQUESTRequestMessages
This suitecontains testcases for DHCPREQUESTRequest messages, sent by DHCPclients during theSELECTING state.In this state,theclienthas
received oneor moreDHCPOFFER messages from DHCP server and mustselect oneoftheoffered IPaddress leases. To inform allservers ofthe
selectedoffer,theclient broadcasts a DHCPREQUESTRequest messagetothelocalnetwork,transitions totheREQUESTING state,and waits for
a reply from theselected server.
A DHCPREQUESTRequestmessagecontains theserver identifier (hostname, domainname, or IPaddress) ofthe DHCP serverthat offered the
accepted IPaddress leaseand a Requested IP Address option that specifies andconfirms the IPaddress assignedto the client inthepreceding
DHCPOFFER message. The message canalso contain other options that specify additionalsettings, suchas a Parameter Request List option that
requests configuration parameters fromtheserver.
All receiving DHCP servers use the server identifier valueto determineiftheir IPaddress leasewas acceptedby theclient:
If the serveridentifiervaluedoes not matchtheidentifier(host name, domain name, orIP address) ofthereceiving server, theserver considers
the IP address leaserejectedand takes no furtheraction.
If the serveridentifiervaluematches theidentifierofthe receiving server,theIP address lease offeredby thatserver has beenacceptedby the
client. Fora valid DHCPREQUESTRequest message,theselected serverreturns a DHCPNAK(negativeacknowledgement) or DHCPACK
(acknowledgement) reply.
Each testcaseinthis suiteinitiates thefollowing message exchangesequenceduring an analysis:
The DHCP client(theMu appliance) sends a DHCPDISCOVER message totheDHCP server(the analysis Target) andwaits for thecorresponding
DHCPOFFER reply.
After receiving the reply, theclient sends a mutatedDHCPREQUESTRequestmessageto theserverand waits for a DHCPACKreply.
Whether ornot a replyis received, the client sends a validDHCPRELEASEand a validDHCPDECLINEmessageto releasetheIP address lease.
DHCPv6 :: DHCPv6 SOLICITMessages
This suitecontains testcases for DHCP SOLICITmessages, used by DHCPclients thatdo not haveanIP address and do not know thelocationof
a DHCP serveron thenetwork.To locate a server andobtain an IPaddress,a clientsends a SOLICITmessageto the multicast address
All_DHCP_Relay_Agents_and_Servers (FF02::1:2) andwaits for a reply froma DHCPserver. Theclientspecifies thetype ofaddress it wants to
receiveby creating anIdentity Association (IA) for thattypeand assigning each IAan Identity Association Identifier(IAID). In the SOLICIT
message,theclient places theIAs for which itwants toobtain an IPv6 address withinan IAOptions option. For a valid SOLICITrequest, the
server returns anADVERTISEmessage.
A valid DHCP SOLICITmessageuses a MessageTypeof1 and contains thefollowing options:
Client IdentifierOption. Specifies the DUID for the clientidentifierassociatedwith thesending DHCP client.
IAOptions. Specify theIdentity Associations andaddresses assigned totheinterfacefor which the client wants to obtainanIPv6address.
Option Request Options. Specify theDHCPv6options theclientwants to receivefrom theserver.
ReconfigureAcceptOption.Specifies whether or not the clientcan accept Reconfiguremessages fromtheserver.
Each testcaseinthis suiteinitiates thefollowing message exchangesequenceduring an analysis: TheDHCPclient (the Mu appliance) sends a
mutatedSOLICITmessageto theDHCP server(theanalysis Target) and waits for thecorresponding ADVERTISEreply. Becausethe client does
not return an REQUESTmessage totheadvertising server, the IPleaseis notactually granted,and does notneed tobe declined or released.
DHCPv6 :: DHCPv6 REQUESTMessages
This suitecontains testcases for DHCP REQUESTmessages,usedby DHCPclientto populateIdentityAssociations (IAs) with IP addresses and to
obtain configuration information.For valid REQUESTmessages,theserver returns a REPLYmessagethatcontains IAoptions specifying
addresses and other IAconfiguration data.
A valid DHCP REQUESTmessage uses a MessageType of3 and contains the following options:
Client IdentifierOption. Specifies the DUID for the clientidentifierassociatedwith thesending DHCP client.
Server Identifier Option.Specifies theDUID for theserver identifier associatedwith the destination DHCPserver.
IAOptions. Specify that the client wants thereceiving serverto assign theclientoneor morenetwork addresses.
Option Request Options. Specify theDHCPv6options theclientwants to receivefrom theserver.
ReconfigureAcceptOption.Specifies whether or not the clientcan accept Reconfiguremessages fromtheserver.
Each testcaseinthis suiteinitiates thefollowing message exchangesequenceduring an analysis:
The DHCP client(theMu appliance) sends a valid SOLICITmessage tothe DHCPserver (the analysis Target) andwaits for the corresponding
ADVERTISEreply.
After receiving the ADVERTISEreply, the client sends a mutated REQUESTmessageto theserverand waits for a REPLYmessage.
Becausethe client does notsend an CONFIRMmessageto the advertising server, theIP leaseis not actually granted, and does not needto be
declined or released.

2. DHCPv6 :: DHCPv6 RENEW Messages
This suitecontains testcases for DHCP RENEW messages, used byDHCPclients whentheirrenewaltimer has expired, indicating that the
client's IP address leaseis expiring soon.To renew theIP address lease, the client sends a DHCPRENEW message to theserver that grantedthe
leaseand waits for a reply from thatserver.For a validDHCPRENEW message, the receiving DHCPserver either renews theclient's IP address
leaseand sends a REPLY(acknowledgement). Iftheclient does notreceivea REPLY, it sends a REBINDmessageto themulticastaddress
All_DHCP_Relay_Agents_and_Servers (FF02::1:2) andwaits for a REPLYmessagefromoneor more servers.
A valid DHCP RENEW messageuses a Message Typeof5 and contains thefollowing options:
Client IdentifierOption. Specifies the DUID for the clientidentifierassociatedwith thesending DHCP client.
Server Identifier Option.Specifies theDUID for theserver identifier associatedwith the destinationDHCPserver.
IAOptions. Specify theIdentity Associations andaddresses assigned totheinterfacethat holds theIP address lease.
Option Request Options. Specify theDHCPv6options theclientwants to receivefrom theserver.
Each testcaseinthis suiteinitiates thefollowing message exchangesequenceduring an analysis:
The DHCP client(theMu appliance) sends a valid SOLICITmessage totheDHCPserver (the analysis Target) andwaits for the corresponding
ADVERTISEreply.
After receiving the ADVERTISEreply, the client sends a valid REQUESTmessageto theserverandwaits for a REPLYmessage.
After receiving the REPLY, the client sends a mutated RENEW message totheserver andwaits for a REPLYmessage.
DHCPv6 :: DHCPv6 RELEASEMessages
This suitecontains testcases for DHCP RELEASEmessages, used by DHCP clients to release an existing IP address lease. To terminatetheIP
address leasebefore itexpires,theclient sends a DHCPRELEASEmessage totheserver that grantedthelease. Aclient might needto end a
leaseearly when the host deviceis moving to a different network, to accommodatea new network numbering implementation, or toobtain a
new leasefrom a different server. For a valid DHCP RELEASEmessages,thereceiving DHCP server considers the IPaddress leaseas ended,un-
allocates that IPaddress, and returns a REPLYto the client.
A valid DHCP RELEASEmessageuses a MessageType of8 andcontains thefollowing options:
Client IdentifierOption. Specifies the DUID for the clientidentifierassociatedwith thesending DHCP client.
Server Identifier Option.Specifies theDUID for theserver identifier associatedwith the destinationDHCPserver.
IAOptions. Specify theIdentity Associations andaddresses that theclients wants to release.
Each testcaseinthis suiteinitiates thefollowing message exchangesequenceduring an analysis:
The DHCP client(theMu appliance) sends a valid SOLICITmessage totheDHCPserver (the analysis Target) andwaits for the corresponding
ADVERTISEreply.
After receiving the ADVERTISEreply, the client sends a valid REQUESTmessageto theserverandwaits for a REPLYmessage.
After receiving the REPLY, the client sends a mutated RELEASEmessageto terminatetheIP address lease andwaits for a REPLY message.
The clientsends a valid RELEASEmessage toterminate the IPaddress leaseand waits for a REPLYmessage.
DHCPv6 :: DHCPv6 REBINDMessages
This suitecontains testcases for DHCP REBIND messages, used by DHCP clients to obtaina new IPaddress leasewhen attempts torenewan
existing leasefail.When a client's renewal timer expires, theclientfirst sends a RENEW message totheserver (unicast) that grantedthe
existing lease; if theclientdoes not receivea REPLYfrom thatserver,it thensends a REBIND message tothemulticast address
All_DHCP_Relay_Agents_and_Servers (FF02::1:2) andwaits for a REPLYmessagefromoneor more servers. Avalid DHCPREBIND message uses
a Message Typeof6 and contains thefollowing options:
Client IdentifierOption. Specifies the DUID for the clientidentifierassociatedwith thesending DHCP client.
IAOptions. Specify theIdentity Associations andaddresses ofinterfaces for which the client wants to obtainnewIP leases.
Option Request Options. Specify theDHCPv6options theclientwants to receivefrom theserver.
Each testcaseinthis suiteinitiates thefollowing message exchangesequenceduring an analysis:
The DHCP client(theMu appliance) sends a valid SOLICITmessage totheDHCPserver (the analysis Target) andwaits for the corresponding
ADVERTISEreply.
After receiving the ADVERTISEreply, the client sends a valid REQUESTmessageto theserverandwaits for a REPLYmessage.
After receiving the REPLY, the client sends a mutated REBIND messageto the server and waits for a REPLYmessage.
DHCPv6 :: DHCPv6 INFORMATION-REQUESTMessages
This suitecontains testcases for DHCP INFORMATION-REQUESTmessages, usedby DHCP clients or servers that wantto obtainconfiguration
parameters from other DHCP servers on thenetwork but do not wantto obtainanIP address lease.To obtain theseparameters, the sender
(client or server) cansenda multicastrequest to allDHCP servers on thenetwork or toa singleserver:
When the sender does notknow thelocation ofa DHCPserver, it multicasts the DHCPINFORMATION-REQUESTmessageto themulticast
address All_DHCP_Relay_Agents_and_Servers (FF02::1:2) andwaits for a reply fromany availableserver.
When the sender knows theidentity and address ofa DHCP server, itunicasts the DHCP INFORMATION-REQUESTmessageto a specific server
and waits for that serverto senda reply.
For a valid DHCPINFORMATION-REQUESTmessage, a receiving DHCP server sends a REPLYthat contains an OptionRequestOption withthe
requestedparameters (or defaultparameters,when nonewerespecified intherequest). AvalidDHCPINFORMATION-REQUESTmessage usesa
MessageType of11and contains thefollowing options:
Client IdentifierOption. Specifies the DUID for the clientidentifierassociatedwith thesending DHCP client.
Server Identifier Option (Unicast Only). Specifies theDUID for theserveridentifier associated withthedestination DHCP server.
Option Request Options. Specify theDHCPv6options theclientwants to receivefrom theserver.
For each testcase inthis suite, the DHCPclient (theMu appliance) sends a INFORMATION-REQUESTmessage totheDHCPserver (the analysis
Target) and waits for thecorresponding REPLY(acknowledgement).Because noIP address leaseis grantedor renewed, theclient does not
need to send a RELEASEor DECLINEmessageto releasethe IPaddress lease.

3. DHCPv6 :: DHCPv6 DECLINEMessages
This suitecontains testcases for DHCP DECLINEmessages, used by DHCPclients to declineanadvertisedIP address lease. After theclient
accepts an IP address leaseoffer, itverifies thattheoffered IPaddress is not currentlyin use. To inform theservers that the client is refusing an
offer becausetheIP address is alreadyin use, theclientsends a DHCP DECLINEmessageto the server (unicast), andwaits for a reply.For a valid
DHCP DECLINEmessages,thereceiving DHCP serverconsiders the IPaddress as unavailable.
A valid DHCP DECLINEmessageuses a MessageTypeof9 andmustcontainthefollowing options:
Client IdentifierOption. Specifies the DUID for the clientidentifierassociatedwith thesending DHCP client.
Server Identifier Option.Specifies theDUID for theserver identifier associatedwith the destinationDHCPserver.
IAOptions. Specify theIdentity Associations andaddresses that theclientis declining
Each testcaseinthis suiteinitiates thefollowing message exchangesequenceduring an analysis:
The DHCP client(theMu appliance) sends a valid SOLICITmessage totheDHCPserver (the analysis Target) andwaits for the corresponding
ADVERTISE reply.
After receiving the ADVERTISEreply, the client sends a valid REQUESTmessageto theserverandwaits for a REPLYmessage.
After receiving the REPLY, the client sends a mutated DECLINEmessage totheserver and waits for a REPLYmessage.
The clientsends a mutated DECLINEmessageto terminatetheIP address lease and waits for a REPLYmessage.
DHCPv6 :: DHCPv6 CONFIRMMessages
This suitecontains testcases for DHCP CONFIRMmessages, usedby DHCP clients to confirmacceptance ofan advertisedIP address lease.After
the client accepts anIP address lease offer, itverifies that theoffered IP address is not currently inuse.To informthe server that the client has
confirmed that the offeredIP address is notin useand is accepting theoffered lease, theclientsends a DHCP CONFIRMmessageto the
multicast address All_DHCP_Relay_Agents_and_Servers (FF02::1:2) and waits for a reply. Fora valid DHCP CONFIRMmessages, thereceiving
DHCP server considers theIP address as allocated to theclient.
A valid DHCP CONFIRMmessageuses a MessageType of4 and must contain the following options:
Client IdentifierOption. Specifies the DUID for the clientidentifierassociatedwith thesending DHCP client.
Server Identifier Option.Specifies theDUID for theserver identifier associatedwith the destinationDHCPserver.
IAOptions. Specify theIdentity Associations andaddresses assigned totheinterfaceaccepting theIP address lease.
Each testcaseinthis suiteinitiates thefollowing message exchangesequenceduring an analysis:
The DHCP client(theMu appliance) sends a valid SOLICITmessage totheDHCPserver (the analysis Target) andwaits for the corresponding
ADVERTISEreply.
After receiving the ADVERTISEreply, the client sends a valid REQUESTmessageto theserverandwaits for a REPLYmessage.
After receiving the REPLY, the client sends a mutated CONFIRMmessageto the server and waits for a REPLYmessage.
The clientsends a valid RELEASEmessage toterminate the IPaddress leaseand waits for a REPLYmessage.