Multicast Address Dynamic Client Allocation Protocol

The Multicast Address Dynamic Client Allocation Protocol (MADCAP) is designed to allow for automatic dynamic assignment of multicast addresses.{{cite book|last1=Huggins|first1=Diana|title=Windows 2000 network infrastructure|date=2003|publisher=Que|location=Indianapolis, Ind.|isbn=0-7897-2863-X|edition= 2nd.|url=http://www.pearsonitcertification.com/articles/article.aspx?p=101618&seqNum=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 2¹¹² possible multicast addresses, IPv4 multicast addresses are restricted to only class D Internet addresses (224.0.0.0/4).{{cite web|title=Windows Server 2008 R2 and Windows Server 2008|url=https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd469716(v=ws.10)|website=docs.microsoft.com| date=2 July 2012 |publisher=Microsoft|accessdate=21 January 2018}}{{cite web|title=Configuring Multicast Scopes|url=https://www.serverbrain.org/network-infrastructure-2003/configuring-multicast-scopes.html|website=serverbrain.org|accessdate=21 January 2018}}

Port number 2535 is assigned by IANA for use with this protocol.{{cite web|title=Service Name and Transport Protocol Port Number Registry|url=https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=2535|website=IANA.org|accessdate=21 January 2018}} All protocol messages are encapsulated in UDP datagrams.{{cite journal|title=RFC 2730 Section 1.5|url=https://tools.ietf.org/html/rfc2730#section-1.5|website=IETF|date=December 1999 |accessdate=21 January 2018 |last1=Patel |first1=Baiju V. |last2=Shah |first2=Munil |last3=Hanna |first3=Steve }} The MADCAP protocol has much in common with DHCP, but they are separate protocols with no common dependencies.{{cite journal|title=RFC 2730 Section 1.4|url=https://tools.ietf.org/html/rfc2730#section-1.4|website=IETF|date=December 1999 |accessdate=21 January 2018 |last1=Patel |first1=Baiju V. |last2=Shah |first2=Munil |last3=Hanna |first3=Steve }}

MADCAP was originally based on DHCP. Microsoft included MADCAP as part of the DHCP service in Windows 2000.{{cite book|last1=Alcott|first1=Neall|title=DHCP for Windows 2000|date=January 2001|publisher=O'Reilly Media, Inc.|isbn=1565928385|pages=Chapter 8|url=https://www.safaribooksonline.com/library/view/dhcp-for-windows/1565928385/ch08.html}} 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.{{cite journal|last1=Haberman|first1=B|title=RFC 3307|url=https://tools.ietf.org/html/rfc3307|website=IETF|date=September 2002|accessdate=21 January 2018}}

{{Reflist}}

• [https://technet.microsoft.com/en-us/library/cc958927.aspx Multicast DHCP]
• [https://technet.microsoft.com/en-us/library/cc958950.aspx Supporting MADCAP]

Category:Communications protocols

{{Compu-network-stub}}