Multicast Source Discovery Protocol (MSDP) is a Protocol Independent Multicast (PIM) family multicast routing protocol defined by Experimental RFC 3618.[1] Despite becoming the IPv4 de facto standard for inter-domain multicast, development of the protocol stopped in 2006 and it was decided by the authors not to proceed with making it a proposed standard.[2] MSDP interconnects multiple IPv4 PIM Sparse-Mode (PIM-SM) domains which enables PIM-SM to have Rendezvous Point (RP) redundancy and inter-domain multicasting RFC 4611.

MSDP uses TCP as its transport protocol. Each multicast tree needs to have its own RP. All of the RPs are peers (directly or through other MSDP peers). Messages contain the sender (source) address and the multicast group address (S,G). If an RP on its own domain receives a message, it determines if there are listeners for this group. If listeners exist, it triggers a PIM join into the source domain towards the data source. In a peering relationship, one MSDP peer listens for new TCP connections on the well-known port 639.

MSDP is deliberately unspecified for IPv6,[2][3] for a number of reasons, including that protocols such as Source-Specific Multicast (SSM), Bi-directional Multicast and IPv6 Embedded Rendezvous Points would mean there was less requirement for MSDP.

References

  1. ↑ Meyer; Fenner (October 2003). "RFC3618 - Multicast Source Discovery Protocol (MSDP)". tools.ietf.org. IETF. Retrieved 17 August 2018.
  2. 1 2 McBride; Meylor; Meyer (August 2006). "RFC4611 - Multicast Source Discovery Protocol (MSDP) Deployment Scenarios". IETF. Retrieved 17 August 2018.
  3. ↑ Pekka, Savola; Brian, Haberman (November 2004). "Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address". tools.ietf.org. IETF. Retrieved 17 August 2018.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.