Multicast Address Dynamic Client Allocation Protocol Explained

The Multicast Address Dynamic Client Allocation Protocol (MADCAP) is a communication protocol that allows hosts to request multicast addresses from a server.[1] [2] [3]

Overview

The Multicast Address Dynamic Client Allocation Protocol (MADCAP) is designed to allow for automatic dynamic assignment of multicast addresses.[4]

MADCAP allows for efficient allocation of multicast addresses. This is important for IPv4 which has a small number of multicast addresses available. This is less of a concern with IPv6 multicast. Whereas IPv6 allows for 2112 possible multicast addresses, IPv4 multicast addresses are restricted to only class D Internet addresses (224.0.0.0/4).[5] [6]

Port number 2535 is assigned by IANA for use with this protocol.[7] All protocol messages are encapsulated in UDP datagrams.[8] The MADCAP protocol has much in common with DHCP, but they are separate protocols with no common dependencies.[9]

History

MADCAP was originally based on DHCP. Microsoft included MADCAP as part of the DHCP service in Windows 2000.[10] RFC 2730 was published as a proposed networking standard by the IETF in December 1999. Guidelines for the allocation of IPv6 multicast addresses using MADCAP were published in RFC 3307 in August 2002.[11]

External links

Notes and References

  1. RFC 2730. IETF. December 1999 . 21 January 2018 . Patel . Baiju V. . Shah . Munil . Hanna . Steve .
  2. Web site: Windows 2000 DHCP. comptechdoc.org. 21 January 2018.
  3. Web site: Troubleshooting telephony in Windows 2000 Professional. TechRepublic (ZDNet/CBS Interactive).
  4. Book: Huggins. Diana. Windows 2000 network infrastructure. 2003. Que. Indianapolis, Ind.. 0-7897-2863-X. 2nd..
  5. Web site: Windows Server 2008 R2 and Windows Server 2008. docs.microsoft.com. 2 July 2012 . Microsoft. 21 January 2018.
  6. Web site: Configuring Multicast Scopes. serverbrain.org. 21 January 2018.
  7. Web site: Service Name and Transport Protocol Port Number Registry. IANA.org. 21 January 2018.
  8. RFC 2730 Section 1.5. IETF. December 1999 . 21 January 2018 . Patel . Baiju V. . Shah . Munil . Hanna . Steve .
  9. RFC 2730 Section 1.4. IETF. December 1999 . 21 January 2018 . Patel . Baiju V. . Shah . Munil . Hanna . Steve .
  10. Book: Alcott. Neall. DHCP for Windows 2000. January 2001. O'Reilly Media, Inc.. 1565928385. Chapter 8.
  11. Haberman. B. RFC 3307. IETF. September 2002. 21 January 2018.