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.[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][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

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]

References

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


Stub icon

This computer networking article is a stub. You can help Wikipedia by adding missing information.

Content Disclaimer

Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.

  1. The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
  2. There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
  3. It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
  4. Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
  5. Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.