- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Thu, 12 Aug 2021 07:53:16 +0000
- To: public-webrtc-logs@w3.org
@aboba mentioned in https://lists.w3.org/Archives/Public/public-webrtc/2021Aug/0028.html the following: > While the stack and protocol are evolving quickly, I'd prefer not to add a native transform specific to a protocol that hasn't been adopted by an IETF WG, particularly if that method can't accommodate automatic key management. That is just inviting interoperability problems. I understand it that, you would prefer not to add SFrameTransform to the spec as long as the SFrame current draft is not a SFrame WG draft. We could make it clear in the spec that SFrameTransform is based on ongoing IETF work that did not yet reach stability and might remove SFrameTransform at any time if this ongoing work does not succeed. Would that be ok with you? -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/112#issuecomment-897425997 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 12 August 2021 07:53:18 UTC