[tcpm] Re: Discussion on whether the TCP four-wave mechanism can be simplified to three-wave mechanism
"yangbuwangchuxin@163.com" <yangbuwangchuxin@163.com> Sun, 25 August 2024 07: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 937E8C14CEFC for <tcpm@ietfa.amsl.com>; Sun, 25 Aug 2024 00:09:06 -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_DNSWL_NONE=-0.0001, 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 92PMuHuetH3h for <tcpm@ietfa.amsl.com>; Sun, 25 Aug 2024 00:09:05 -0700 (PDT)
Received: from m16.mail.163.com (m16.mail.163.com [117.135.210.3]) by ietfa.amsl.com (Postfix) with ESMTP id F0C04C14F71D for <tcpm@ietf.org>; Sun, 25 Aug 2024 00:09:04 -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=HH9nbYKvgt1qbQzC7ATHEBI16rga18wfB9VD3e5+Urg=; b=M IVrKgWO/6e0ghzCXmXwUkqPNbEOBrIDzA6BKSJBxbrY0lyfeM0+OjM28UVad2mXW gvL60AaYcPUT91FSL1MvnwS9emE9kPCetSecIpiFm9a0Wn5SXlDYYRnGx5QGCWyD f464rn174HRYEgv2H6nrjeaY0nT4K/OSZR+40sCWxQ=
Received: from yangbuwangchuxin$163.com ( [183.210.92.59] ) by ajax-webmail-wzpm-k8s-gz (Coremail) ; Sun, 25 Aug 2024 15:08:53 +0800 (GMT+08:00)
X-Originating-IP: [183.210.92.59]
Date: Sun, 25 Aug 2024 15:08:53 +0800
From: "yangbuwangchuxin@163.com" <yangbuwangchuxin@163.com>
To: "nsd.ietf" <nsd.ietf@gmail.com>
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: <CAAK044SZyk5LJwohkJ-Fjk1rZidq5fGKXHYBBxgUWh45aiijXA@mail.gmail.com>
References: <6defaffd.3f8b1.1917c9c2f23.Coremail.yangbuwangchuxin@163.com> <CAAK044SZyk5LJwohkJ-Fjk1rZidq5fGKXHYBBxgUWh45aiijXA@mail.gmail.com>
X-NTES-SC: AL_Qu2ZBvmdtk8o5SCfZOkfm04Xjuc9WcK0u/si249eNpt4jBvuwTotcHtsDFv62sCjFR+DjTe4UhF01/lwcZJ/fa0X0XAgtzA2lO8qSmXGyAaf6A==
Content-Type: multipart/alternative; boundary="----=_Part_1108759_2046993634.1724569733078"
MIME-Version: 1.0
Message-ID: <55af587.448d8.191885dc7d7.Coremail.yangbuwangchuxin@163.com>
X-Coremail-Locale: zh_CN
X-CM-TRANSID: _____wD3n2aG2Mpm5IEbAA--.2269W
X-CM-SenderInfo: p1dqwuxxzd0wxfkx5xrq6rljoofrz/1tbiXQhG7GXAm6lcCwABs+
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: WH4L3OFF7CEZINW77HBBI7SISYGOCAFP
X-Message-ID-Hash: WH4L3OFF7CEZINW77HBBI7SISYGOCAFP
X-Mailman-Approved-At: Sun, 25 Aug 2024 06:20:05 -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/bgtVGPY4E0Pp5I_7MmqGeOkTtec>
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>
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] Discussion on whether the TCP four-wave me… yangbuwangchuxin@163.com
- [tcpm] Re: Discussion on whether the TCP four-wav… Yoshifumi Nishida
- [tcpm] Re: Discussion on whether the TCP four-wav… yangbuwangchuxin@163.com
- [tcpm] Re: Discussion on whether the TCP four-wav… Yoshifumi Nishida
- [tcpm] Re: Discussion on whether the TCP four-wav… yangbuwangchuxin@163.com
- [tcpm] Re: Discussion on whether the TCP four-wav… yangbuwangchuxin@163.com
- [tcpm] Re: Discussion on whether the TCP four-wav… Yoshifumi Nishida
- [tcpm] Re: Discussion on whether the TCP four-wav… Michael Tuexen
- [tcpm] Re: Discussion on whether the TCP four-wav… yangbuwangchuxin@163.com