Section 4.4.2: createOffer() and setLocalDescription() resource handling

[aboba]

Section 4.4.2 says:

"If a system has limited resources (e.g. a finite number of decoders), createOffer needs to return an offer that reflects the current state of the system, so that setLocalDescription will succeed when it attempts to acquire those resources. The session descriptions MUST remain usable by setLocalDescription without causing an error until at least the end of the fulfillment callback of the returned promise."

[BA] My understanding is that existing implementations do not provide this guarantee. Do we need to change the text?

[youennf]

My understanding is that implementations guarantee the setlocalDescription will succeed because UA will not really acquire these resources at this time.
Given the resources allocation is racy and might actually happen way after setLocalDescription, it makes sense to me to remove the mention of resource acquisition.

[dontcallmedom-bot]

This issue had an associated resolution in the minutes of WebRTC March 2023 meeting – 21 March 2023 (Issue #2835: Section 4.4.2: createOffer() and setLocalDescription() resource handling):

RESOLUTION: #2835 is ready for pull request