Skip to content
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.

Sign up for GitHub

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

Don't retry from retry #616

Merged
merged 5 commits into from
Aug 5, 2024
Merged

Don't retry from retry #616

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
48e8499
Don't retry from retry
ekr May 27, 2024
8405ddd
Explain why you shouldn't retry
ekr May 27, 2024
3a1b4d5
Clarifyretry behavior
ekr Aug 3, 2024
7366697
Clarifyretry behavior
ekr Aug 3, 2024
5c78be3
Fix long line
ekr Aug 3, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions draft-ietf-tls-esni.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -886,8 +886,12 @@ initiated in response to a "retry_config". Sending a "retry_config"
in this situation is a signal that the server is misconfigured, e.g.,
the server might have multiple inconsistent configurations so that the
client reached a node with configuration A in the first connection and
a node with configuration B in the second. If a client does not retry,
it MUST report an error to the calling application.
a node with configuration B in the second. Note that this guidance
does not apply to the cases in the previous paragraph where the server
has securely disabled ECH.

If a client does not retry, it MUST report an error to the calling
application.

### Authenticating for the Public Name {#auth-public-name}

Expand Down
Loading