Re: [quicwg/base-drafts] Clarify client anti-amplification response (#3445)
Jana Iyengar <notifications@github.com> Tue, 25 February 2020 23:37 UTC
Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 328CE3A0876 for <quic-issues@ietfa.amsl.com>; Tue, 25 Feb 2020 15:37:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.1
X-Spam-Level:
X-Spam-Status: No, score=-3.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4OiR8IS9Uujx for <quic-issues@ietfa.amsl.com>; Tue, 25 Feb 2020 15:37:45 -0800 (PST)
Received: from out-23.smtp.github.com (out-23.smtp.github.com [192.30.252.206]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1ACEE3A0884 for <quic-issues@ietf.org>; Tue, 25 Feb 2020 15:37:45 -0800 (PST)
Received: from github-lowworker-275fa97.va3-iad.github.net (github-lowworker-275fa97.va3-iad.github.net [10.48.17.64]) by smtp.github.com (Postfix) with ESMTP id 673376600A8 for <quic-issues@ietf.org>; Tue, 25 Feb 2020 15:37:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1582673864; bh=FL2b8qhYBMbMQr8OjrQrwfhrlOrf35UYOJwZLLLPJeU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pFQM+87Qi4U99ZuA7s9YDAFC4WNFccUfG4S155Avd1nET0GZCVGavn6E73NQ5w5t8 e/6jcsSArb1lpgXQBrB/AXe3t8dXalviOfwz1pxxn/JiaTcrzaWqmdp+le3Dx7rnyI TxDlS2Har1EXkJoq78W8RWubGtFClmKUVpPTQNIg=
Date: Tue, 25 Feb 2020 15:37:44 -0800
From: Jana Iyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKY734ILVTOEE7VM45V4MLREREVBNHHCDAXLQI@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3445/review/364527056@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3445@github.com>
References: <quicwg/base-drafts/pull/3445@github.com>
Subject: Re: [quicwg/base-drafts] Clarify client anti-amplification response (#3445)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e55afc855e5b_39d83fc5a70cd968496cc"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/bTH5jQpGqcXMS9U1zNy2tc7NhaY>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Feb 2020 23:37:54 -0000
janaiyengar commented on this pull request. a few suggestions > @@ -1626,14 +1626,17 @@ payloads of at least 1200 bytes, adding padding to packets in the datagram as necessary. Sending padded datagrams ensures that the server is not overly constrained by the amplification restriction. -Packet loss, in particular loss of a Handshake packet from the server, can cause -a situation in which the server cannot send when the client has no data to send -and the anti-amplification limit is reached. In order to avoid this causing a -handshake deadlock, clients MUST send a packet upon a probe timeout, as -described in {{QUIC-RECOVERY}}. If the client has no data to retransmit and does -not have Handshake keys, it MUST send an Initial packet in a UDP datagram of -at least 1200 bytes. If the client has Handshake keys, it SHOULD send a -Handshake packet. +Loss of an Initial or Handshake packet from the server can cause a deadlock if +the client does not send additional Initial or Handshake packets. The server +can reach its anti-amplification limit, but if the client has received +acknowledgements for all the data is has sent, it has no reason to send more ```suggestion acknowledgements for all the data it has sent, it has no reason to send more ``` > @@ -1626,14 +1626,17 @@ payloads of at least 1200 bytes, adding padding to packets in the datagram as necessary. Sending padded datagrams ensures that the server is not overly constrained by the amplification restriction. -Packet loss, in particular loss of a Handshake packet from the server, can cause -a situation in which the server cannot send when the client has no data to send -and the anti-amplification limit is reached. In order to avoid this causing a -handshake deadlock, clients MUST send a packet upon a probe timeout, as -described in {{QUIC-RECOVERY}}. If the client has no data to retransmit and does -not have Handshake keys, it MUST send an Initial packet in a UDP datagram of -at least 1200 bytes. If the client has Handshake keys, it SHOULD send a -Handshake packet. +Loss of an Initial or Handshake packet from the server can cause a deadlock if +the client does not send additional Initial or Handshake packets. The server ```suggestion the client does not send additional Initial or Handshake packets. This can happen because the server ``` > @@ -1626,14 +1626,17 @@ payloads of at least 1200 bytes, adding padding to packets in the datagram as necessary. Sending padded datagrams ensures that the server is not overly constrained by the amplification restriction. -Packet loss, in particular loss of a Handshake packet from the server, can cause -a situation in which the server cannot send when the client has no data to send -and the anti-amplification limit is reached. In order to avoid this causing a -handshake deadlock, clients MUST send a packet upon a probe timeout, as -described in {{QUIC-RECOVERY}}. If the client has no data to retransmit and does -not have Handshake keys, it MUST send an Initial packet in a UDP datagram of -at least 1200 bytes. If the client has Handshake keys, it SHOULD send a -Handshake packet. +Loss of an Initial or Handshake packet from the server can cause a deadlock if +the client does not send additional Initial or Handshake packets. The server +can reach its anti-amplification limit, but if the client has received ```suggestion can reach its anti-amplification limit, and if the client has received ``` > @@ -1626,14 +1626,17 @@ payloads of at least 1200 bytes, adding padding to packets in the datagram as necessary. Sending padded datagrams ensures that the server is not overly constrained by the amplification restriction. -Packet loss, in particular loss of a Handshake packet from the server, can cause -a situation in which the server cannot send when the client has no data to send -and the anti-amplification limit is reached. In order to avoid this causing a -handshake deadlock, clients MUST send a packet upon a probe timeout, as -described in {{QUIC-RECOVERY}}. If the client has no data to retransmit and does -not have Handshake keys, it MUST send an Initial packet in a UDP datagram of -at least 1200 bytes. If the client has Handshake keys, it SHOULD send a -Handshake packet. +Loss of an Initial or Handshake packet from the server can cause a deadlock if +the client does not send additional Initial or Handshake packets. The server +can reach its anti-amplification limit, but if the client has received +acknowledgements for all the data is has sent, it has no reason to send more +packets. In this case, where the client would otherwise not send any +additional packets, the server will be unable to send because it has not ```suggestion additional packets, the server will be unable to send more data because it has not ``` > @@ -1626,14 +1626,17 @@ payloads of at least 1200 bytes, adding padding to packets in the datagram as necessary. Sending padded datagrams ensures that the server is not overly constrained by the amplification restriction. -Packet loss, in particular loss of a Handshake packet from the server, can cause -a situation in which the server cannot send when the client has no data to send -and the anti-amplification limit is reached. In order to avoid this causing a -handshake deadlock, clients MUST send a packet upon a probe timeout, as -described in {{QUIC-RECOVERY}}. If the client has no data to retransmit and does -not have Handshake keys, it MUST send an Initial packet in a UDP datagram of -at least 1200 bytes. If the client has Handshake keys, it SHOULD send a -Handshake packet. +Loss of an Initial or Handshake packet from the server can cause a deadlock if +the client does not send additional Initial or Handshake packets. The server +can reach its anti-amplification limit, but if the client has received +acknowledgements for all the data is has sent, it has no reason to send more +packets. In this case, where the client would otherwise not send any +additional packets, the server will be unable to send because it has not +received enough from the client or validated the clients address. To prevent ```suggestion received enough data from the client or has not validated the client's address. To prevent ``` > -Packet loss, in particular loss of a Handshake packet from the server, can cause -a situation in which the server cannot send when the client has no data to send -and the anti-amplification limit is reached. In order to avoid this causing a -handshake deadlock, clients MUST send a packet upon a probe timeout, as -described in {{QUIC-RECOVERY}}. If the client has no data to retransmit and does -not have Handshake keys, it MUST send an Initial packet in a UDP datagram of -at least 1200 bytes. If the client has Handshake keys, it SHOULD send a -Handshake packet. +Loss of an Initial or Handshake packet from the server can cause a deadlock if +the client does not send additional Initial or Handshake packets. The server +can reach its anti-amplification limit, but if the client has received +acknowledgements for all the data is has sent, it has no reason to send more +packets. In this case, where the client would otherwise not send any +additional packets, the server will be unable to send because it has not +received enough from the client or validated the clients address. To prevent +this deadlock, clients MUST send a packet on a probe timeout, or PTO; ```suggestion this deadlock, clients MUST send a packet on a probe timeout (PTO, ``` > -a situation in which the server cannot send when the client has no data to send -and the anti-amplification limit is reached. In order to avoid this causing a -handshake deadlock, clients MUST send a packet upon a probe timeout, as -described in {{QUIC-RECOVERY}}. If the client has no data to retransmit and does -not have Handshake keys, it MUST send an Initial packet in a UDP datagram of -at least 1200 bytes. If the client has Handshake keys, it SHOULD send a -Handshake packet. +Loss of an Initial or Handshake packet from the server can cause a deadlock if +the client does not send additional Initial or Handshake packets. The server +can reach its anti-amplification limit, but if the client has received +acknowledgements for all the data is has sent, it has no reason to send more +packets. In this case, where the client would otherwise not send any +additional packets, the server will be unable to send because it has not +received enough from the client or validated the clients address. To prevent +this deadlock, clients MUST send a packet on a probe timeout, or PTO; +see Section 5.3 of {{QUIC-RECOVERY}}. In this case, the client MUST send an ```suggestion see Section 5.3 of {{QUIC-RECOVERY}}). Specifically, the client MUST send an ``` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/quicwg/base-drafts/pull/3445#pullrequestreview-364527056
- [quicwg/base-drafts] Clarify client anti-amplific… ianswett
- Re: [quicwg/base-drafts] Clarify client anti-ampl… ianswett
- Re: [quicwg/base-drafts] Clarify client anti-ampl… ianswett
- Re: [quicwg/base-drafts] Clarify client anti-ampl… ianswett
- Re: [quicwg/base-drafts] Clarify client anti-ampl… Martin Thomson
- Re: [quicwg/base-drafts] Clarify client anti-ampl… ianswett
- Re: [quicwg/base-drafts] Clarify client anti-ampl… ianswett
- Re: [quicwg/base-drafts] Clarify client anti-ampl… Martin Thomson
- Re: [quicwg/base-drafts] Clarify client anti-ampl… ianswett
- Re: [quicwg/base-drafts] Clarify client anti-ampl… ianswett
- Re: [quicwg/base-drafts] Clarify client anti-ampl… Martin Thomson
- Re: [quicwg/base-drafts] Clarify client anti-ampl… Christian Huitema
- Re: [quicwg/base-drafts] Clarify client anti-ampl… Martin Thomson
- Re: [quicwg/base-drafts] Clarify client anti-ampl… Christian Huitema
- Re: [quicwg/base-drafts] Clarify client anti-ampl… Martin Thomson
- Re: [quicwg/base-drafts] Clarify client anti-ampl… Christian Huitema
- Re: [quicwg/base-drafts] Clarify client anti-ampl… Jana Iyengar
- Re: [quicwg/base-drafts] Clarify client anti-ampl… ianswett
- Re: [quicwg/base-drafts] Clarify client anti-ampl… ianswett
- Re: [quicwg/base-drafts] Clarify client anti-ampl… ianswett
- Re: [quicwg/base-drafts] Clarify client anti-ampl… ianswett
- Re: [quicwg/base-drafts] Clarify client anti-ampl… ianswett
- Re: [quicwg/base-drafts] Clarify client anti-ampl… ianswett
- Re: [quicwg/base-drafts] Clarify client anti-ampl… ianswett
- Re: [quicwg/base-drafts] Clarify client anti-ampl… ianswett
- Re: [quicwg/base-drafts] Clarify client anti-ampl… Martin Thomson