Connection establishment #1
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
To elaborate on the client behavior for error recovery, BCP14 and ACE terminology are required.
Suggested in followup discussion after Marco Tiloca's WGLC review.
Clarify that clients that support multiple transport protocols should first try the transport protocol that they want to use for DTLS/TLS in the subsequent protocol steps. See also: https://mailarchive.ietf.org/arch/msg/ace/PLWDk5l0Tcb64O0vB4Z8LFdLXkM/
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.
In the followup discussion after WGLC, Marco Tiloca has suggested to elaborate more on possible connection setup failures that can arise if a Client supports only one of {DTLS|TLS}. This PR creates a new section to do so. As a result of the wording being used, the BCP14 terminology section has been included that also has a reference to the ACE framework/DTLS profile terminology.