组播协议简介.ppt

* * Dense-mode multicast protocols Initially flood/broadcast multicast data to entire network, then prune back paths that dont have interested receivers Sparse-mode multicast protocols Assumes no receivers are interested unless they explicitly ask for it Sparse-dense mode multicast protocols Behaves in manner that is appropriate for distribution of receiver group (sparse or dense, or any combination thereof) * IETF status of Multicast Protocols DVMRPv1 is obsolete and is no longer used. DVMRPv2 is the current implementation and is used through-out the Mbone. However, DVMRPv2 is only an “Internet-Draft”. Only MOSPF currently has an IETF Category of “Standards-Track”. However, most members of the IETF IDMR working group are unsure that MOSPF will scale to any degree and are therefore uncomfortable with declaring MOSPF as “the” standard for IP Multicasting. (Even the author of MOSPF, J. Moy, has been quoted in an RFC that, “more work needs to be done to determine the scalability of MOSPF.”) At the August 1997 meeting of the IETF IDMR working group, the vote to approve PIM as the IETF Multicast protocol standard was 2 votes short of being unanimous. Given the above, the IETF is expected to reassign all of the above protocols to the “Experimental” Category in order to give all protocols a level playing field. * DVMRP Overview DVMRP is a Distance vector based protocol that is modeled after RIPv1 with the following fundamental differences: Infinity = 32 (hops) Subnet masks are sent in the route advertisements which make DVMRP a Classless protocol. DVMRP also makes special use of Poison-Reverse advertisements which is explained in the following slides. DVMRP routing information is carried inside of IGMP (IP protocol 2) packets. Therefore, if you are trying to capture a DVMRP conversation using equipment like a Network General Sniffer, you will need to capture IGMP packets and futher decode them. The IGMP type code for DVMRP is 0x13. * Appropriate for large number