Re: [webrtc-extensions] RTP Header Extension Encryption (#47)

The question of bundling is really how we need to deal with offers coming from non-browsers.
If draft-ietf-avtcore-cryptex stays the way it is, we must have a sensible code path for dealing with SDP containing:

a=group:BUNDLE A B
a=group:BUNDLE C D

m=audio
a=cryptex
a=mid:A
m=audio
a=cryptex
a=mid:B

m=video
a=mid:C
m=video
a=mid:D

ie cryptex on the audio, not on the video.
If avtcodre-bundle had said "IDENTICAL", we could have rejected this offer.
As it is, rejecting it could be an interop problem.


-- 
GitHub Notification of comment by alvestrand
Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/47#issuecomment-968586697 using your GitHub account


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

Received on Monday, 15 November 2021 06:50:20 UTC