Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-channel-04.txt

[Randell Jesup <[e-mail]>]

On 3/6/2013 7:08 AM, MARCON, JEROME (JEROME) wrote:
> But then - and given that DATA_CHANNEL_OPEN_RESPONSE no longer exists in this new draft version - I wonder how the peer can reject an incoming DATA_CHANNEL_OPEN message signaling a 'subprotocol' it does not support.

channel.close();

I.e. there's no explicit prior-to-connect rejection, you simply state 
instead "I'm not interested" and close it.  This resets the streams, and 
causes the other side to be notified of the close. You're correct in 
that this is not distinguished from other reasons to close() it; if 
those are needed you should either negotiate it out-of-band, or make a 
rejection part of the protocol you run over it.  This is entirely within 
the application's domain.  Most applications would have no need for this.

-- 
Randell Jesup
[e-mail]