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
Diagnostic notation for CoAP requests #16
Labels
enhancement
New feature or request
Comments
miri64
added a commit
to core-wg/draft-dns-over-coap
that referenced
this issue
Aug 9, 2021
The notation is inspired by the notation in RFC 8613, but as of yet, there is no standard diagnostic notation for CoAP (see core-wg/corrclar#16) as we have for HTTP/2.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Several documents building on CoAP currently have examples like
or
(not trying to be particularly accurate in the above examples, suffice to say the notation varies)
It Would Be Nice If we could have an agreed-on notation, possibly through corrclar. HTTP/2 has something like this, which is used in practice in documents. This was suggested by different people before; I didn't take the time to look up the meetings or mailing list posts as I'm pretty sure none of them said anything more concrete than "it would be nice if".
I don't have a concrete proposal for here -- more starting a wishlist for whoever (may or may not be me) might pick that up later into corrclar if we want it there. Nice properties would include:
Req: GET coap://[2001:db8::1]/.well-known/core?foo=bar
may be easier to use, especially in long examples, than the fullThe notation should not be designed for parsing, really just for illustration. (We may need one parser to verify document content, unless we have a single trusted pretty-printer and verify by having binary versions of all examples). In addition to serving as usable format for IDs, it might also double as debug output for CoAP sniffers or implementations.
The text was updated successfully, but these errors were encountered: