Re: [webrtc-pc] Update the accessibility section 14 to include RFC 8865 for real-time text in WebRTC data channel (#2931)

@aboba , you said > "Also, RFC 8865 lacks RTP packet fields such as timestamp and CSRC/SSRC that are important for sync with audio/video as well as implementation of RFC 9071 conferencing. If an RFC 8865bis design sent RTP packets over data channel unreliable/unordered transport, these problems would not arise."

I see that my answers on these comments were not complete. Here is a refinement:

When drafting RFC 8831, it was decided that real time text should use a reliable data channel. That is specified in RFC 8831 3.2 U-C 5.  Therefore, sending over unreliable/unordered is not within scope. 
RFC 8865 is made in alignment with that decision. 
RFC 8865 makes use of the stream id for mapping the source to the stream similar to how SSRC/CSRC is used in RTP. And the Label provides mapping between source and a readable name of the source like RTCP CNAME. 

I already answered the other questions, So I hope that all issues are solved now, except the discovered problem with RFC 8864 when using a mix of SDP according to section 4 of RFC 8865 and RFC 8832 for creating the channel. 

We can temporarily say: When applying RFC 8865 together with the W3C WebRTC API, section 4 of RFC 8865 MUST not be used.



-- 
GitHub Notification of comment by gunnarhm
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2931#issuecomment-1964534653 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 26 February 2024 16:10:07 UTC