Re: [tcpm] Comments to draft-ietf-tcpm-tcp-edo-13

"D. Wythe" <alibuda@linux.alibaba.com> Mon, 27 November 2023 06:31 UTC

Return-Path: <alibuda@linux.alibaba.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 E3FC1C14CF1D for <tcpm@ietfa.amsl.com>; Sun, 26 Nov 2023 22:31:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.999
X-Spam-Level:
X-Spam-Status: No, score=-9.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, ENV_AND_HDR_SPF_MATCH=-0.5, NICE_REPLY_A=-0.091, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
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 Grr9yjTv8-12 for <tcpm@ietfa.amsl.com>; Sun, 26 Nov 2023 22:31:53 -0800 (PST)
Received: from out30-101.freemail.mail.aliyun.com (out30-101.freemail.mail.aliyun.com [115.124.30.101]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 26524C14CF1C for <tcpm@ietf.org>; Sun, 26 Nov 2023 22:31:52 -0800 (PST)
X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R201e4; CH=green; DM=||false|; DS=||; FP=0|-1|-1|-1|0|-1|-1|-1; HT=ay29a033018045192; MF=alibuda@linux.alibaba.com; NM=1; PH=DS; RN=1; SR=0; TI=SMTPD_---0VxALF9O_1701066708;
Received: from 30.221.149.95(mailfrom:alibuda@linux.alibaba.com fp:SMTPD_---0VxALF9O_1701066708) by smtp.aliyun-inc.com; Mon, 27 Nov 2023 14:31:49 +0800
Message-ID: <8652dde1-df4b-9b42-8617-0b5d2e96956c@linux.alibaba.com>
Date: Mon, 27 Nov 2023 14:31:47 +0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.15.1
Content-Language: en-US
To: tcpm@ietf.org
References: <fc2d032a-eed3-536a-7131-f4c8ba697136@linux.alibaba.com> <CAAK044QNA9dUw=yfPLkRDOFZ58q7vFhbSKNNNADDFNayoZsuUg@mail.gmail.com> <0c8c3062-1efd-fc7c-2497-49a99f8f0b9d@linux.alibaba.com> <45b812f2-7fb1-4ace-9b7b-a810fd46fdc4@gmx.at>
From: "D. Wythe" <alibuda@linux.alibaba.com>
In-Reply-To: <45b812f2-7fb1-4ace-9b7b-a810fd46fdc4@gmx.at>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/e6ZV6Rz8hjGtJ8y2_IgSw6WZpCg>
Subject: Re: [tcpm] Comments to draft-ietf-tcpm-tcp-edo-13
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Nov 2023 06:31:55 -0000

Hi Richard,

I have reported the issues to all the organizations I observed, and some 
of them have already
started the repairs.

Always glad to make contributions.

Best wishes,
D. Wythe


On 11/23/23 7:46 PM, rs.ietf@gmx.at wrote:
>
> Hi Wythe,
>
> Since you found this example and they seem to be using github issues to
> document shortfalls and bugs - maybe you could document your finding. In
> general, reflecting unknown options and flags is a very bad practise -
> as the semantics of these extentions are unknown. And even a stateless
> SYNACK reflector could simply remove unknown things and not incur too
> much or a performance penalty.
>
> Maybe you want to give some feedback along these lines to the
> developers/maintainers of this particular codebase.
>
> Thanks for bringing it up!
>
> Richard
>
>
> Am 23.11.2023 um 07:25 schrieb D. Wythe:
>
>> A example I found is:
>>
>> https://github.com/iqiyi/dpvs/blob/master/src/ipvs/ip_vs_synproxy.c
>>
>>  From this perspective, it is worth considering that these issues may
>> only affect certain organizations and regions.
>> I agree with your point about buggy implementations, as these types of
>> issues can be never-ending and are
>> beyond the protocol's control or responsibility to handle.
>>
>> Best wishes,
>> D. Wythe
>