Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Protocol-Independent Multicast
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Sparse mode== '''Protocol Independent Multicast - Sparse-Mode''' ('''PIM-SM''') is a [[protocol (computing)|protocol]] for efficiently [[routing]] [[Internet Protocol]] (IP) [[packet (information technology)|packets]] to [[multicast]] groups that may span wide-area and [[inter-domain]] internets. The protocol is named ''protocol-independent'' because it is not dependent on any particular unicast routing protocol for topology discovery, and ''sparse-mode'' because it is suitable for groups where a very low percentage of the nodes (and their [[router (computing)|router]]s) will subscribe to the multicast session. Unlike earlier dense-mode multicast routing protocols such as [[DVMRP]] and [[dense multicast]] routing which flooded packets across the network and then pruned off branches where there were no receivers, PIM-SM explicitly constructs a tree from each sender to the receivers in the multicast group.<ref name=CiscoPIM>{{citation |url=http://www.cisco.com/en/US/docs/switches/lan/catalyst3750x_3560x/software/release/12.2_53_se/configuration/guide/swmcast.html |title=Configuring IP Multicast Routing |publisher=[[Cisco Systems]] |access-date=2013-12-06}}</ref> ===Multicast clients=== A router receives explicit Join/Prune messages from those neighboring routers that have downstream group members. * In order to join a multicast group, G, a host conveys its membership information through the [[Internet Group Management Protocol]] (IGMP). * The router then forwards data packets addressed to a multicast group G to only those interfaces on which explicit joins have been received. * A Designated Router (DR) sends periodic Join/Prune messages toward a group-specific Rendezvous Point (RP) for each group for which it has active members. ** Note that one router will be automatically or statically designated as the rendezvous point (RP), and all routers must explicitly join through the RP. * Each router along the path toward the RP builds a wild card (any-source) state for the group and sends Join/Prune messages on toward the RP. ** The term route entry is used to refer to the state maintained in a router to represent the distribution tree. ** A route entry may include such fields as: *** source address *** the group address *** the incoming interface from which packets are accepted *** the list of outgoing interfaces to which packets are sent *** timers, flag bits, etc. ** The wild card route entry's incoming interface points toward the RP ** The outgoing interfaces point to the neighboring downstream routers that have sent Join/Prune messages toward the RP as well as the directly connected hosts which have requested membership to group G. * This state creates a shared, RP-centered, distribution tree that reaches all group members. ===Multicast sources=== * When a data source first sends to a group, its Designated Router (DR) unicasts Register messages to the Rendezvous Point (RP) with the source's data packets encapsulated within. * If the data rate is high, the RP can send source-specific Join/Prune messages back towards the source and the source's data packets will follow the resulting forwarding state and travel un-encapsulated to the RP. * Whether they arrive encapsulated or natively, the RP forwards the source's de-capsulated data packets down the RP-centered distribution tree toward group members. * If the data rate warrants it, routers with local receivers can join a source-specific, shortest path, distribution tree, and prune this source's packets off the shared RP-centered tree. * For low data rate sources, neither the RP, nor last-hop routers need join a source-specific shortest path tree and data packets can be delivered via the shared RP-tree. Once the other routers which need to receive those group packets have subscribed, the RP will unsubscribe to that multicast group, unless it also needs to forward packets to another router or node. Additionally, the routers will use [[reverse-path forwarding]] to ensure that there are no loops for packet forwarding among routers that wish to receive multicast packets.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)