Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-protocol-01.txt

[Randell Jesup <[e-mail]>]

On 10/28/2013 8:05 AM, Michael Tuexen wrote:
> On Oct 24, 2013, at 10:38 PM, "Ejzak, Richard P (Richard)" <[e-mail]> wrote:
>
>>
>> http://www.w3.org/TR/webrtc/#methods-1 describes the "id" attribute in the RTCDataChannelInit dictionary that must be the equivalent of the "stream identifier".  No other interpretation makes sense to me but please correct me if I am wrong.  Note in particular the following text within the description of the createDataChannel procedure (my parenthetical): "If the value of the id attribute is null, initialize it to a value generated by the user agent (browser), according to the WebRTC DataChannel Protocol specification, and skip to the next step. Otherwise, if the value of the id attribute is taken by an existing RTCDataChannel, throw a TBD exception and abort these steps."  So "id" must refer to "stream identifier" since there is no other id in your draft that it could refer to.
> I don't see in the document a statement that the id corresponds to the stream identifier.
> If that is the case, it should be mentioned. The W3C document indicates that the type
> of id is unsigned short?. I don't know enough JS to know if this corresponds to uint16_t
> or not. If not, there is a problem...

That's uint16_t, yes.  There's no specific link in the W3C draft that W3 
DataChannel id == SCTP Stream ID, but it's strongly implied and probably 
should be specified now that we allow external negotiation (before that 
it was less interesting).  Also we should specify that 65535 means "no 
id established yet" in the W3 spec.


-- 
Randell Jesup -- rjesup a t mozilla d o t com