Re: [tcpm] TCP EDO and SYN-EXT-OPT finalization - request for discussion

Yoshifumi Nishida <nsd.ietf@gmail.com> Thu, 14 October 2021 01:51 UTC

Return-Path: <nsd.ietf@gmail.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 03D4D3A17BE for <tcpm@ietfa.amsl.com>; Wed, 13 Oct 2021 18:51:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 zu_LGFsTyDSD for <tcpm@ietfa.amsl.com>; Wed, 13 Oct 2021 18:51:01 -0700 (PDT)
Received: from mail-qk1-x729.google.com (mail-qk1-x729.google.com [IPv6:2607:f8b0:4864:20::729]) (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 F20093A17BD for <tcpm@ietf.org>; Wed, 13 Oct 2021 18:51:00 -0700 (PDT)
Received: by mail-qk1-x729.google.com with SMTP id l7so4196692qkk.0 for <tcpm@ietf.org>; Wed, 13 Oct 2021 18:51:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Rh5otqDuI8KgvZE9AoLJLEHA9HruWe4kkTDWG2WnOag=; b=pmZdEf0jJzerkHGi0B9sou70IGtxAE7JAB4126DB8suzlFLto4xMjYfWwrLZ/hKfKu 0RbSpmjIvFLXQjl6WBv5Aq5bV/gFMEpvUCGKEdbtwo5mgfQp6JQGSWfsGgbKSLwqEMJ1 LEM/pjqitFpUaAvNSf0IKKO4K2E5aB9k9oQns0Tc+dqnl0JTBulu0szX/3YURaY++1Gc CXikXemxKOZhRGDMQpmYoSi1z5L0tJTnkGZiaex0Utz5uzd7kUvKN6ZlAdKRFK9BS3aG CcegrvYmYoWkL2my4qioKXjmxQpHdXLlSnFzA0xTsg4ToCh9jpfG1mJz0MO78qnAl7F6 0fJQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Rh5otqDuI8KgvZE9AoLJLEHA9HruWe4kkTDWG2WnOag=; b=XX75ewKgvILD+/dldwLzH5Wea8FArYnih4YqTigl9U7v87vS4oEBgferoS4EYDDjiK Fxepxqn8a9g23Q61sxNEefuhpYfY4xdSlijlkrsfeIxs3HZK9Hv4SoYJRXUkN6d9O5WS YCeiF/CioaraLEWe2kpZXkLy14kAtWU27GAy+rNENWe7jxHUZyHFsUE+2d8UTxAtoPVW un4o6xzPW5TUYQXftzqO52T86uUaULTzmsYYPZLkBnXjD2CViCMCARXKdM9szDQu2iUq +EuYClF8ZXjYL5wND0ZqwDGMZwE+78/+aM5dBeGO/i/+ECS2BhF14sjWLmQFLZHk+rNi mbRQ==
X-Gm-Message-State: AOAM531HqcwRuJsugCt5YPMKBQs3DDkFz/zte4Sa9TvtXnQlOxlv2+FH KAAkgxhHQ78MkmSLNytRqZCM2IWeh6ZDL3vbruw=
X-Google-Smtp-Source: ABdhPJz/oA4Aj0Qt29mAPt6CIW1GbFHVYY4fbimOB73u9+slCAoHra8O1dAjyurKBz/El0n3d6KPLUzlJQgp81qOoSw=
X-Received: by 2002:ae9:ebc2:: with SMTP id b185mr2289521qkg.491.1634176259748; Wed, 13 Oct 2021 18:50:59 -0700 (PDT)
MIME-Version: 1.0
References: <0FF01EB8-C286-481D-9694-673DC3C59C7A@strayalpha.com> <96c57846-bb58-d186-82a1-dac649370602@mti-systems.com> <23584_1634116047_6166A1CF_23584_209_1_787AE7BB302AE849A7480A190F8B93303542B124@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <CAAK044TGV0tE0q9RHbctKQLLpg6+gA6=0YMeQ6Gxcm1FqUjYXg@mail.gmail.com> <22495_1634122761_6166BC09_22495_349_9_787AE7BB302AE849A7480A190F8B93303542B25D@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
In-Reply-To: <22495_1634122761_6166BC09_22495_349_9_787AE7BB302AE849A7480A190F8B93303542B25D@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
From: Yoshifumi Nishida <nsd.ietf@gmail.com>
Date: Wed, 13 Oct 2021 18:50:48 -0700
Message-ID: <CAAK044QMFxg07_6KCLrcTctC0yUcP7UzcG9WLzgRO8ANc=CT9A@mail.gmail.com>
To: mohamed.boucadair@orange.com
Cc: Wesley Eddy <wes@mti-systems.com>, "touch@strayalpha.com" <touch@strayalpha.com>, tcpm <tcpm@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007676d705ce464fe2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/WIV_aLhwr0gXZyfBnabE78sh-Dg>
Subject: Re: [tcpm] TCP EDO and SYN-EXT-OPT finalization - request for discussion
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: Thu, 14 Oct 2021 01:51:07 -0000

Hi Med,
Thanks for the link. Yes, I think there are some common things in both
drafts.
I will definitely note or discuss it in the next version. Please allow some
time to think about this a bit more.
--
Yoshi

On Wed, Oct 13, 2021 at 3:59 AM <mohamed.boucadair@orange.com> wrote:

> Re-,
>
>
>
> Thanks for the pointer.
>
>
>
> I like the aggregation option spirit. It is advanced compared to a design
> proposal we had in
>
>
> https://datatracker.ietf.org/doc/html/draft-boucadair-tcpm-capability-option-01.
> Please note that in draft-boucadair-tcpm-capability-option, we had a
> specific applicability scope for which we don’t have the negotiation issue
> that may be applicable to draft-nishida-tcpm-agg-syn-ext. No?
>
>
>
> Cheers,
>
> Med
>
>
>
> *De :* Yoshifumi Nishida <nsd.ietf@gmail.com>
> *Envoyé :* mercredi 13 octobre 2021 12:16
> *À :* BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>
> *Cc :* Wesley Eddy <wes@mti-systems.com>om>; touch@strayalpha.com; tcpm <
> tcpm@ietf.org>
> *Objet :* Re: [tcpm] TCP EDO and SYN-EXT-OPT finalization - request for
> discussion
>
>
>
> Hi Med,
>
> FWIW, I wrote
> https://datatracker.ietf.org/doc/html/draft-nishida-tcpm-agg-syn-ext-00.txt
> which can extend SYN option space without using OOB packets.
>
> As SYN option space extension is an important and fundamental feature, I
> personally prefer to discuss the doc at the WG.
>
> --
>
> Yoshi
>
>
>
> On Wed, Oct 13, 2021 at 2:07 AM <mohamed.boucadair@orange.com> wrote:
>
> Hi all,
>
> I agree with Wes.
>
> Solving the SYN case is more problematic (e.g., consider an application
> relying upon MP_CAPABLE + FAST_OPEN). We managed to solve this specific
> issue in RFC8803 without requiring SYN-EOS/OOB, but that approach cannot be
> generalized. Having a tcpm WG document to cover the SYN case + discuss the
> issues of an OOB mechanism is useful.
>
> Cheers,
> Med
>
> > -----Message d'origine-----
> > De : tcpm <tcpm-bounces@ietf.org> De la part de Wesley Eddy
> > Envoyé : mardi 12 octobre 2021 22:07
> > À : touch@strayalpha.com; tcpm <tcpm@ietf.org>
> > Objet : Re: [tcpm] TCP EDO and SYN-EXT-OPT finalization - request for
> > discussion
> >
> > On 10/12/2021 3:50 PM, touch@strayalpha.com wrote:
> > >
> > > - are there any open issues or pending suggestions to TCP EDO to
> > > prepare it for last call?
> > >
> > I think it's in good shape for a last call.  It's stable and addresses
> all
> > of the feedback to date, aside from greater implementation and field
> > experience.  At the moment, it seems like QUIC has solved the burning
> need
> > we had for TCP options space, by attracting all the work that would
> > normally need more options. However, after many years of discussion about
> > how to handle this for TCP, and many candidates, the EDO approach was the
> > one the working group was able to get consensus around, and we really
> > should wrap up and publish it, IMHO.
> >
> >
> > > - would the WG like to adopt SYN-EXT-OPT as experimental as well or
> > > would it be preferred (and OK) to submit this as
> > > individual/experimental if not?
> > >
> > Either approach is fine with me, and I prefer either of them rather than
> > not advancing anything.  I would be willing to contribute reviews for
> > either path.
> >
> >
> > _______________________________________________
> > tcpm mailing list
> > tcpm@ietf.org
> > https://www.ietf.org/mailman/listinfo/tcpm
>
>
> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez
> recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou
> falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and
> delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been
> modified, changed or falsified.
> Thank you.
>
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm
>
> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>
>