From c8bcb7836308a4a9038bbad7aa2944a074dd76b7 Mon Sep 17 00:00:00 2001 From: David Schinazi Date: Fri, 26 Jan 2024 13:39:56 -0800 Subject: [PATCH] Fix draft references --- draft-pauly-v6ops-happy-eyeballs-v3.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/draft-pauly-v6ops-happy-eyeballs-v3.md b/draft-pauly-v6ops-happy-eyeballs-v3.md index 4299154..c4e3a13 100644 --- a/draft-pauly-v6ops-happy-eyeballs-v3.md +++ b/draft-pauly-v6ops-happy-eyeballs-v3.md @@ -249,7 +249,7 @@ If any of the answers were from SVCB RRs, they SHOULD be sorted ahead of any answers that were not associated with a SVCB record. If the client supports TLS Encrypted Client Hello (ECH) discovery through -SVCB records {{!SVCB-ECH=I-D.draft-ietf-tls-svcb-ech}}, depending on the +SVCB records {{!SVCB-ECH=I-D.ietf-tls-svcb-ech}}, depending on the client's preference to handle ECH, the client SHOULD sort addresses with ECH keys taking priority to maintain privacy when attempting connection establishment. @@ -388,7 +388,7 @@ attempts to establish a connection, some cryptographic handshakes may be dependent on ServiceMode SVCB RRs and could impose limitations on establishing a connection. For instance, ECH-capable clients may become SVCB-reliant clients ({{Section 3 of SVCB}}) when SVCB RRs -contain the "ech" SvcParamKey {{!ECH=I-D.ietf-tls-svcb-ech}}. If the +contain the "ech" SvcParamKey {{SVCB-ECH}}. If the client is either an SVCB-reliant client or a SVCB-optional client that might switch to SVCB-reliant connection establishment during the process, the client MUST wait for SVCB RRs before proceeding with the