From nobody Thu Dec 1 09:21:42 2022 Return-Path: X-Original-To: tcpm@ietfa.amsl.com Delivered-To: tcpm@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07EF7C14CF05 for ; Thu, 1 Dec 2022 09:21:42 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.599 X-Spam-Level: X-Spam-Status: No, score=-17.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3vZMhg-CaGVq for ; Thu, 1 Dec 2022 09:21:40 -0800 (PST) Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 454A5C14CF14 for ; Thu, 1 Dec 2022 09:21:40 -0800 (PST) Received: by mail-wm1-x334.google.com with SMTP id l39-20020a05600c1d2700b003cf93c8156dso2130355wms.4 for ; Thu, 01 Dec 2022 09:21:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=/J4oVe64VSrEDmYzMTOk8WvbJLnqJ6GpgXwN+MXEnEQ=; b=OMb09byUVPdjH0wPUL+ZsbGl6oYWWQaDl7gERUaq4z20+BBrosENiPtuHTAmd3fUmf YQ1A8kF3yBu04cmx/ezTPaXD8WosRar8Vq+3RtkqBbdiVHM4QhhZBDiO7JyTHgeu5ofJ D1OK6pzDPD57FmqC964Wa6/vgAA88RuwufInm1+hJhDhaiC82m4sk8zgfQK6iumrP5mF AjbIUmPIrr+bFGJ95Z9iEQ6rWUTr1hCvovjmGWwyfh43klVC++tUqRzVNvAvWx0Rhaxw Vh3DIwwsviqfOAXOr42Kj5RpV189Q1INMx5nykrPQ2eMI6aCSW1d5DWHJRpQ+G2K2005 4e2A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=/J4oVe64VSrEDmYzMTOk8WvbJLnqJ6GpgXwN+MXEnEQ=; b=ht48y9PHLcDQHv7cksZbLVU4RKZa8gJUwziMBqzPGZqKmRpP4o9ufCFZXSw66WkESL FGaqpTE9DaAQNuqGK6tDaHNsOH9sp1S6enzHGF9WiXIpQQZhlfTlOCzyPvusNBmhNIRN ncRsUnC865DHYmVTTX01qLg1YK3waMgubGwBeraH7TrjSd743Ic0LdFXoGWljj95Wxz2 bBgusBC1p909hPGJHMQHMQZfGApDW7Bxl8sZ+WYm300zrznu88dmYl+SR+qz18DbwcYg yCaxNFsoeTzRmHZTAGhwMyK3ztUo83CdkiHY4lsmIFMAI8dk+VMGI7BPjGEGUF763t1H uC2w== X-Gm-Message-State: ANoB5pm6/JDk2LdCHn5DBklbaV6yaYy8IF21Rzf5//47N+44XU1MUHrx JhaxndBMGejOM+v/I+qcMMpmlUmYP3IG2u7ypL57bA== X-Google-Smtp-Source: AA0mqf4TIi+N0LzuWeIoZqfowrA4ffHkuWJjq+j3M9lLTlVqiHK+NRo87o6JNUZDadK1Kk0Niy67CSSxCJaBBX2rP00= X-Received: by 2002:a05:600c:4386:b0:3cf:a4a6:a048 with SMTP id e6-20020a05600c438600b003cfa4a6a048mr35182365wmn.202.1669915297892; Thu, 01 Dec 2022 09:21:37 -0800 (PST) MIME-Version: 1.0 References: <161060871994.10783.1247396842504892132@ietfa.amsl.com> <7c527d72-2f48-b39e-9f09-0f22e9c865f2@gmx.at> In-Reply-To: From: Yuchung Cheng Date: Thu, 1 Dec 2022 09:21:01 -0800 Message-ID: To: Yoshifumi Nishida Cc: Yuchung Cheng , rscheff@freebsd.org, tcpm@ietf.org, draft-ietf-tcpm-prr-rfc6937bis@ietf.org, "Semke, Jeff" Content-Type: multipart/alternative; boundary="00000000000023851805eec774cf" Archived-At: Subject: Re: [tcpm] I-D Action: draft-ietf-tcpm-prr-rfc6937bis-02.txt X-BeenThere: tcpm@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: TCP Maintenance and Minor Extensions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Dec 2022 17:21:42 -0000 --00000000000023851805eec774cf Content-Type: text/plain; charset="UTF-8" Hi Yoshifumi, We'll come up an example as you are the second reviewer asking for that. Stay tuned. On Sun, Nov 27, 2022 at 11:28 PM Yoshifumi Nishida wrote: > Hi Yuchung, > > On Mon, Nov 14, 2022 at 12:43 PM Yuchung Cheng 40google.com@dmarc.ietf.org> wrote: > >> >> > Sec 7, PRR example... You describe the forced fast retransmit on the >> > first transmission oppty. Shouldn't that shift the "N" transmissions >> > here one notch to the left? (The ACK for "4"). >> > >> > PRR >> > ack# X 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 >> > cwnd: 20 20 19 19 18 17 17 16 16 15 15 14 14 13 13 12 12 11 10 >> > pipe: 19 19 18 18 17 17 16 16 15 15 14 14 13 13 12 12 11 11 10 >> > sent: N N R N N N N N N N N >> no because forced retransmit only applies when the fast recovery >> starts (i.e. prr_out = 0). by ack #4, prr_out is already 1 due to the >> first "R". >> >> > Hmm. I'm not very sure which situation triggers force retransmit. > Because I think fast recovery starts after fast retransmission which > increases prr_out. > -- > Yoshi > --00000000000023851805eec774cf Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Yoshifumi,

We'll come up an exam= ple as you are the second reviewer asking for that. Stay tuned.
=
On Sun= , Nov 27, 2022 at 11:28 PM Yoshifumi Nishida <nsd.ietf@gmail.com> wrote:
Hi=C2=A0Yuchung,
<= div>
On Mon, Nov 14, 2022 at 12:43 PM Yuchung Cheng <ycheng=3D40google.com@dmarc.ie= tf.org> wrote:

> Sec 7, PRR example... You describe the forced fast retransmit on the > first transmission oppty. Shouldn't that shift the "N" t= ransmissions
> here one notch to the left? (The ACK for "4").
>
> PRR
>=C2=A0 =C2=A0 =C2=A0ack#=C2=A0 =C2=A0X=C2=A0 1=C2=A0 2=C2=A0 3=C2=A0 4= =C2=A0 5=C2=A0 6=C2=A0 7=C2=A0 8=C2=A0 9 10 11 12 13 14 15 16 17 18 19
>=C2=A0 =C2=A0 =C2=A0cwnd:=C2=A0 =C2=A0 20 20 19 19 18 17 17 16 16 15 15= 14 14 13 13 12 12 11 10
>=C2=A0 =C2=A0 =C2=A0pipe:=C2=A0 =C2=A0 19 19 18 18 17 17 16 16 15 15 14= 14 13 13 12 12 11 11 10
>=C2=A0 =C2=A0 =C2=A0sent:=C2=A0 =C2=A0 =C2=A0N=C2=A0 N=C2=A0 R=C2=A0 N= =C2=A0 =C2=A0 =C2=A0 =C2=A0 N=C2=A0 =C2=A0 =C2=A0N=C2=A0 =C2=A0 =C2=A0N=C2= =A0 =C2=A0 =C2=A0N=C2=A0 =C2=A0 =C2=A0N=C2=A0 =C2=A0 =C2=A0N=C2=A0 =C2=A0 = =C2=A0N
no because forced retransmit only applies when the fast recovery
starts (i.e. prr_out =3D 0). by ack #4, prr_out is already 1 due to the
first "R".


Hmm. I'm n= ot very sure which situation triggers force retransmit.=C2=A0
Bec= ause I think fast recovery starts after fast retransmission which increases= prr_out.
--
Yoshi=C2=A0
--00000000000023851805eec774cf--