You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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).
cabo
transferred this issue from core-wg/corrclar-old
Jul 22, 2023
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: