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]
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][4]
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]
Historyedit
MADCAP was originally based on DHCP.[9] 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.[1] Guidelines for the allocation of IPv6 multicast addresses using MADCAP were published in RFC 3307 in August 2002.[11]
multicast, address, dynamic, client, allocation, protocol, madcap, communication, protocol, that, allows, hosts, request, multicast, addresses, from, server, contents, overview, history, references, external, linksoverview, editthe, madcap, designed, allow, au. 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 Contents 1 Overview 2 History 3 References 4 External linksOverview editThe 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 4 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 editMADCAP was originally based on DHCP 9 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 1 Guidelines for the allocation of IPv6 multicast addresses using MADCAP were published in RFC 3307 in August 2002 11 References edit a b RFC 2730 IETF Retrieved 21 January 2018 Windows 2000 DHCP comptechdoc org Retrieved 21 January 2018 Troubleshooting telephony in Windows 2000 Professional TechRepublic ZDNet CBS Interactive a b Huggins Diana 2003 Windows 2000 network infrastructure 2nd ed Indianapolis Ind Que ISBN 0 7897 2863 X Windows Server 2008 R2 and Windows Server 2008 docs microsoft com Microsoft Retrieved 21 January 2018 Configuring Multicast Scopes serverbrain org Retrieved 21 January 2018 Service Name and Transport Protocol Port Number Registry IANA org Retrieved 21 January 2018 RFC 2730 Section 1 5 IETF Retrieved 21 January 2018 a b RFC 2730 Section 1 4 IETF Retrieved 21 January 2018 Alcott Neall January 2001 DHCP for Windows 2000 O Reilly Media Inc pp Chapter 8 ISBN 1565928385 Haberman B RFC 3307 IETF Retrieved 21 January 2018 External links editMulticast DHCP Supporting MADCAP nbsp This computer networking article is a stub You can help Wikipedia by expanding it vte Retrieved from https en wikipedia org w index php title Multicast Address Dynamic Client Allocation Protocol amp oldid 855637647, wikipedia, wiki, book, books, library,
