Re: [rtcweb] interworking with non-WEBRTC endpoints [was RE: Use Case draft]

[Marshall Eubanks <[e-mail]>]

On Wed, May 2, 2012 at 1:54 PM, Iñaki Baz Castillo <[e-mail]> wrote:
> 2012/5/2 Dan Wing <[e-mail]>:
>> For other decisions, such as if we disallow un-encrypted RTP by
>> WEBRTC endpoints, we create a requirement that some device does
>> the interworking between WEBRTC endpoints (which do only SRTP)
>> and non-WEBRTC endpoints (which do RTP).  That means, for that
>> interworking, we would adopt the interworking model on slide 7
>> that I presented at IETF83,
>> http://www.ietf.org/proceedings/83/slides/slides-83-WEBRTC-3.pdf
>
> Hi, the link is broken (404). Could you please point to a working one?
>

http://www.ietf.org/proceedings/83/slides/slides-83-rtcweb-3.pdf

> However, when I presented slide 7, there were objections at the microphone that this model 'is broken'.  I would like to understand the objections so we can reach consensus on how interworking from WEBRTC to non-WEBRTC is expected to occur.

My objection is that the proposed system will require middleware to
interoperate with the
vast number of videoconferencing sessions out there, most of which use
RTP. From the
standpoint of a video service provider, buying hardware to support
video to laptops is likely to
lead to requests that participants download some other software which
interoperates natively.

This is an existing business with a fairly large scale and installed
base. Not operating the way that they do is not likely to go over
well.

Regards
Marshall

> Thanks a lot.
>
> --
> Iñaki Baz Castillo
> <[e-mail]>
> _______________________________________________
> rtcweb mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/rtcweb