- From: docfaraday via GitHub <sysbot+gh@w3.org>
- Date: Tue, 13 Dec 2022 14:10:07 +0000
- To: public-webrtc-logs@w3.org
> Hm. I can't remember seeing a case where an RFC specified behavior for the case where some party is able to do something, but just refuses to do it at the moment (code supports it, but is not willing to do it). The common writing style (citing RFC 9000 as an example) seems to assume that if you're able to do something, you're also willing to do it. Generally speaking, unless it violates a MUST (or MUST NOT) level requirement, an implementation of an IETF spec can do whatever it wants at pretty much any time. For instance, an endpoint might support bundle, but for some reason does not want to use it at the moment. -- GitHub Notification of comment by docfaraday Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/132#issuecomment-1348646285 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 13 December 2022 14:10:08 UTC