Re: [rtcweb] SDP Offer/Answer draft-jennings-rtcweb-signaling - Scope

2011/10/18 Christer Holmberg <>:
>>No, this is not a draft about a "default signaling protocol"
>>for RTCweb. Wrong. This is just a protocol for communication
>>between the JavaScript code and the RTCweb stack in the
>>browser. It does NOT mandate how the signaling messages are
>>sent on-the-wire.
> Eventhough the draft does not suggest a default signaling protocol, I don't think that is completely true that it is only between the JS app and broswer. At least it's not very clear.
> - Section 5.1 says: "ROAP messages are typically carried over a **reliable transport** (likely HTTP via XMLHttpRequest or WebSockets),..."

Yes, that is because JavaScript code running in a browser can only
communicate via HTTP or WebSocket.

> - Section 5.3.3 defines an "OK" message, which is used to cease **re-transmissions** of the ANSWER.

I expect that is a "guideline" for the signaling protocol implementor.
There is no need for such "OK" message to be received from the peer or
server. The own JS code could generate it when appropriate and pass it
to its RTCweb stack.

> - In addition, there is text talking about **ROAP signaling messages** (and gateways translating between those and SIP messages).

That just means that, of course, ROAP must be carried within some
signaling protocol (obvious) so, in case of interoperating with a SIP
network a gateway is required (unless you use SIP over WebSocket).

> So, while I support and offer/answer based approach, I think we need to get a clearer understanding of the scope.

IMHO "ROAP" draft just suggests a generic signaling guidelines for
future RTCweb protocol developers. It does define the communication
between the JS code and its own RTCweb stack, but not the signaling
on-the-wire (for that guidelines are provided).


Iñaki Baz Castillo

Received on Tuesday, 18 October 2011 10:36:45 UTC