Re: [tcpm] Progressing draft-ietf-tcpm-converters

Yuchung Cheng <ycheng@google.com> Mon, 03 June 2019 19:09 UTC

Return-Path: <ycheng@google.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 AADAC12062A for <tcpm@ietfa.amsl.com>; Mon, 3 Jun 2019 12:09:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.509
X-Spam-Level:
X-Spam-Status: No, score=-17.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 nAG6HLsJIMNR for <tcpm@ietfa.amsl.com>; Mon, 3 Jun 2019 12:09:57 -0700 (PDT)
Received: from mail-wm1-x330.google.com (mail-wm1-x330.google.com [IPv6:2a00:1450:4864:20::330]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8499F12064B for <tcpm@ietf.org>; Mon, 3 Jun 2019 12:09:56 -0700 (PDT)
Received: by mail-wm1-x330.google.com with SMTP id s3so5039152wms.2 for <tcpm@ietf.org>; Mon, 03 Jun 2019 12:09:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=zR+EZCGd0ZW062+hVucKrV6DjjeSV80h2Bw0CfaAa5E=; b=kBqG1Lm5CKhJygyjwquU2FRvVwrjvtY/fHqOVMwqkIrMbtyljsTS/DqP2wl/yiAm9q aIKH7zaluIDngglvMySUsCrcCkMnth5wSWmUuv6q+0uHLT/25yrfHWVwqhUYYXSGF9IQ m5g3wDpzos4hG+oWvbABrpiYCxvQQ47yq8LXb3s5LLLMbHiYCQBDYc32nMeY1oPGIt/t iGfZ/3Qe+W1gqszUeMWy6iy6+LjdyWTpbOtYL63C9hoGuBb88gY3sD/yY7YY/oNpjo4G BBqs1cNw9KoZqCWBuLmHqGbci+2JvJvo418J35Cf64GQcBgn0ai8g4mQymXHLmA+8UwI KcLA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=zR+EZCGd0ZW062+hVucKrV6DjjeSV80h2Bw0CfaAa5E=; b=VKBgyNmWT6cALFdysGphfLtX43JV7OATbjqJOqtA9nSYyld0tl7gMiG4DZY3B7vATe L1ez03atxIBX/9Tqsrl/Lh6HSkM32PJlVEHtHQCWXQPF63Dc67u5v1oJpsz2BzdIpogw u3lu9P2wDrsQW/eXC+nvCOSgDzVYdDrNldj6QXxND9CqYHBFbL5Jtbs2wfpLsdLeSyFW 6Qh1okw1pHET2iJn3oz97lWsTXBm78fgl0TWqXA9Katsc2GAO7Yn5HcBOIkK2GP45zom ktegvqCL4Xv5c1lAXd7SHIIXjsGDX6FJKYsClChi9eWoSgdbWQ/yQ+7WXk1ZSQbuobJs B8VA==
X-Gm-Message-State: APjAAAX9cQw6hp2o+OxX1FwcOKSboZfK0FmZm4xokmTHCOAbrRLvdgV7 IkTAhLfRqt/bKrIrHzmwpZDY5TAiGe4IpVr66TmzfA==
X-Google-Smtp-Source: APXvYqzLjgwBlyuKq+loeT3gugdOvk/g+9Ortdw9+0WHm5Ty/kyQ0iT2/EtlNqiFZwZfDHC9E1AbbarzfV0qXDkG3vc=
X-Received: by 2002:a05:600c:291:: with SMTP id 17mr4633029wmk.32.1559588994434; Mon, 03 Jun 2019 12:09:54 -0700 (PDT)
MIME-Version: 1.0
References: <F92BF1E2-60EB-4E48-84A4-1C82589A056A@tessares.net> <CAK6E8=f-TAUWs3x4P9XHUHbvRhOqBhH9GU910Yoy5v_0vzUxAQ@mail.gmail.com> <A0496204-331F-4D8E-A1C1-83D3E1CE759B@tessares.net> <CAK6E8=e0RVzfRA0j=y8EZK0HonH6vaMBL6m-U3L+8cNO-zpqqw@mail.gmail.com> <787AE7BB302AE849A7480A190F8B93302EA8E8EF@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <CAK6E8=cDrLB0Oop2act7jCe_CYnNd2gJZU06ZHg_zJXXh_VOXg@mail.gmail.com> <MW2PR2101MB1049E8330D990998817F1A82B6020@MW2PR2101MB1049.namprd21.prod.outlook.com> <787AE7BB302AE849A7480A190F8B93302EA8F7C3@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <MW2PR2101MB10493385260DA9D53B92B1A4B61E0@MW2PR2101MB1049.namprd21.prod.outlook.com> <4258DCF5-1588-4B97-9C05-F0722E053072@tessares.net> <MW2PR2101MB1049AF12221F9EE37133F603B61F0@MW2PR2101MB1049.namprd21.prod.outlook.com> <3d979013-16d3-689f-45cb-e5b007fe7f13@wizmail.org> <CAK6E8=fjfk=EMfvRL_eqco3-Siz1fHN46hAANwspDzK8vf+1kA@mail.gmail.com> <70e482bb-b1d6-f50b-2032-4707013ccfc9@wizmail.org>
In-Reply-To: <70e482bb-b1d6-f50b-2032-4707013ccfc9@wizmail.org>
From: Yuchung Cheng <ycheng@google.com>
Date: Mon, 3 Jun 2019 12:09:15 -0700
Message-ID: <CAK6E8=cjxghmbV7x7nRhNtA7WjoA3BNy7yN8X_bJfAPYU7ruCQ@mail.gmail.com>
To: Jeremy Harris <jgh@wizmail.org>
Cc: "tcpm@ietf.org Extensions" <tcpm@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/yxp_sv5lG4GvaeresxHJ3WOU-0k>
Subject: Re: [tcpm] Progressing draft-ietf-tcpm-converters
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: Mon, 03 Jun 2019 19:10:00 -0000

On Mon, Jun 3, 2019 at 11:09 AM Jeremy Harris <jgh@wizmail.org>; wrote:
>
> On 03/06/2019 18:58, Yuchung Cheng wrote:
> > On Mon, Jun 3, 2019 at 7:37 AM Jeremy Harris <jgh@wizmail.org>; wrote:
> >>
> >> On 29/05/2019 17:27, Praveen Balasubramanian wrote:
> >>> 2. Ability to RECEIVE data in SYN payload on server. This is only supported on all OS *after* 3WHS is completed. This is per RFC 793. The only exception is if TFO API is used, and then if cookie is validated the application will  receive early-data. There is no way to retrieve early data otherwise.
> >>
> >> There is a bit in the tcp_fastopen sysctl for Linux described so:
> >>
> >>     0x200: (server) accept data-in-SYN w/o any cookie option present.
> >>
> >> It doesn't say explicitly that the data is presented to the application
> >> (neither does the doc for the with-cookie server TFO control bit).
> >> Does anybody know whether it is?
> > I am not sure what you mean - what is "it" in your last question?
>
> Whether the data, that arrived on the SYN, is available to the
> application (before, the item I forgot to specify, the ACK for the
> SYN,ACK arrives at the server).
Then answer is yes (if not clear from my previous post).

>
> > when this option is used (0x200), TFO will accept the data in SYN w/o
> > or w/ any cookie. Accept(2) will return in 3WHS. but note that SYN-ACK
> > is returned immediately upon receiving SYN-data in this mode. so this
> > mode will not support the latest tcpm-converter proposal where SYN-ack
> > is delayed upon (in-data) cookie verification and proxy 3WHS
> > completion. This change requires non-trivial implementation for a
> > listener handling millions of requests in Linux.
>
> That's a separate point of interest, as is whether it will ever be
> feasible to carry data on the SYN,ACK (either for cookieless or
> cookieful mode).
>
> --
> Cheers,
>   Jeremy
>
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm