From 89e0e2e00a382ace9216397243024fac55425567 Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Wed, 23 Dec 2020 15:53:27 +1100 Subject: [PATCH] Use "domain name", not "DNS name" To align with "official" terminology in RFC 8499. Cite that. --- draft-ietf-quic-http.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/draft-ietf-quic-http.md b/draft-ietf-quic-http.md index 2163754c53..e086d2c4cb 100644 --- a/draft-ietf-quic-http.md +++ b/draft-ietf-quic-http.md @@ -370,9 +370,10 @@ QUIC transport versions with HTTP/3 MAY be defined by future specifications. QUIC version 1 uses TLS version 1.3 or greater as its handshake protocol. HTTP/3 clients MUST support a mechanism to indicate the target host to the -server during the TLS handshake. If the server is identified by a DNS name, -clients MUST send the Server Name Indication (SNI; {{!RFC6066}}) TLS extension -unless an alternative mechanism to indicate the target host is used. +server during the TLS handshake. If the server is identified by a domain name +({{?DNS-TERMS=RFC8499}}), clients MUST send the Server Name Indication (SNI; +{{!RFC6066}}) TLS extension unless an alternative mechanism to indicate the +target host is used. QUIC connections are established as described in {{QUIC-TRANSPORT}}. During connection establishment, HTTP/3 support is indicated by selecting the ALPN