…us Protocol (OCSP) Stapling (i.e., Certificate Status Request in Section 8 of [ RFC6066 ), both of which confer substantial performance and privacy benefits when used in combination with SVCB records. To realize the greatest privacy benefits, this proposal is intended for use ove…
…]. Clients MUST use the Server Name Indication extension in the TLS handshake [ RFC6066 ]. Once a connection to the server has been established (including a connection via a proxy or over a TLS-encrypted tunnel), the client MUST send an opening handshake to the server. The handsh…
…6]. Clients MUST use the Server Name Indication extension in the TLS handshake [RFC6066]. Once a connection to the server has been established (including a connection via a proxy or over a TLS-encrypted tunnel), the client MUST send an opening handshake to the server. The handsha…
… there is no harm in supporting the TLS Server Name Indication (SNI) extension [RFC6066], this is not necessary since the same function is served in XMPP by the 'to' address of the initial stream header as explained in Section 4.7.2 of [RFC6120]. 3.6. Human Factors It is strongly…
…services over plain HTTP (e.g., the "Certificate Status Request" TLS extension [RFC6066], often colloquially referred to as "OCSP Stapling"). NOTE: The above points are expressly only an example and do not purport to address all the involved complexities. For instance, there are …
…ervices over plain HTTP (e.g., the "Certificate Status Request" TLS extension [ RFC6066 ], often colloquially referred to as "OCSP Stapling"). NOTE: The above points are expressly only an example and do not purport to address all the involved complexities. For instance, there are…
…y a domain name DNS-TERMS ), 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 s…
…ervices over plain HTTP (e.g., the "Certificate Status Request" TLS extension [ RFC6066 ], often colloquially referred to as "OCSP Stapling"). NOTE: The above points are expressly only an example and do not purport to address all the involved complexities. For instance, there are…
…ng the TLS handshake. This may be done using the Server Name Indication (SNI) [ RFC6066 ] extension to TLS or using some other mechanism. QUIC connections are established as described in [ QUIC-TRANSPORT ]. During connection establishment, HTTP/QUIC support is indicated by select…
…y a domain name DNS-TERMS ), 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 s…
…there is no harm in supporting the TLS Server Name Indication (SNI) extension [ RFC6066 ], this is not necessary since the same function is served in XMPP by the 'to' address of the initial stream header as explained in Section 4.7.2 of [RFC6120] 3.6 . Human Factors It is strongl…
… domain name ([DNS-TERMS]), 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 …
…]. Clients MUST use the Server Name Indication extension in the TLS handshake [ RFC6066 ]. Once a connection to the server has been established (including a connection via a proxy or over a TLS-encrypted tunnel), the client MUST send an opening handshake to the server. The handsh…
…bilities, such as those supporting Server Name Indication (SNI) ( Section 3 of [RFC6066] ), for operational purposes. This specification defines a new concept in HTTP, "Alternative Services", that allows an origin server to nominate additional means of interacting with it on the …
…ervices over plain HTTP (e.g., the "Certificate Status Request" TLS extension [ RFC6066 ], often colloquially referred to as "OCSP Stapling"). NOTE: The above points are expressly only an example and do not purport to address all the involved complexities. For instance, there are…