timers and ACKs #47
Merged
timers and ACKs #47
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
Fix #13 Fix #18 Signed-off-by: Thomas Fossati <[email protected]>
thomas-fossati
commented
Feb 17, 2024
thomas-fossati
commented
Feb 23, 2024
thomas-fossati
commented
Feb 23, 2024
| This allows for selective or early retransmission, which leads to more efficient use of bandwidth and memory resources. | ||
|
|
||
| Due to the vast range of network technologies used in IoT deployments, from wired LAN to GSM-SMS, it's not possible to provide a universal recommendation for an initial timeout. | ||
| Therefore, it is RECOMMENDED that DTLS 1.3 implementations allow users to explicitly set the initial timer value. |
There was a problem hiding this comment.
Suggested change
| Therefore, it is RECOMMENDED that DTLS 1.3 implementations allow users to explicitly set the initial timer value. | |
| Therefore, it is RECOMMENDED that DTLS 1.3 implementations allow developers to explicitly set the initial timer value. |
thomas-fossati
commented
Feb 23, 2024
| this document RECOMMENDED to use an initial timer value of 9 seconds with | ||
| exponential back off up to no less then 60 seconds. | ||
| For RRC, the recommendations in {{Section 7.5 of !I-D.ietf-tls-dtls-rrc}} apply. | ||
| Just like the handshake initial timers, it is RECOMMENDED that DTLS 1.2 and 1.3 implementations offer an option for their users to explicitly set the RRC timer. |
There was a problem hiding this comment.
Suggested change
| Just like the handshake initial timers, it is RECOMMENDED that DTLS 1.2 and 1.3 implementations offer an option for their users to explicitly set the RRC timer. | |
| Just like the handshake initial timers, it is RECOMMENDED that DTLS 1.2 and 1.3 implementations offer an option for their developers to explicitly set the RRC timer. |
There was a problem hiding this comment.
My caused by my limited English, why is developer used twice and user still once?
There was a problem hiding this comment.
My caused by my limited English, why is developer used twice and user still once?
I think "user" was consistently replaced by "developer" in what got eventually merged.
There was a problem hiding this comment.
Your right, I was mixed up by the diff on diff.
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.
Fix #13
Fix #18