Re: [rtcweb] Data channel: Handling of packets on unknown channels

> On 28. Jun 2018, at 13:30, Harald Alvestrand <harald@alvestrand.no> wrote:
> 
> In considering the datachannel API, we encountered one interesting race
> condition:
> 
> A: <configure for datachannel>
> 
> A: CreateOffer(), SetLocalDescription(), send SDP
> 
> B: SetRemoteDescription, CreateAnswer, SetLocalDescription, send SDP
> 
> B: Configure an externally defined data channel, with #3249
> 
> B: Send a message on #3249
> 
> A: SetRemoteDescription
> 
> A: Wait a while (THE PAUSE)
> 
> A: Configure #3249
> 
> Now, if a message comes in to A on #3249 during THE PAUSE, what is the
> implementation to do?
Isn't that some kind or error condition?

If that it true, one could apply:

   If a message with an unsupported PPID is received or some error
   condition related to the received message is detected by the receiver
   (for example, illegal ordering), the receiver SHOULD close the
   corresponding data channel.  This implies in particular that
   extensions using additional PPIDs can't be used without prior
   negotiation.

> I studied draft-ietf-rtcweb-data-channel-13 for at least 3 minutes
> before concluding that it doesn't say.
> 
> What I'd PREFER it to say is "these messages will be dropped on the
> floor. Tough luck."
> 
> I would prefer it to say so explicitly.
> 
> Can we do this?
Not sure about the procedural thing... That ID is stuck in the RFC editor queue
for a long time...

Best regards
Michael
> 
> -- 
> Surveillance is pervasive. Go Dark.
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb