w3c/webrtc-svc issues and pull requests

#104 - Remove Discovery Section

Pull Request - State: closed - Opened by aboba 7 months ago - 1 comment
Labels: Editorial

#103 - Discovery: Where does this material belong?

Issue - State: closed - Opened by aboba 7 months ago
Labels: PR exists

#102 - Dependency on AV1 RTP payload specification

Issue - State: open - Opened by aboba 9 months ago

#101 - Rewrite of Privacy Considerations Section

Pull Request - State: closed - Opened by aboba 10 months ago

#100 - Aboba patch 12

Pull Request - State: closed - Opened by aboba 10 months ago

#99 - Rewrite of Privacy Considerations Section

Pull Request - State: closed - Opened by aboba 10 months ago

#98 - Use canonical AV1-RTP-SPEC reference

Pull Request - State: closed - Opened by fippo 10 months ago

#97 - Rewrite of Privacy Considerations Section

Pull Request - State: closed - Opened by aboba 12 months ago - 1 comment

#96 - Remove reference to Media Capabilities from Terminology Section

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

#95 - Questions on Scalability Mode and Media Capabilities

Issue - State: closed - Opened by bc-lee about 1 year ago - 1 comment

#94 - What's the default behaviour when user not specify scalabilityMode?

Issue - State: closed - Opened by bdrtc over 1 year ago - 3 comments
Labels: question

#93 - Clarification of privacy considerations

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

#92 - Align exposing `scalabilityMode` with the WebRTC "hardware capabilities" check

Issue - State: open - Opened by pes10k over 1 year ago - 9 comments
Labels: PR exists, privacy-needs-resolution, To be moved: filed in the wrong repo

#91 - Nit: Typos in Privacy Considerations section

Issue - State: closed - Opened by pes10k over 1 year ago - 1 comment
Labels: PR exists

#90 - Example: mixed codec simulcast + SVC

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

#89 - Refer to the addTransceiver and setParameters validation steps

Pull Request - State: closed - Opened by Orphis over 1 year ago
Labels: Editorial, Editors Can Integrate

#88 - Layer Refresh

Issue - State: open - Opened by aboba over 1 year ago - 1 comment
Labels: enhancement

#87 - Why is scalabilityMode not an enum?

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

#86 - Refine error conditions for use of 'S' modes

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

#85 - Minor fix for simulcast with L1T3 sample code.

Pull Request - State: closed - Opened by taste1981 almost 2 years ago
Labels: Editorial

#84 - Add missing modes to the table

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

#83 - Other modes missing from the table

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

#82 - Addition of mode L3T1_KEY to table

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

#81 - L3T1_KEY is missing from the table, but not the diagram section

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

#80 - Lack of access to webrtc-svc

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

#79 - Update getParameters() to not return the default scalabilityMode

Pull Request - State: closed - Opened by Orphis almost 2 years ago
Labels: Needs Test

#78 - Add Media Capabilities Sample

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

#77 - Remove extension to getCapabilities() in favour of MediaCapabilities

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

#76 - Remove extension to getCapabilities() in favour of MediaCapabilities

Pull Request - State: closed - Opened by Orphis almost 2 years ago - 10 comments
Labels: Needs Test

#75 - Returning the default scalabilityMode problematic after fallback

Issue - State: closed - Opened by Orphis almost 2 years ago - 1 comment
Labels: CR-blocking, ready for PR

#73 - S modes and a single active simulcast layer

Issue - State: closed - Opened by Orphis about 2 years ago - 12 comments
Labels: PR exists

#72 - Adding SVC-related stats fields

Issue - State: closed - Opened by bc-lee about 2 years ago - 1 comment

#71 - Remove references to L1T2h and L1T3h

Pull Request - State: closed - Opened by Orphis about 2 years ago

#70 - Revert "Clarify behavior of setParameters()"

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

#69 - Clarify behavior of getParameters()

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

#68 - Clarify behavior of getParameters()

Issue - State: closed - Opened by aboba almost 3 years ago - 5 comments
Labels: PR exists, CR-blocking

#67 - Clarify behavior of setParameters()

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

#66 - setParameters() behavior

Issue - State: closed - Opened by aboba almost 3 years ago - 2 comments
Labels: PR exists, CR-blocking

#65 - Mark up scalabilityModes values as exported definitions

Pull Request - State: closed - Opened by dontcallmedom almost 3 years ago
Labels: Editorial

#64 - Add Behavior section

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

#63 - Editorial reorganization

Pull Request - State: closed - Opened by aboba almost 3 years ago
Labels: Editorial

#62 - Substitute spatialScalabilty for referenceScaling

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

#61 - how to specify L3T3?

Issue - State: closed - Opened by fippo almost 3 years ago - 6 comments
Labels: question

#60 - [Question] Difference between SVC and Simulcast

Issue - State: closed - Opened by mickel8 almost 3 years ago - 4 comments
Labels: question

#59 - What should the scalability mode be when the preferred scalability mode is not supported on the requested codec?

Issue - State: closed - Opened by alvestrand almost 3 years ago - 3 comments
Labels: PR exists, CR-blocking

#58 - What should the scalability mode be when no scalability mode is specified?

Issue - State: closed - Opened by alvestrand almost 3 years ago - 8 comments
Labels: PR exists, CR-blocking

#57 - Handling of unknown scalability modes is underspecified

Issue - State: closed - Opened by alvestrand almost 3 years ago - 4 comments
Labels: PR exists, CR-blocking

#56 - Changing the interpretation if referenceScaling is absent

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

#55 - Fix reference to yet-unspecified referenceScaling

Pull Request - State: closed - Opened by dontcallmedom almost 3 years ago
Labels: Editorial

#54 - Remove RTCRtpReceiver.getCapabilities()

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

#53 - Clarify SDP negotiation and Decoder Compliance

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

#52 - Decoder Capabilities

Issue - State: closed - Opened by aboba about 3 years ago - 3 comments
Labels: PR exists, CR-blocking

#51 - Add L1T1 scalability mode`

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

#50 - should scalabilityMode be an array scalabilityModes?

Issue - State: closed - Opened by fippo about 3 years ago - 11 comments
Labels: question

#49 - SVC getCapabilities() is redundant with Media Capabilities query

Issue - State: closed - Opened by youennf about 3 years ago - 53 comments
Labels: Needs Test

#48 - Do we need an L1T1 scalability mode?

Issue - State: closed - Opened by alvestrand about 3 years ago - 7 comments
Labels: PR exists

#47 - Registries?

Issue - State: closed - Opened by aboba over 3 years ago - 2 comments

#46 - "legal" -> "compliant"

Pull Request - State: closed - Opened by aboba over 3 years ago - 1 comment
Labels: Editorial

#45 - Move to Candidate Recommendation

Issue - State: open - Opened by alvestrand over 3 years ago - 14 comments

#44 - s/legal/valid/?

Issue - State: closed - Opened by jan-ivar over 3 years ago - 2 comments

#43 - Upgrade automatic TR publication

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

#42 - TAG feedback

Issue - State: closed - Opened by aboba about 4 years ago - 2 comments
Labels: tag-tracker

#41 - Upgrade to latest respec profile

Pull Request - State: closed - Opened by dontcallmedom over 4 years ago
Labels: Editorial

#40 - Add note about mappings of scalability modes to AV1

Pull Request - State: closed - Opened by aboba over 4 years ago - 8 comments
Labels: Editorial

#39 - Scalability Mode Table revision

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

#38 - Fix images height and remove legacy images

Pull Request - State: closed - Opened by DanilChapovalov over 4 years ago - 2 comments
Labels: Editorial

#37 - Add and overwrite images for all structures

Pull Request - State: closed - Opened by DanilChapovalov over 4 years ago - 3 comments
Labels: Editorial

#36 - Confusing names for KEY and KEY_SHIFT structures

Issue - State: closed - Opened by DanilChapovalov over 4 years ago - 10 comments

#35 - Browser/SFU negotiation

Pull Request - State: closed - Opened by aboba over 4 years ago - 3 comments
Labels: July Virtual Interim

#34 - Browser/SFU capability negotiation

Issue - State: closed - Opened by aboba over 4 years ago
Labels: PR exists, July Virtual Interim

#33 - Case Sensitivity of scalability modes

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

#33 - Case Sensitivity of scalability modes

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

#32 - Make it clear that scalabilityMode is case-sensitive

Issue - State: closed - Opened by xfq over 4 years ago
Labels: PR exists, i18n-needs-resolution

#31 - Remove outdated ack and empty changelog

Pull Request - State: closed - Opened by dontcallmedom over 4 years ago
Labels: Editorial

#31 - Remove outdated ack and empty changelog

Pull Request - State: closed - Opened by dontcallmedom over 4 years ago
Labels: Editorial

#30 - Privacy considerations aren't specific enough?

Issue - State: closed - Opened by dontcallmedom over 4 years ago - 2 comments

#29 - Wide review of the spec

Issue - State: closed - Opened by dontcallmedom over 4 years ago - 1 comment

#28 - Clean up ReSpec formatting

Pull Request - State: closed - Opened by dontcallmedom over 4 years ago
Labels: Editorial

#27 - Guidelines for addition of scalabilityMode values

Pull Request - State: closed - Opened by aboba almost 5 years ago - 1 comment
Labels: Editorial

#26 - Hardware/software leaks

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

#26 - Hardware/software leaks

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

#25 - Guidelines for addition of scalabilityMode values

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

#25 - Guidelines for addition of scalabilityMode values

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

#24 - Clarification on scalabiltyMode support

Pull Request - State: closed - Opened by aboba almost 5 years ago - 1 comment
Labels: Editorial

#23 - "S" mode considerations

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

#23 - "S" mode considerations

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

#22 - `getCapabilities` seems to leak hardware capabilities w/o a permission

Issue - State: closed - Opened by pes10k about 5 years ago - 23 comments
Labels: privacy-needs-resolution