-
Notifications
You must be signed in to change notification settings - Fork 11
Reword covered use case language #63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
suggestion to remove "this solution may address uses cases" -> this solution shall address use cases that may include...
|
What would you think of changing "shall address" to "addresses" ? I don't feel strongly about this one way or other |
|
Hi Cullen, changing "shall address" to "addresses" works for me |
changed "shall address" -> addresses
|
+1 on the change |
This incorporates the changes proposed #63, #64, and #68, removes the Mandatory-to-Implement section as discussed on the mailing lists, and makes the required changes to address the Block from the IESG charter discussion. It does not address #66, Spencer's suggestion to drop the Architecture documents, or his suggestion that we specify of MoQ-capable in front of relays (and similar).
|
Hi Ted - I am good with the final MOQ charter as the language is clear WRT to the statement about the use cases. The PR I raised right after the IETF 114 meeting was specifically asking to change In the end, the final wording is even better: "This solution addresses use cases including live streaming, gaming, and media conferencing and will scale efficiently." So, I am all good WRT my PR, however, administratively, it appears my request should have been picked as it was submitted way ahead of the IESG request and in fact, I spoke about this on the MIC in the room (the day of the BOF). |
suggestion to remove "this solution may address uses cases" -> this solution shall address use cases that may include...