issues
search
w3c
/
webrtc-nv-use-cases
Use cases for WebRTC NV
https://w3c.github.io/webrtc-nv-use-cases/
Other
32
stars
13
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Clarifying "without a corresponding sender"
#24
aboba
closed
5 years ago
0
Update "parallel forking" language and remove "early media" requirement
#23
aboba
closed
5 years ago
0
Should DataChannels have a getStats() method, should they be usable as selector to the getStats algorithm?
#22
na-g
opened
5 years ago
2
Requirements Secure Web Conferencing
#21
fluffy
closed
5 years ago
11
(How) does SCTP handle CPU-bound congestion on JavaScript thread?
#30
henbos
closed
5 years ago
67
Remove Secure Communications use case and requirements
#20
dontcallmedom
closed
5 years ago
1
Remove Secure Communications Use Case
#19
aboba
closed
5 years ago
0
Remove secure communications use-case
#18
aboba
closed
5 years ago
0
Obtain user consent for one-way media and data use cases
#58
lgrahl
opened
6 years ago
20
Allocate RAW data capture buffer as shared GPU memory buffer
#17
astojilj
closed
5 years ago
4
N20 Raw media should support various pixel formats
#16
astojilj
closed
5 years ago
4
Distributed hash tables
#15
max-mapper
opened
6 years ago
23
N29: A way to obtain user consent for one-way media and data use cases
#14
lgrahl
opened
6 years ago
8
N23: Why share media between worker and main thread?
#13
lgrahl
closed
5 years ago
3
N14: Already supported by 1.0?
#12
lgrahl
closed
5 years ago
2
"Cannot be supported in 1.0"
#11
lgrahl
closed
5 years ago
2
Mobility: Peer reflexive candidates
#10
lgrahl
opened
6 years ago
8
Mobility backup candidate pairs
#9
lgrahl
closed
5 years ago
3
Can we move away from the terms "offer" and "answer"?
#8
lgrahl
closed
5 years ago
1
N11: "as a single message" is implementation, not requirement
#7
alvestrand
closed
5 years ago
1
N08: "receive audio/video without a corresponding sender" - not a new requirement?
#6
alvestrand
closed
5 years ago
1
N03: "Bandwidth limit across mesh endpoints" needs clarification or modification
#5
alvestrand
closed
5 years ago
1
N04: The term "early media" MUST NOT be used on its own, and MAY be removed.
#4
alvestrand
closed
5 years ago
2
The term "parallel forking" is overloaded and should not be used
#3
alvestrand
closed
5 years ago
1
WebRTC and Real-time Translation
#2
AdamSobieski
closed
5 years ago
2
IoT use-case requires direct one-way media support
#1
steely-glint
opened
6 years ago
24
Integrate CSP access control into algorithms
#36
alvestrand
closed
5 years ago
9
WebRTC bypass CSP connect-src policies
#35
murillo128
closed
5 years ago
4
Need for Initial Bitrate by the Application/RtpSender?
#31
vr000m
opened
7 years ago
12
Previous