Re: [rtcweb] Current state of signaling discussion

[Eric Rescorla <[e-mail]>]

On Tue, Oct 18, 2011 at 2:05 PM, Hadriel Kaplan <[e-mail]> wrote:
>
> In the abstract it states:
> "The protocol focuses solely on media negotiation and does not handle call control, call processing, or other functions."
>
> Ignoring esoteric stuff like session transfer, forwarding, etc. (ie, ignoring "phone" stuff) is fine.
>
> BUT, for an actual session protocol to work for even a gaming app, you need to do the following:
> 1) determine a target for the ROAP message (ie, who's this OFFER going to in the end?)
> 2) define how that target identity is conveyed (ie, how does the web server know which browser to give this ROAP OFFER to?)
> 3) define a source identity model, possibly with authentication (ie, who are you?)
> 4) define how the source identity is conveyed (ie, how does the server/far-end-browser know who's calling?)

One might already have much of this stuff in your application to support
whatever person-to-person communications (E.g., IM) you already
have. When I heard "20 lines of code" I always assumed that it excluded that
sort of routing-type stuff.


> 5) define a end-of-session indication
> 6) define a keep-alive mechanism, for when the far end goes away silently and (5) doesn't apply

Do these involve a lot of code?

-Ekr