Please Whitelist This Site?

I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :)

If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads.

If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK.

Thanks for your understanding!

Sincerely, Charles Kozierok
Author and Publisher, The TCP/IP Guide


NOTE: Using software to mass-download the site degrades the server and is prohibited.
If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.

The Book is Here... and Now On Sale!

The whole site in one document for easy reference!
The TCP/IP Guide

Custom Search







Table Of Contents  The TCP/IP Guide
 9  TCP/IP Application Layer Protocols, Services and Applications (OSI Layers 5, 6 and 7)
      9  TCP/IP Network Configuration and Management Protocols (BOOTP, DHCP, SNMP and RMON)
           9  Host Configuration and TCP/IP Host Configuration Protocols (BOOTP and DHCP)
                9  TCP/IP Dynamic Host Configuration Protocol (DHCP)

Previous Topic/Section
DHCP Security Issues
Previous Page
Pages in Current Topic/Section
1
2
Next Page
TCP/IP Network Management Framework and Protocols (SNMP and RMON)
Next Topic/Section

DHCP For IP Version 6 (DHCPv6)
(Page 2 of 2)

DHCPv6 Operation Overview

The operation of DHCPv6 is similar to that of DHCPv4, but the protocol itself has been completely rewritten. It is not based on the older DHCP or on BOOTP, except in conceptual terms. It still uses UDP but uses new port numbers, a new message format, and restructured options. All of this means that the new protocol is not strictly compatible with DHCPv4 or BOOTP, though I believe work is underway on a method to allow DHCPv6 servers to work with IPv4 devices.

Key Concept: Since DHCP works with IP addresses and other configuration parameters, the change from IPv4 to IPv6 requires a new version of DHCP commonly called DHCPv6. This new DHCP represents a significant change from the original DHCP, and is still under development. DHCPv6 is used for IPv6 “stateful” autoconfiguration; the alternative is stateless autoconfiguration, a feature of IPv6 that allows a client to determine its IP address without need for a server.


DHCPv6 is also oriented around IPv6 methods of addressing, especially the use of link-local scoped multicast addresses. This allows efficient communication even before a client has been assigned an IP address. Once a client has an address and knows the identity of a server it may communicate with the server directly using unicast addressing.

DHCP Message Exchanges

There are two basic client/server message exchanges that are used in DHCPv6: the four-message exchange and the two-message exchange. The former is used when a client needs to obtain an IPv6 address and other parameters. This process is similar to the regular DHCP address allocation process; highly simplified, it involves these steps:

  1. The client sends a multicast Solicit message to find a DHCPv6 server and ask for a lease.

  2. Any server that can fulfill the client's request responds to it with an Advertise message.

  3. The client chooses one of the servers and sends a Request message to it asking to confirm the offered address and other parameters.

  4. The server responds with a Reply message to finalize the process.

There is also a shorter variation of the four-message process above, where a client sends a Solicit message and indicates that a server should respond back immediately with a Reply message.

If the client already has an IP address, either assigned manually or obtained in some other way, a simpler process can be undertaken, similar to how in regular DHCP the DHCPINFORM message is used:

  1. The client multicasts an Information-Request message.

  2. A server with configuration information for the client sends back a Reply message.

As in regular DHCP, a DHCPv6 client renews its lease after a period of time by sending a Renew message. DHCPv6 also supports relay agent functionality as in DHCPv4.

 


Previous Topic/Section
DHCP Security Issues
Previous Page
Pages in Current Topic/Section
1
2
Next Page
TCP/IP Network Management Framework and Protocols (SNMP and RMON)
Next Topic/Section

If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support!
Donate $2
Donate $5
Donate $10
Donate $20
Donate $30
Donate: $



Home - Table Of Contents - Contact Us

The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005

© Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.