Re: [MMUSIC] Re: [MBONED] WG action for draft-savola-mboned-mcast-rpaddr-03.txt

The question "how to achieve ASM at the end hosts" is pretty vague, given
that the end hosts already support ASM natively. 

If you mean, how to use SSM in applications, then the SDP source filter
extensions <draft-ietf-mmusic-sdp-srcfilter-05.txt> allow you to signal
SSM sessions in SDP (and hence in SIP). This draft is in AD review for
Proposed Standard.

If the aim is to emulate many-to-many multicast with multiple SSM channels,
then an application that knows its peers could, for example, signal a full
mesh of SSM channels using SIP. I'm not aware of any applications that do
this, since a central server architecture is easier and scales to the sizes
most people are considering, but it doesn't seem outside the realm of what
is possible. The question is better suited for the SIPPING working group,
though.

Colin

--> hoerdt@clarinet.u-strasbg.fr writes:
> Yes, I am very curious of how to achieve ASM at the end hosts using
> SIP and sdp. Maybe some people from mmusic could give us some hints ?
> 
> Hoerdt Mickaël
> 
> > IMO, you'll never get a consensus on depricating ASM until all of the
> > pieces are in place for SSM to accomplish the same thing.  I think that
> > what you will get a consensus on is a document that identifies the
> > missing pieces and provides recommendations on how these pieces could
> > be provided both at the protocol level, hardware level (MLDv2
> > Snooping??) and most importantly, at the application or session level
> > to achieve the same many-to-many ASM behavior.
> >
> > Respectfully,
> >
> > Beau Williamson
> >
> >
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
> 

-- 
Colin Perkins
csp@csperkins.org

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic