Publish Recommendation with Proposed Amendments

[dontcallmedom]

Since the initial publication of WebRTC as a Recommendation in January 21, the Working Group has identified, approved and integrated in the editors draft 47 substantive amendments (changes and additions) to the specification.

We published 26 as Candidate Amendments in March 2023.

Among the 47 amendments, 28 have now demonstrated to be implemented and interoperable (see below).

This means we can now bring these 28 amendments to Last Call for Proposed Amendments if there is WG consensus. Doing so starts a 60 wide review period and an Advisory Committee review, which, if successful, allows to republish the Recommendation with these 28 amendments normatively integrated (and properly covered by the Patent Policy).

The targeted amendments can be classified as follows:

• Amendments aligning with existing implementations
  • Set default values of the RTCConfiguration dictionary, aligning it with current implementations - section 4.2.1 RTCConfiguration Dictionary (PR #2691)
  • Update RTCIceGatheringState, RTCPeerConnectionState, RTCIceConnectionState to clarify the relevant transport it represents - section 4.3.2 RTCIceGatheringState Enum (PR #2680)
  • No longer queue a task in the determine DTMF algorithm - section 7.3 canInsertDTMF algorithm (PR #2742)
  • Align MTI stats with implementations - section 8.6 Mandatory To Implement Stats (PR #2744, PR #2748)
  • Clarify simulcast envelope is determined by negotiation - section 5.4.1 Simulcast functionality (PR #2760)
  • Update explanation of simulcast envelope. - section 5.4.1 Simulcast functionality (PR #2814)
  • Fix ambiguities in the setCodecPreferences() algorithm - section Methods (PR #2847)
  • Reject setParameters(), replaceTrack(), & insertDTMF() after stop() - section Methods (PR #2829)
  • Make removeTrack() a no-op after transceiver.stop() - section Methods (PR #2875)
  • Don't fire connectionstatechange on pc.close() - section Update the connection state (PR #2876)
  • Fix binaryType setter requirements - section Attributes (PR #2909)
  • Change the default value of binaryType - section Attributes (PR #2913)
• Untestable amendments
  • Substantive but unobservable IDL changes:
    • Replace DOMTimeStamp in the definition of the RTCCertificateExpiration.expires and of RTCCertificate.expires, and change its origin to certificate creation time - section 4.9.1 RTCCertificateExpiration Dictionary (PR #2686, PR #2700)
    • Remove unused RTCRtpDecodingParameters dictionary - section 5.2.5 RTCRtpDecodingParameters Dictionary (PR #2753)
    • Remove single-value RTCIceCredentialType enum - section 4.2.2 RTCIceCredentialType Enum (PR #2767)
    • Create RTCRtpCodec dictionary and reuse in RTCRtpCodecCapability and RTCRtpCodecParameters definitions - section 5.2.9 RTCRtpCodecParameters Dictionary (PR #2834)
    • Make RTCRtpHeaderExtensionCapability.uri required - section 5.2.12 RTCRtpHeaderExtensionCapability Dictionary (PR #2841)
    • Add empty setParameterOptions as second argument to setParameters for extensibility - section RTCSetParameterOptions Dictionary (PR #2885)
  • Untestable in WPT:
    • Allow an implementation-defined limited to the number of configured ICE Servers - section 4.2.1 RTCConfiguration Dictionary (PR #2679)
    • Allow encoder resolution alignment in scaleResolutionDownBy. - section 5. RTP Media API (PR #2808)
• Interoperable modifications
  • Ensure the connecting state happens whenever a ICE or DTLS transport is new - section 4.3.3 RTCPeerConnectionState Enum (PR #2687)
  • Validate ICE transport settings upfront when setting a configuration - section 4.4.1.6 Set the configuration (PR #2689)
  • Put ICE transport connection in failed state when no candidates are received - section 5.6.4 RTCIceTransportState Enum (PR #2704)
  • Add RTCRtpEncodingParameters.maxFramerate - section Methods (PR #2785)
  • Remove RTCRtpEncodingParameters.scaleResolutionDownBy for audio - section Methods (PR #2772, PR #2799)
  • Default RTCRtpEncodingParameters.scaleResolutionDownBy to 1 for video - section Methods (PR #2772)
  • setCodecPreferences only takes into account receive codecs - section Methods (PR #2926)
  • Add control for the receiver's jitter buffer - section RTCRtpReceiver Interface (PR #2953)

[dontcallmedom-bot]

This issue was discussed in WebRTC WG Meeting at TPAC 2024 – 24 September 2024 (Updating the W3C Recommendation)