From 3485ca9572f8455565fd376b32eb71021da7f610 Mon Sep 17 00:00:00 2001 From: Ariel Otilibili <30573755+ariel-anieli@users.noreply.github.com> Date: Tue, 10 Apr 2018 10:27:56 +0200 Subject: [PATCH 1/3] QUIC is QUIC, and does not stay for anything. https://www.ietf.org/mail-archive/web/quic/current/msg03855.html --- draft-ietf-quic-transport.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index a52d0230f4..e344b714b2 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -137,6 +137,9 @@ protocol, including the conceptual design, wire format, and mechanisms of the QUIC protocol for connection establishment, stream multiplexing, stream and connection-level flow control, connection migration, and data reliability. +QUIC used to be known as 'Quick UDP Internet Connections', but the present +document advises it be used no more: QUIC does not stand for anything. + Accompanying documents describe QUIC's loss detection and congestion control {{QUIC-RECOVERY}}, and the use of TLS 1.3 for key negotiation {{QUIC-TLS}}. From 4d8ab11608a9a7909998787edd20db134c93de4e Mon Sep 17 00:00:00 2001 From: Ariel Otilibili <30573755+ariel-anieli@users.noreply.github.com> Date: Tue, 10 Apr 2018 10:59:48 +0200 Subject: [PATCH 2/3] Update draft-ietf-quic-transport.md --- draft-ietf-quic-transport.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index e344b714b2..0422e585be 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -137,8 +137,7 @@ protocol, including the conceptual design, wire format, and mechanisms of the QUIC protocol for connection establishment, stream multiplexing, stream and connection-level flow control, connection migration, and data reliability. -QUIC used to be known as 'Quick UDP Internet Connections', but the present -document advises it be used no more: QUIC does not stand for anything. +QUIC is a name, not an acronym. Accompanying documents describe QUIC's loss detection and congestion control {{QUIC-RECOVERY}}, and the use of TLS 1.3 for key negotiation {{QUIC-TLS}}. From 07ea187d86a460b4f97d01084f129489a24cdca3 Mon Sep 17 00:00:00 2001 From: Ariel Otilibili <30573755+ariel-anieli@users.noreply.github.com> Date: Wed, 11 Apr 2018 09:03:09 +0200 Subject: [PATCH 3/3] Update draft-ietf-quic-transport.md --- draft-ietf-quic-transport.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index 0422e585be..6b50a803e3 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -137,8 +137,6 @@ protocol, including the conceptual design, wire format, and mechanisms of the QUIC protocol for connection establishment, stream multiplexing, stream and connection-level flow control, connection migration, and data reliability. -QUIC is a name, not an acronym. - Accompanying documents describe QUIC's loss detection and congestion control {{QUIC-RECOVERY}}, and the use of TLS 1.3 for key negotiation {{QUIC-TLS}}. @@ -184,6 +182,8 @@ QUIC packet: : A well-formed UDP payload that can be parsed by a QUIC receiver. +QUIC is a name, not an acronym. + ## Notational Conventions