ORTC CG vs WebRTC WG Issues

Hi all,

It seems some clarification is needed here with respect to what bugs should
be filed against which spec/repo. The object model has been adopted by the
W3C WebRTC Working Group, therefore all proposed object model changes need
to come through the WG. The APIs are converging, it would cause enormous
churn if we took that work on inside the CG.  We (ORTC editors, spec
authors, chairs) will not submit Issues or PRs in the WG on behalf of
another person or organization.

If you wish to submit an issue or a PR for the WebRTC object model, please
do that directly in the WG. https://www.w3.org/2011/04/webrtc/


You will need to be a member of the W3C and the Working Group in order to
for that work to be accepted. Here are the instructions to join:

https://www.w3.org/2004/01/pp-impl/47318/instructions

Note: For those who are not employed by W3C member organizations but would
like to contribute to the spec, may want to pay closer attention to the
bits around "Invited Experts".


With that being said, the following tickets in the ORTC CG repo will be
closed:

RTCRtpSender not checking media track state or identity constraints in
constructor
https://github.com/openpeer/ortc/issues/468

RTCRtpSender.setTransport may raise a IncompatibleMediaStreamTrackError due
to identity check
https://github.com/openpeer/ortc/issues/467

RTX APT capability?
https://github.com/openpeer/ortc/issues/444

Split RTCRtpEncodingParameters in RTCRtpEncodingParameters and
RTCRtpDecodingParameters
https://github.com/openpeer/ortc/issues/440


The ORTC editorial members appreciate the effort our members put into
building a better ORTC spec, we hope to see more from you with that in
mind. Please do not take this as a lack of interest or appreciation, the
opposite is in fact true.


Best Regards,
Erik Lagerway, ORTC Chair
(WebRTC WG Co-chair)

CC. WebRTC WG Chairs, W3C Staff