Re: [tcpm] Fwd: I-D Action: draft-nishida-tcpm-agg-syn-ext-00.txt

Kangjiao <kangjiao@huawei.com> Wed, 10 February 2021 01:14 UTC

Return-Path: <kangjiao@huawei.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 5590E3A1118 for <tcpm@ietfa.amsl.com>; Tue, 9 Feb 2021 17:14:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Tl9e3PBFUgah for <tcpm@ietfa.amsl.com>; Tue, 9 Feb 2021 17:14:19 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5A6D3A1116 for <tcpm@ietf.org>; Tue, 9 Feb 2021 17:14:18 -0800 (PST)
Received: from fraeml708-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Db1sN5Fxxz67lyl; Wed, 10 Feb 2021 09:10:32 +0800 (CST)
Received: from fraeml795-chm.china.huawei.com (10.206.15.16) by fraeml708-chm.china.huawei.com (10.206.15.36) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Wed, 10 Feb 2021 02:14:12 +0100
Received: from fraeml795-chm.china.huawei.com (10.206.15.16) by fraeml795-chm.china.huawei.com (10.206.15.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Wed, 10 Feb 2021 02:14:12 +0100
Received: from DGGEMM403-HUB.china.huawei.com (10.3.20.211) by fraeml795-chm.china.huawei.com (10.206.15.16) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.2106.2 via Frontend Transport; Wed, 10 Feb 2021 02:14:12 +0100
Received: from DGGEMM514-MBS.china.huawei.com ([169.254.3.180]) by DGGEMM403-HUB.china.huawei.com ([10.3.20.211]) with mapi id 14.03.0509.000; Wed, 10 Feb 2021 09:14:04 +0800
From: Kangjiao <kangjiao@huawei.com>
To: Yoshifumi Nishida <nsd.ietf@gmail.com>, "tcpm@ietf.org Extensions" <tcpm@ietf.org>
CC: Liangqiandeng <liangqiandeng@huawei.com>
Thread-Topic: [tcpm] Fwd: I-D Action: draft-nishida-tcpm-agg-syn-ext-00.txt
Thread-Index: AQHW+fwAzocl9W3Fpky4agCZWo0PP6pQnyjQ
Date: Wed, 10 Feb 2021 01:14:04 +0000
Message-ID: <719A2C1D4AC73847B6E1BF21DF1545EAE5E77372@dggemm514-mbs.china.huawei.com>
References: <161233469809.31214.294457730576935197@ietfa.amsl.com> <CAAK044QYBiGXKm+D+=edc8TWhjzAadBxER5VRFmJOdW8hdXFKg@mail.gmail.com>
In-Reply-To: <CAAK044QYBiGXKm+D+=edc8TWhjzAadBxER5VRFmJOdW8hdXFKg@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.67.102.89]
Content-Type: multipart/alternative; boundary="_000_719A2C1D4AC73847B6E1BF21DF1545EAE5E77372dggemm514mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/tYHHIxbLkNub5Cpwm56PGLiilp0>
Subject: Re: [tcpm] Fwd: I-D Action: draft-nishida-tcpm-agg-syn-ext-00.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 10 Feb 2021 01:14:21 -0000

Hi Yoshi,

I wrote a draft to propose an idea for MPTCP subtype capability exchange during MPTCP handshake.  We think, in MPTCP, some options are mandatory but some options can be set as optional ones. So an exchange mechanism of actual capability between both parties are needed.

URL:            https://www.ietf.org/archive/id/draft-kang-tcpm-subtype-capability-exchange-00.txt
Status:         https://datatracker.ietf.org/doc/draft-kang-tcpm-subtype-capability-exchange/
Html:           https://www.ietf.org/archive/id/draft-kang-tcpm-subtype-capability-exchange-00.html
Htmlized:       https://tools.ietf.org/html/draft-kang-tcpm-subtype-capability-exchange-00

When I read your draft, I think maybe our above work have some relevance to your suggestions. If you think it'll help with this work, I hope we can discuss this new negotiation mechanism for related options and subtypes. Thanks

Best wishes,
Jiao

From: tcpm [mailto:tcpm-bounces@ietf.org] On Behalf Of Yoshifumi Nishida
Sent: Wednesday, February 3, 2021 3:12 PM
To: tcpm@ietf.org Extensions <tcpm@ietf.org>
Subject: [tcpm] Fwd: I-D Action: draft-nishida-tcpm-agg-syn-ext-00.txt

Hi folks,

I prepared a draft for SYN option space extensions.
I know this is a difficult issue in TCP and has been discussed for a long time.
But, I'm thinking that it might be a good time to discuss it again.

Key ideas of the draft are the followings.
1: drastic changes in TCP's spec will not be required
    (it does not require updating TCP header format nor using multiple SYN packets or additional SYN-like packets)
2: utilize the option negotiation schemes in mptcp for generic purposes. so, I think it can be considered middlebox friendly.
3: it has some limitations (e.g it can only extend around 30-40 bytes for SYN option space). But, if it's combined with EDO, we can use more option space.
    (depends on how EDO draft will progress, though)

Please let me know if you have any questions or comments or suggestions.

Thank you so much!
--
Yoshi


---------- Forwarded message ---------
From: <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
Date: Tue, Feb 2, 2021 at 10:45 PM
Subject: I-D Action: draft-nishida-tcpm-agg-syn-ext-00.txt
To: <i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>>



A New Internet-Draft is available from the on-line Internet-Drafts directories.


        Title           : Aggregated Option for SYN Option Space Extension
        Author          : Yoshifumi Nishida
        Filename        : draft-nishida-tcpm-agg-syn-ext-00.txt
        Pages           : 14
        Date            : 2021-02-02

Abstract:
   TCP option space is scarce resource as its max length is limited to
   40 bytes.  This limitation becomes more significant in SYN segments
   as all options used in a connection should be exchanged during SYN
   negotiations.  This document proposes a new SYN option negotiation
   scheme that provide a feature to compress TCP options in SYN segments
   and provide more option space.  The proposed scheme does not update
   the format of TCP header nor transmit any additional SYN or SYN-like
   segments so that it has lower risks for middlebox interventions.  In
   addition, by combining another proposal for option space extension,
   it is possible to provide further option space.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-nishida-tcpm-agg-syn-ext/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-nishida-tcpm-agg-syn-ext-00
https://datatracker.ietf.org/doc/html/draft-nishida-tcpm-agg-syn-ext-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org<http://tools.ietf.org>.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org<mailto:I-D-Announce@ietf.org>
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt