Correct. It also solves the problem of controlling the propagation of these messages in the PIM domain, which is a trickier business with AutoRP, especially when using platforms with distributed forwarding.
-- Marko Milivojevic - CCIE #18427 (SP R&S) Senior CCIE Instructor - IPexpert On Thu, Nov 29, 2012 at 12:48 AM, Bal Birdy <[email protected]> wrote: > Quick one, when the bootstrap router sends it's messages out it floods > using the all PIM Router IP of 224.0.0.13, with a TTL of 1. Now normally > I'd sit here and say routers would not send this packet on due to the TTL > setting, but then it suddenly dawned on me how the hell does the BSR > message get around the multicast domain !? > > 20 mins later, I re-read my notes and found a statement saying that all > routers that recieve this message flood it out of pim enabled interfaces. > my question - is it a copy, or the original mcast packet !? It's a copy > right !? so it's not actually routing/forwarding the original packet, but > duplicating (copying) it. If this is the case this is underlying > fundamentals to the protocol which explains why it's "better" than auto-rp, > i.e. no requirement for autorp-listener or sparse-dense mode and obviously > vendor neutral. > > Thanks > B > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > Are you a CCNP or CCIE and looking for a job? Check out > www.PlatinumPlacement.com > > http://onlinestudylist.com/mailman/listinfo/ccie_rs _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com http://onlinestudylist.com/mailman/listinfo/ccie_rs
