RFC 9175: Add in support #786
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mrdeep1
force-pushed
the
echo_rtag_options
branch
from
69fe0b7 to
3859784
Compare
mrdeep1
force-pushed
the
echo_rtag_options
branch
from
3859784 to
a27d1d4
Compare
|
This PR does not currently have the corner case code referred to in #793. It will be in a different PR based off this code, but it made this PR too complicated. |
mrdeep1
force-pushed
the
echo_rtag_options
branch
from
a27d1d4 to
08363ba
Compare
mrdeep1
force-pushed
the
echo_rtag_options
branch
from
08363ba to
0a1c37b
Compare
mrdeep1
force-pushed
the
echo_rtag_options
branch
3 times, most recently
from
37c239b to
6e80bee
Compare
mrdeep1
force-pushed
the
echo_rtag_options
branch
from
6e80bee to
e489994
Compare
obgm
changed the title
mrdeep1
force-pushed
the
echo_rtag_options
branch
from
e489994 to
fcec0f5
Compare
mrdeep1
force-pushed
the
echo_rtag_options
branch
from
fcec0f5 to
159c04a
Compare
mrdeep1
force-pushed
the
echo_rtag_options
branch
from
159c04a to
f36161e
Compare
mrdeep1
force-pushed
the
echo_rtag_options
branch
from
f36161e to
6836104
Compare
mrdeep1
force-pushed
the
echo_rtag_options
branch
3 times, most recently
from
44df810 to
c2795da
Compare
A unique Request-Tag is added to any PUT/POST/FETCH request that contains a large body. The server is then able to differentiate between concurrent sending of large data using the same session. If a server responds with a 4.01 and includes an Echo option, then the libcoap client retransmits the request adding in the received Echo option with the same value. If the server responds normally with an Echo option, then the next request from the libcoap client (internally added by libcoap) will contain that Echo option. It is the responsibility of the server application to add in the Echo option if required and validate the next request unless the Echo is triggered by OSCORE (RFC8613 Appendix B.1.2).
mrdeep1
force-pushed
the
echo_rtag_options
branch
from
c2795da to
2165991
Compare
obgm
reviewed
Jun 22, 2022
|
🎉 |
This was referenced Sep 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add in support for the Echo and Request-Tag options.
A unique Request-Tag is added to any PUT/POST/FETCH request that contains
a large body. The server is then able to differentiate between concurrent
sending of large data using the same session.
If a server responds with a 4.01 and Echo option, then the libcoap client
retransmits the request adding in the received option.
If the server responds normally with an Echo option, then the next request
from the client (added by libcoap) will contain that request option.
It is the responsibility of the server application to add in the Echo
option unless this is triggered by OSCORE.
Request-Tag code abstracted from #611
Echo code abstracted from #764