Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / w3c/webrtc-nv-use-cases issues and pull requests

#129 - Section 3.2.1: Add N49 - video decoding recovery after packet loss

Pull Request - State: open - Opened by xingri 11 months ago - 17 comments

#128 - Made N42 and N47 orthogonal.

Pull Request - State: closed - Opened by stefhak 12 months ago

#127 - N42 and N47 partly overlapping

Issue - State: closed - Opened by stefhak 12 months ago - 2 comments

#126 - Further clarify cloud gaming

Pull Request - State: closed - Opened by stefhak about 1 year ago - 1 comment

#125 - Clarify Requirement N37

Pull Request - State: closed - Opened by aboba about 1 year ago - 1 comment
Labels: December 5 VI

#124 - Requirement N38 is satisfied by jitterBufferTarget

Pull Request - State: closed - Opened by aboba about 1 year ago - 1 comment
Labels: Editors can integrate

#123 - Section 3.2.2: Clarify Use Case

Pull Request - State: closed - Opened by aboba about 1 year ago - 7 comments
Labels: December 5 VI

#122 - setMetadata for redundant relay PCs

Issue - State: open - Opened by palak8669 over 1 year ago - 4 comments
Labels: TPAC 2023

#121 - Section 3.2.2: Clarify meaning of "low latency"

Pull Request - State: closed - Opened by aboba over 1 year ago - 4 comments
Labels: July 2023 Virtual Interim

#120 - Section 3.2.2: Add requirements N13 and N16

Pull Request - State: closed - Opened by aboba over 1 year ago - 4 comments
Labels: July 2023 Virtual Interim

#119 - Section 3.2: Streaming should not require user prompts without sending media

Pull Request - State: closed - Opened by xingri over 1 year ago - 5 comments
Labels: July 2023 Virtual Interim

#118 - Section 3.2.1: Add N48 - bandwidth feedback speed

Pull Request - State: open - Opened by xingri over 1 year ago - 54 comments
Labels: December 5 VI

#117 - Section 3.2.1: Update Requirement N37

Pull Request - State: closed - Opened by aboba over 1 year ago - 3 comments
Labels: July 2023 Virtual Interim

#116 - Req N22: Remove specific hardware reference (GPU)

Pull Request - State: closed - Opened by aboba over 1 year ago - 2 comments
Labels: July 2023 Virtual Interim

#115 - Requirement N22 is hardware specific

Issue - State: closed - Opened by aboba over 1 year ago
Labels: PR exists, July 2023 Virtual Interim

#114 - Section 3.2: Clarify Cloud Gaming Requirements

Issue - State: closed - Opened by xingri over 1 year ago - 12 comments
Labels: duplicate

#113 - Remove Machine Learning Use Case (Section 3.7)

Pull Request - State: closed - Opened by aboba over 1 year ago - 2 comments
Labels: June 2023 Virtual Interim

#112 - Remove Section 3.9: Reduced Complexity Signaling

Pull Request - State: closed - Opened by aboba over 1 year ago - 3 comments
Labels: June 2023 Virtual Interim

#111 - Update Cloud Game Providers information

Pull Request - State: closed - Opened by xingri over 1 year ago - 1 comment

#110 - Removing Section 3.7: Machine Learning

Issue - State: closed - Opened by aboba over 1 year ago - 1 comment
Labels: PR exists, June 2023 Virtual Interim

#109 - Removing Section 3.9: Reduced Complexity Signaling

Issue - State: closed - Opened by aboba over 1 year ago
Labels: PR exists, June 2023 Virtual Interim

#108 - Rename "WebRTC-NV Use Cases" to "WebRTC Extended Use Cases"

Pull Request - State: closed - Opened by aboba over 1 year ago
Labels: Editorial

#107 - Dropping "NV" from the document name

Issue - State: closed - Opened by aboba almost 2 years ago
Labels: PR exists

#106 - Section 3.10.3: Feedback related to decoding pre-encoded media use case

Issue - State: open - Opened by youennf almost 2 years ago - 1 comment

#105 - Section 3.10.2: Feedback related to Transmitting stored encoded media use case

Issue - State: open - Opened by youennf almost 2 years ago - 1 comment

#104 - Section 3.10.1: Feedback related to Live encoded non-WebRTC media use case

Issue - State: open - Opened by youennf almost 2 years ago - 1 comment

#103 - Section 3.2: Feedback related to WebRTC-NV Low Latency Streaming Use Case

Issue - State: open - Opened by youennf almost 2 years ago - 10 comments
Labels: PR exists, TPAC 2023

#102 - Section 3.10: "(outgoing/incoming) WebRTC connection" not defined

Issue - State: open - Opened by stefhak almost 2 years ago - 1 comment

#100 - Section 3.10.1: Live encoded non-WebRTC media use case not compelling

Issue - State: open - Opened by jan-ivar almost 2 years ago - 18 comments

#99 - N15 latency control should be formulated in a technology-agnostic way

Pull Request - State: closed - Opened by aboba almost 2 years ago

#98 - Clarify meaning of "node" in requirement N39

Pull Request - State: closed - Opened by aboba almost 2 years ago

#97 - Remove DRM Requirement N36

Pull Request - State: closed - Opened by aboba almost 2 years ago

#96 - Sections 3.10.1, 3.10.2 and 3.10.3: Control of packetization/depacketization

Issue - State: open - Opened by aboba almost 2 years ago - 2 comments

#95 - Low Latency Streaming: Review of requirements

Issue - State: closed - Opened by aboba almost 2 years ago - 3 comments
Labels: duplicate

#94 - Section 3.2.1: Improvements for game pad input

Issue - State: closed - Opened by aboba almost 2 years ago - 5 comments
Labels: July 2023 Virtual Interim

#93 - Section 3.10: A little thought about the one way media use case

Issue - State: open - Opened by bdrtc almost 2 years ago - 1 comment

#92 - Describe use cases for decoding pre-encoded media

Pull Request - State: closed - Opened by alvestrand almost 2 years ago - 1 comment

#91 - N15 latency control should be formulated in a technology-agnostic way

Issue - State: closed - Opened by alvestrand almost 2 years ago - 3 comments

#90 - Remove requirement N36 (and substitute N13)

Pull Request - State: closed - Opened by aboba almost 2 years ago

#89 - Remove requirement N36 (and substitute N13)

Pull Request - State: closed - Opened by aboba almost 2 years ago

#88 - Remove requirement N36 (and substitute N13)

Pull Request - State: closed - Opened by aboba almost 2 years ago - 1 comment

#87 - Use case:Stored media for RTP transmission

Pull Request - State: closed - Opened by alvestrand almost 2 years ago

#85 - What is a "node" in the Low latency Broadcast with Fanout use case?

Issue - State: closed - Opened by jan-ivar almost 2 years ago - 4 comments

#84 - Add use case for connecting preencoded video from cameras

Pull Request - State: closed - Opened by alvestrand almost 2 years ago

#82 - Use case: Transmit stored pre-encoded content over RTP

Issue - State: closed - Opened by alvestrand almost 2 years ago
Labels: Ready for PR

#81 - Use case: Transmit pre-encoded live content over RTP

Issue - State: closed - Opened by alvestrand almost 2 years ago
Labels: Ready for PR

#80 - Access to raw audio data

Issue - State: open - Opened by lminiero almost 2 years ago - 6 comments
Labels: TPAC 2023

#79 - Use case: Low Latency Broadcast with fanout

Pull Request - State: closed - Opened by aboba almost 2 years ago - 1 comment

#78 - use case:disable A/V sync for remote control or online gaming

Issue - State: closed - Opened by bdrtc almost 2 years ago - 8 comments

#77 - Use case: Broadcast with late fanout

Issue - State: closed - Opened by alvestrand almost 2 years ago - 4 comments
Labels: PR exists

#76 - Support for End to End Encryption (E2EE)

Issue - State: closed - Opened by fluffy about 2 years ago - 3 comments
Labels: Ready for PR

#75 - Add requirements for low latency streaming use cases

Pull Request - State: closed - Opened by aboba about 2 years ago - 5 comments

#74 - Detailed example of potential value of A/V/data sync in WebRTC

Issue - State: open - Opened by darkvertex almost 3 years ago - 1 comment

#73 - Tries to reflect Dec-21 interim discussion:

Pull Request - State: closed - Opened by steely-glint almost 3 years ago

#72 - Expose SCTP sequence number through Data Channel Message object

Issue - State: closed - Opened by epes over 3 years ago - 7 comments

#71 - Update links to IETF to use datatracker rather than tools.ietf.org

Pull Request - State: closed - Opened by dontcallmedom over 3 years ago - 1 comment

#70 - standardized support for captions/subtitles

Issue - State: open - Opened by dogben over 3 years ago - 2 comments

#69 - Setup automatic TR publication

Pull Request - State: closed - Opened by dontcallmedom almost 4 years ago

#68 - first pass at new and updated usecases as presented at TPAC

Pull Request - State: closed - Opened by steely-glint almost 4 years ago - 3 comments
Labels: June 2023 Virtual Interim

#67 - Clarify particular types of workers that need WebRTC

Pull Request - State: closed - Opened by aboba about 4 years ago

#66 - Add call-forking to the mobile use case

Pull Request - State: closed - Opened by aboba about 4 years ago

#65 - Upgrade to new respec profile

Pull Request - State: closed - Opened by dontcallmedom about 4 years ago

#64 - Add call-forking to the mobile use case

Pull Request - State: closed - Opened by aboba over 4 years ago

#63 - Call forking use case

Issue - State: closed - Opened by aboba over 4 years ago - 1 comment
Labels: PR exists

#62 - Low latency streaming with WebTransport + WebRTC

Issue - State: closed - Opened by jianjunz over 4 years ago - 2 comments
Labels: PR exists

#61 - Clarify particular types of workers that need WebRTC

Pull Request - State: closed - Opened by interfect over 4 years ago - 1 comment

#60 - Using WebRTC peer-to-peer networks to back Service Workers

Issue - State: open - Opened by interfect over 4 years ago - 2 comments

#59 - Local IP obfuscation

Issue - State: open - Opened by shacharz almost 5 years ago - 2 comments

#58 - Obtain user consent for one-way media and data use cases

Issue - State: open - Opened by lgrahl about 6 years ago - 20 comments

#58 - Obtain user consent for one-way media and data use cases

Issue - State: open - Opened by lgrahl about 6 years ago - 20 comments

#57 - do we need RTCCbrStatus?

Issue - State: open - Opened by aboba almost 5 years ago - 1 comment

#56 - Peer Connection and back/forward cache

Issue - State: open - Opened by aboba almost 5 years ago - 2 comments

#55 - Requirements for Secure Web Conferencing (Revised)

Pull Request - State: closed - Opened by aboba about 5 years ago

#54 - Requirement tables

Issue - State: closed - Opened by martinthomson about 5 years ago - 1 comment

#53 - Advanced Codec Capabilities API

Issue - State: closed - Opened by henbos about 5 years ago - 10 comments
Labels: Ready for PR

#52 - More control over latency/acceptable loss

Issue - State: open - Opened by Sean-Der about 5 years ago

#51 - Censorship Circumvention/VPN

Issue - State: open - Opened by Sean-Der about 5 years ago - 1 comment

#50 - Broadcasting of 1:Many

Issue - State: closed - Opened by Sean-Der about 5 years ago - 3 comments
Labels: WebTransport Use Case

#49 - Requirements for Secure Web Conferencing (Revised)

Pull Request - State: closed - Opened by aboba about 5 years ago - 2 comments

#48 - Requirements for Secure Web Conferencing (Revised)

Pull Request - State: closed - Opened by aboba about 5 years ago

#47 - Addition of accessibility features

Pull Request - State: closed - Opened by aboba about 5 years ago

#47 - Addition of accessibility features

Pull Request - State: closed - Opened by aboba about 5 years ago

#45 - Accessibility Use Cases

Issue - State: open - Opened by aboba over 5 years ago - 1 comment
Labels: TPAC 2019

#44 - WHATWG streams for data channel messages

Issue - State: open - Opened by aboba over 5 years ago - 7 comments
Labels: Extension spec needed

#42 - Send transferable data

Issue - State: closed - Opened by aboba over 5 years ago - 1 comment

#41 - API for codec performance

Issue - State: closed - Opened by aboba over 5 years ago - 1 comment

#40 - Control surface for header extensions

Issue - State: closed - Opened by aboba over 5 years ago - 2 comments
Labels: PR exists

#40 - Control surface for header extensions

Issue - State: closed - Opened by aboba over 5 years ago - 2 comments
Labels: PR exists

#39 - Requirements for Secure Web Conferencing (Revised)

Pull Request - State: closed - Opened by aboba over 5 years ago

#37 - Requirements for Secure Web Conferencing

Issue - State: open - Opened by aboba over 5 years ago - 1 comment
Labels: PR exists, TPAC 2019

#24 - Clarifying "without a corresponding sender"

Pull Request - State: closed - Opened by aboba over 5 years ago

#23 - Update "parallel forking" language and remove "early media" requirement

Pull Request - State: closed - Opened by aboba over 5 years ago

#22 - Should DataChannels have a getStats() method, should they be usable as selector to the getStats algorithm?

Issue - State: open - Opened by na-g over 5 years ago - 2 comments
Labels: Extension spec needed

#20 - Remove Secure Communications use case and requirements

Pull Request - State: closed - Opened by dontcallmedom almost 6 years ago - 1 comment

#18 - Remove secure communications use-case

Pull Request - State: closed - Opened by aboba almost 6 years ago

#15 - Distributed hash tables

Issue - State: open - Opened by max-mapper about 6 years ago - 23 comments
Labels: June 2019 Interim, TPAC 2019