Menu
Home Explore People Places Arts History Plants & Animals Science Life & Culture Technology
On this page
Multicast Address Dynamic Client Allocation Protocol

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

We don't have any images related to Multicast Address Dynamic Client Allocation Protocol yet.
We don't have any YouTube videos related to Multicast Address Dynamic Client Allocation Protocol yet.
We don't have any PDF documents related to Multicast Address Dynamic Client Allocation Protocol yet.
We don't have any Books related to Multicast Address Dynamic Client Allocation Protocol yet.
We don't have any archived web articles related to Multicast Address Dynamic Client Allocation Protocol yet.

Overview

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

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).456

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.[9] Microsoft included MADCAP as part of the DHCP service in Windows 2000.8 RFC 2730 was published as a proposed networking standard by the IETF in December 1999.9 Guidelines for the allocation of IPv6 multicast addresses using MADCAP were published in RFC 3307 in August 2002.10

References

  1. Patel, Baiju V.; Shah, Munil; Hanna, Steve (December 1999). "RFC 2730". IETF. Retrieved 21 January 2018. https://tools.ietf.org/html/rfc2730 ↩

  2. "Windows 2000 DHCP". comptechdoc.org. Retrieved 21 January 2018. http://www.comptechdoc.org/os/windows/win2k/win2kdhcp.html ↩

  3. Huggins, Diana (2003). Windows 2000 network infrastructure (2nd. ed.). Indianapolis, Ind.: Que. ISBN 0-7897-2863-X. 0-7897-2863-X ↩

  4. "Windows Server 2008 R2 and Windows Server 2008". docs.microsoft.com. Microsoft. 2 July 2012. Retrieved 21 January 2018. https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd469716(v=ws.10) ↩

  5. "Configuring Multicast Scopes". serverbrain.org. Retrieved 21 January 2018. https://www.serverbrain.org/network-infrastructure-2003/configuring-multicast-scopes.html ↩

  6. Huggins, Diana (2003). Windows 2000 network infrastructure (2nd. ed.). Indianapolis, Ind.: Que. ISBN 0-7897-2863-X. 0-7897-2863-X ↩

  7. "Service Name and Transport Protocol Port Number Registry". IANA.org. Retrieved 21 January 2018. https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=2535 ↩

  8. Alcott, Neall (January 2001). DHCP for Windows 2000. O'Reilly Media, Inc. pp. Chapter 8. ISBN 1565928385. 1565928385 ↩

  9. Patel, Baiju V.; Shah, Munil; Hanna, Steve (December 1999). "RFC 2730". IETF. Retrieved 21 January 2018. https://tools.ietf.org/html/rfc2730 ↩

  10. Haberman, B (September 2002). "RFC 3307". IETF. Retrieved 21 January 2018. https://tools.ietf.org/html/rfc3307 ↩