generated from martinthomson/internet-draft-template
-
Notifications
You must be signed in to change notification settings - Fork 1
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
"request URI" not defined #10
Labels
documentation
Improvements or additions to documentation
Comments
Thanks! We should probably include some bits from section 2 of RFC 7230 on this (where it's called "target URI"). It might also be a good idea to emphasize the distinction between the concept (request URI) and its representation (Uri-* options). |
Reopen due to large PENDING |
Let's try to enumerate all the URIs that come with a CoAP request/response:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The RFC uses "request URI" terminology, but there is no definition or reference of what a request URI is.
Also, while the RFC document does describe how the request URI can be generated based on CoAP message elements, it is not very clear that the request URI is not a message element itself (in SIP, the request URI is part of the message syntax).
The text was updated successfully, but these errors were encountered: