Re: [MMUSIC] ICE and RTCP host components

On 10/23/15 2:25 PM, Roman Shpount wrote:
> The normal use case for ICE are large numbers of end points deployed
> behind NAT sending media directly to each other.

"Normal" changes over time. I think what you mean here is "current".

As ICE becomes more mature and people understand it better, it will be 
used more broadly, for things that have legacy components.

In any case, I think there will be much use of webrtc as one end of a 
session with the other end being a legacy sip device.

> Deploying a lot of end
> points without some sort of consent to send media mechanism creates a
> perfect platform for denial of service attacks. ICE solves this issue if
> legacy support is disabled. Furthermore, legacy end points without SDP
> rtcp attribute support end up sending RTCP to completely wrong place.
> Best solution for anything ICE enabled is to set c= line address to IP4
> 0.0.0.0 and provide real RTP and RTCP in ICE candidates. Legacy will not
> work, but no traffic to unexpected destinations will be generated.

Don't break interworking. Certainly this will require at least a 
signaling gateway. In general that will require a media gateway too. But 
anything that can be done to reduce the load on such a media gateway is 
good. It may need to do ICE. It may need to do the consent on behalf of 
the ultimate device.

	Thanks,
	Paul

> On Oct 23, 2015 1:48 PM, "Paul Kyzivat" <pkyzivat@alum.mit.edu
> <mailto:pkyzivat@alum.mit.edu>> wrote:
>
>     Ignoring legacy is a bad idea. It takes a long time for all of it to
>     go away. In the meantime there must be some way of interworking with it.
>
>              Thanks,
>              Paul
>
>     On 10/23/15 1:18 PM, Roman Shpount wrote:
>
>         On Fri, Oct 23, 2015 at 12:48 PM, Harald Alvestrand
>         <harald@alvestrand.no <mailto:harald@alvestrand.no>
>         <mailto:harald@alvestrand.no <mailto:harald@alvestrand.no>>> wrote:
>
>              On 10/22/2015 07:22 AM, Roman Shpount wrote:
>
>                  Basically, end points must implement ICE and be
>             deployed with TURN
>                  servers to play well with other end points. If you
>             implement ICE
>                  with STUN servers only, one would need to make sure to
>             set up
>                  connections only to end points they control, which
>             implement ICE
>                  or at least SDP rtcp attribute. Everything else breaks in
>                  interesting and unpleasant ways. Building anything new
>             now without
>                  ICE, and consent to send traffic which is part of ICE,
>             would be
>                  highly dangerous and can be used for DOS attacks. So, I
>             think it
>                  might be safer to remove interop with legacy.from
>             anything that
>                  supports ICE, and require that remote party implements
>             at least
>                  ice-lite, or no media flow will be established.
>
>
>              RTCP/RTP multiplexing works for all cases where anything
>         works at all.
>
>              Legacy (RTCP port = RTP port + 1) doesn't.
>
>              Time to give up on legacy.
>
>
>         Can we also give up on legacy interop for ICE? Let's make ICE
>         work iwth
>         ICE enabled end points only and stop worrying what goes into c= line
>         address, m= line port, and SDP rtcp attribute. If anybody needs to
>         support legacy, put the media proxy on the RTP path.
>         _____________
>         Roman Shpount
>
>
>         _______________________________________________
>         mmusic mailing list
>         mmusic@ietf.org <mailto:mmusic@ietf.org>
>         https://www.ietf.org/mailman/listinfo/mmusic
>
>
>     _______________________________________________
>     mmusic mailing list
>     mmusic@ietf.org <mailto:mmusic@ietf.org>
>     https://www.ietf.org/mailman/listinfo/mmusic
>