[j-nsp] multicast on M20

[harry]

Because PIM sparse mode is based on an explicit join model the lack of a S,G
entry indicates the lack of join state; there is no need to forward such
traffic because evidently no one is interested in receiving it.

In a sparse topology traffic only flows when S,G or *,G joins are sent
towards the source or RP respectively.

To my knowledge only multicast traffic that is originated by or destined to
the RE is processed in SW on the RE. The Tunnel PIC handles PIM register
encapsulation in HW.

HTHs.



> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net 
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Anouk Rocher
> Sent: Thursday, October 23, 2003 4:07 PM
> To: juniper-nsp at puck.nether.net
> Subject: [j-nsp] multicast on M20
> 
> 
> I am trying out IP multicast after a long time. Used to do 
> this with some cisco gear all the way back in 1997-1998.
> 
> My question on the current generation of Juniper equipment is 
> what gets downloaded into H/W - only the Groups or <Source, 
> Group> pairs? I am only just catching up with PIM-SM, but it 
> seems that one would need 
> to control forwarding based on <S, G> pairs. So what happens 
> to packets with <S, G> pairs that are not in H/W. Are these 
> dropped or sent to the CPU?
> 
> TIA,
> Anouk.
> 
> ________________________________________________
> Get your own "800" number
> Voicemail, fax, email, and a lot more 
> http://www.ureach.com/reg/tag 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net 
> http://puck.nether.net/mailman/listinfo/junipe> r-nsp
>