FW: WGLC: draft-ietf-behave-multicast-06.txt

> -----Original Message-----
> From: Marshall Eubanks [mailto:tmemulticasttech.com] 

> On Jun 6, 2007, at 1:01 PM, Brian Haberman wrote:

> > But it could be supported by having an
administrator inside the NAPT
> > assign different groups to all the SSM senders. 
That way, (S,G)
> > collisions will not occur outside the NAPT.
> >
> > I don't see an easy, automated solution.
> 
> The NAPT knows what is SSM. Couldn't it also do a
Multicast Group  
> Translation for SSM groups ? Why
> is this more difficult than, say, port translation ?

Port translation is only important within the NAPT device
itself.
Whereas in multicast, the problem is how to advertize the
address of the
group, and how to make sure this address remain stable. I
think manual
configuration is probably a good bet, if not the only way.

Bert


_______________________________________________
Behave mailing list
Behaveietf.org
https:/
/www1.ietf.org/mailman/listinfo/behave