Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Better explain HTTP focus #157

Closed
mmccool opened this issue Apr 19, 2021 · 2 comments
Closed

Better explain HTTP focus #157

mmccool opened this issue Apr 19, 2021 · 2 comments
Assignees
@mmccool
Labels
Propose Closing Resolve by CR Issues that need to be resolved by CR

Comments

@mmccool
Copy link
Contributor

mmccool commented Apr 19, 2021

for WD update, add at least an editor's note explaining reasoning behind HTTP focus
@mmccool mmccool self-assigned this Apr 19, 2021
@mmccool mmccool mentioned this issue Apr 19, 2021
Closed
@egekorkan egekorkan mentioned this issue May 18, 2021
Closed
@mmccool
Copy link
Contributor Author

mmccool commented Aug 22, 2022

I think this has been resolved. At any rate we have added CoAP now. We should do an editorial review to make sure there are no lingering contradictory statements, both in the main body and the explainer though before we close this issue.

Changing to "Resolve by CR".

@mmccool mmccool added Resolve by CR Issues that need to be resolved by CR and removed Resolve prior to WD update labels Aug 22, 2022
@mmccool
Copy link
Contributor Author

mmccool commented Sep 2, 2022

OK, I read through the spec and looked for this problem, and the current text in the spec seems not be HTTP-specific. The explainer has also been updated to mention HTTP and CoAP where relevant. My conclusion is we can close this issue.

@mmccool mmccool closed this as completed Sep 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mmccool mmccool

Labels
Propose Closing Resolve by CR Issues that need to be resolved by CR
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mmccool