New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 919467 link

Starred by 2 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Feature



Sign in to add a comment

Need ability to persist encryption context for webrtc data channels

Reported by jda...@pcprogramming.com, Jan 7

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

Steps to reproduce the problem:
1. open a webrtc data channel
2. shutdown ISP connection (ie go offline)
3. see if devices behind NAT can still communicate w/ each other

What is the expected behavior?
When internet connectivity is unavailable, devices behind a NAT can still communicate w/ each other, this has significant implications for iot implementations.

What went wrong?
It's not currently possible to persist the encryption context for local communication (webrtc data channel) when a browser app goes offline.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 71.0.3578.98  Channel: stable
OS Version: 10.0
Flash Version:
 
Components: Blink>WebRTC
Labels: Needs-Triage-M71
Cc: hta@chromium.org
Components: -Blink>WebRTC Blink>WebRTC>Network
what does "persist the encryption context" mean in this case, and why do you diagnose this as the cause?

If you can provide some more info (repro case is ideal), that would help in understanding the issue.

This is a feature request.
Cc: santhoshkumar@chromium.org
Labels: -Type-Bug Target-73 Triaged-ET FoundIn-72 M-73 FoundIn-71 FoundIn-73 OS-Linux OS-Mac Type-Feature
Status: Untriaged (was: Unconfirmed)
As per comment#5 the issue seems to be a feature request, hence marking it as untriaged and requesting someone from dev team to look into the issue.

Thanks.!
jdavis@ - per #5, can you describe what the feature is? I'm afraid I don't understand still.

If it is a feature request that requires changes to the JS API specification, the better place to make it is the W3C WG - https://github.com/w3c/webrtc-pc/


Thanks!

Sign in to add a comment