[tcpm] Re: Discussion on whether the TCP four-wave mechanism can be simplified to three-wave mechanism

"yangbuwangchuxin@163.com" <yangbuwangchuxin@163.com> Tue, 27 August 2024 02:09 UTC

Return-Path: <yangbuwangchuxin@163.com>
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 95B9AC14F6F2 for <tcpm@ietfa.amsl.com>; Mon, 26 Aug 2024 19:09:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=163.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 DAEzYDphxcdC for <tcpm@ietfa.amsl.com>; Mon, 26 Aug 2024 19:09:20 -0700 (PDT)
Received: from m16.mail.163.com (m16.mail.163.com [117.135.210.5]) by ietfa.amsl.com (Postfix) with ESMTP id D1CFEC151076 for <tcpm@ietf.org>; Mon, 26 Aug 2024 19:09:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=163.com; s=s110527; h=Date:From:Subject:Content-Type:MIME-Version: Message-ID; bh=huDeGB0MAHshDYYZtcg57hHt/QBeyTZZ+fxYpM5i490=; b=Y eCh044obIYuOTM7wLrzukt4UvkuK7rRemZpFkPW7dNBRwXXxT1ALid4sNvJCdsyg L0kD5A6FEXXp71euvOt1IVFr7tVYQRuiq7ECYZDDch361BYl1D9w1aUbSIlX0llM I3NX4mQea2cnvlzRsedOQFCRWj+WODALxrPxNKkwS8=
Received: from yangbuwangchuxin$163.com ( [180.119.68.49] ) by ajax-webmail-wzpm-k8s-gz (Coremail) ; Tue, 27 Aug 2024 10:09:16 +0800 (GMT+08:00)
X-Originating-IP: [180.119.68.49]
Date: Tue, 27 Aug 2024 10:09:16 +0800
From: "yangbuwangchuxin@163.com" <yangbuwangchuxin@163.com>
To: "michael.tuexen" <michael.tuexen@lurchi.franken.de>
X-Priority: 3
X-Mailer: Coremail Webmail Server Version 2023.1-cmXT build 20230828(bca80109) MailAndroid/7.19.7_(14) Copyright (c) 2002-2024 www.mailtech.cn 163com
In-Reply-To: <B86F084B-797D-42E1-A851-DF6299AC2422@lurchi.franken.de>
References: <6defaffd.3f8b1.1917c9c2f23.Coremail.yangbuwangchuxin@163.com> <CAAK044SZyk5LJwohkJ-Fjk1rZidq5fGKXHYBBxgUWh45aiijXA@mail.gmail.com> <55af587.448d8.191885dc7d7.Coremail.yangbuwangchuxin@163.com> <CAAK044TDm72yUxxhkbtYk7O0cRL5vE35kYp+1Q83S9vbdw0jPw@mail.gmail.com> <383509b2.45497.191888db1eb.Coremail.yangbuwangchuxin@163.com> <CAAK044Se=KKaUDpL4=kBARJrsNVKu85ejDC2i7sFUVBD1tTJRw@mail.gmail.com> <B86F084B-797D-42E1-A851-DF6299AC2422@lurchi.franken.de>
X-NTES-SC: AL_Qu2ZBvuZu00u4CiQYekfm04Xjuc9WcK0u/si249eNpt4jCno4wcab2BhMnrG1+KUOSugljq1QjlS5NljYK1Wcr8qKfu79mzRIXawqr1TG8V6cg==
Content-Type: multipart/alternative; boundary="----=_Part_436236_166824489.1724724556891"
MIME-Version: 1.0
Message-ID: <7a06307d.1afa0.1919198345b.Coremail.yangbuwangchuxin@163.com>
X-Coremail-Locale: zh_CN
X-CM-TRANSID: _____wD33zRMNc1mk0AdAA--.6363W
X-CM-SenderInfo: p1dqwuxxzd0wxfkx5xrq6rljoofrz/1tbiXAtH7GXAncvy1wABsr
X-Coremail-Antispam: 1U5529EdanIXcx71UUUUU7vcSsGvfC2KfnxnUU==
X-MailFrom: yangbuwangchuxin@163.com
X-Mailman-Rule-Hits: nonmember-moderation
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tcpm.ietf.org-0
Message-ID-Hash: UIKRRSCBGPSHFWGNBPUDEQ63XT5QRWYR
X-Message-ID-Hash: UIKRRSCBGPSHFWGNBPUDEQ63XT5QRWYR
X-Mailman-Approved-At: Tue, 27 Aug 2024 05:11:37 -0700
CC: tcpm <tcpm@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [tcpm] Re: Discussion on whether the TCP four-wave mechanism can be simplified to three-wave mechanism
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/MXSQ5ZSccbVoRjBEfJkuPwxq7yc>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Owner: <mailto:tcpm-owner@ietf.org>
List-Post: <mailto:tcpm@ietf.org>
List-Subscribe: <mailto:tcpm-join@ietf.org>
List-Unsubscribe: <mailto:tcpm-leave@ietf.org>

Thank you very much! You can tell me the address of the forum or tell me your email address (I don't know if it is the current email address).



---- Replied Message ----
| From | Michael Tuexen<michael.tuexen@lurchi.franken.de> |
| Date | 08/26/2024 16:30 |
| To | Yoshifumi Nishida<nsd.ietf@gmail.com> |
| Cc | yangbuwangchuxin@163.com、tcpm<tcpm@ietf.org> |
| Subject | Re: [tcpm] Discussion on whether the TCP four-wave mechanism can be simplified to three-wave mechanism |
> On 26. Aug 2024, at 09:24, Yoshifumi Nishida <nsd.ietf@gmail.com> wrote:
>
> Hi Yang,
> I think aggregating the 2nd packet (ACK for FIN) and the 3rd packet (FIN) is theoretically possible if you want to do it.
That is correct. The following packetdrill script tests this:

+0.000 socket(..., SOCK_STREAM, IPPROTO_TCP) = 3
+0.000 setsockopt(3, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
+0.000 bind(3, ..., ...) = 0
+0.000 listen(3, 1) = 0
+0.000 < S  0:0(0)       win 65535 <mss 1460,sackOK,eol,eol>
+0.000 > S. 0:0(0) ack 1 win 65535 <mss 1460,sackOK,eol,eol>
+0.050 <  . 1:1(0) ack 1 win 65535
+0.000 accept(3, ... ,...) = 4
+0.000 close (3) = 0
+0.000 close(4) = 0
+0.000 > F. 1:1(0) ack 1 win 65535
+0.050 < F. 1:1(0) ack 2 win 65535
+0.000 >  . 2:2(0) ack 2 win 65535

Best regards
Michael
> --
> Yoshi
>
>
> On Sun, Aug 25, 2024 at 1:02 AM yangbuwangchuxin@163.com <yangbuwangchuxin@163.com> wrote:
> I find the picture,When the server has no data to transmit, can the second and third waves be combined to reduce one wave? Because it has this delay mechanism, when there is data to be sent, it is sent, and there is no delay waiting. If something needs to be sent during the waiting period, can I do an ACK confirmation to send the merge?
>
>
> ---- Replied Message ----
> From Yoshifumi Nishida<nsd.ietf@gmail.com> Date 08/25/2024 15:34 To yangbuwangchuxin@163.com Cc tcpm<tcpm@ietf.org> Subject Re: [tcpm] Discussion on whether the TCP four-wave mechanism can be simplified to three-wave mechanism Hi Yang,
>
> OK. It seems to me that you're suggesting that when one peer sends the final FIN, it can terminate the connection without waiting for the FIN ACK.
> However, if this FIN hasn't arrived at the other end, the other end cannot know the peer has terminated the connection.
> My concern here is that the other end would be suspended in this kind of situation.
> --
> Yoshi
>
> On Sun, Aug 25, 2024 at 12:09 AM yangbuwangchuxin@163.com <yangbuwangchuxin@163.com> wrote:
> yes
>
>
> ---- Replied Message ----
> From Yoshifumi Nishida<nsd.ietf@gmail.com> Date 08/25/2024 15:05 To yangbuwangchuxin@163.com Cc tcpm<tcpm@ietf.org> Subject Re: [tcpm] Discussion on whether the TCP four-wave mechanism can be simplified to three-wave mechanism Hi Yang,
> Are you referring to the 4 way close in TCP? and you want to make it 3 way?
> --
> Yoshi
>
> On Fri, Aug 23, 2024 at 5:03 AM yangbuwangchuxin@163.com <yangbuwangchuxin@163.com> wrote:
> IEFT Hello, I am a Chinese computer major student, I have an idea is to study the TCP four wave mechanism, if one party still has data to pass, continue to open the connection. However, if both parties have no more data to transmit at a given moment, can it be possible to dispense with one wave, thus turning four waves into three? (Go straight back to the finally state at the end of the third time.) For example, is it feasible to go directly to the last step, that is, to change from the original four waves to three waves? Is there a theoretical basis for this assumption and the possibility of practical application?
>  Thank you, looking forward to reply!
>  I wish all the best!
> Yang Zhiyuan
> August 23, 2024
>  
>
> _______________________________________________
> tcpm mailing list -- tcpm@ietf.org
> To unsubscribe send an email to tcpm-leave@ietf.org
> _______________________________________________
> tcpm mailing list -- tcpm@ietf.org
> To unsubscribe send an email to tcpm-leave@ietf.org