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.

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

Clarify what to do when ALPN negotiation fails #2483

Merged
merged 5 commits into from
Mar 19, 2019
Merged
Changes from all commits
Commits
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-quic-tls.md
Original file line number Diff line number Diff line change
Expand Up @@ -1215,8 +1215,12 @@ QUIC requires that the cryptographic handshake provide authenticated protocol
negotiation. TLS uses Application Layer Protocol Negotiation (ALPN)
{{!RFC7301}} to select an application protocol. Unless another mechanism is
used for agreeing on an application protocol, endpoints MUST use ALPN for this
purpose. When using ALPN, endpoints MUST abort a connection if an application
protocol is not negotiated.
purpose. When using ALPN, endpoints MUST immediately close a connection (see
Section 10.3 in {{QUIC-TRANSPORT}}) if an application protocol is not
negotiated with a no_application_protocol TLS alert (QUIC error code 0x178,
see {{tls-errors}}). While {{!RFC7301}} only specifies that servers use this
alert, QUIC clients MUST also use it to terminate a connection when ALPN
negotiation fails.

An application-layer protocol MAY restrict the QUIC versions that it can operate
over. Servers MUST select an application protocol compatible with the QUIC
Expand Down