Re: [tsvwg] Reminder: Advancing MP-DCCP towards a working group last call : Intended publication status

Martin Duke <martin.h.duke@gmail.com> Tue, 01 November 2022 18:39 UTC

Return-Path: <martin.h.duke@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BF7FC1524BD; Tue, 1 Nov 2022 11:39:01 -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 (2048-bit key) header.d=gmail.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 zLnKnmedXfUY; Tue, 1 Nov 2022 11:39:01 -0700 (PDT)
Received: from mail-qk1-x736.google.com (mail-qk1-x736.google.com [IPv6:2607:f8b0:4864:20::736]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 04CDDC1524BA; Tue, 1 Nov 2022 11:39:01 -0700 (PDT)
Received: by mail-qk1-x736.google.com with SMTP id k2so4624965qkk.7; Tue, 01 Nov 2022 11:39:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=lgjXWdCkVyj10cn9OeI9TawBdQmL+dVDqv3wcWgsXBA=; b=Rj8ZBoKRY7rRDrJv9O24OzlQDaQnQPErzkyvCdgDmz5EfQAQqxoq0DbBvcXWvnBEEp 8IkEA4vLxDe45VALC8WBmbjBOg/gV9XtaeMs5/Bv/zLaI0w3VWvNdeEW3EoFbHQpYAPf 6zLUR7/IIWY818y8GXMJMdfZVfBbEn/g0CE9kJ2X+mrLfq2DPcMBVnyT2BJwH64w7MhF vxl7lfcy2UAxjo6frJo95DtfD1VTYiJIsmLMglntyMs6S+LK98+MRvidS5KHFgJ8umT8 Kdf3N0coF3HLqAOESk5TAGBmkMkK79cgJht4syo2MFhqqstlCpz+H7hxbdNjuK9FAqsW OuTg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=lgjXWdCkVyj10cn9OeI9TawBdQmL+dVDqv3wcWgsXBA=; b=MXHuehy2uanihixE94HUi5hCPbSBl7V9tryM9hAggN3WdY4Ykn8+EtLawABHkdtYu5 qANq1QOpd4bY7CfNTqU2ogLXOj23NLJy94bjYCGKcNCCgH/OSaRiXbTnz91TxfCo8xpl AVrp/4jpUW385nNIZbXMxaWWnjQ/Mymx5lo74TKPsBGxqjFioYEDU7rC29nK5CFBpYLm JJZmI8Fh7LnLWhhMK+QxIpD26NLOfKkBuDZvOAC2C8LqJSO8VKWUVT35wnTT/uxq2ngO gOqlzOoiWUG8w2q0n6LfwzE77BrChuLywqGnZrfY7rdn7fOND8ga9/6U3K5ykazHMHeJ zpPg==
X-Gm-Message-State: ACrzQf2QvUWgmAl3/7q8MjEow9H1nnpRZD6C3XKXsqMpdwseWHQZBj0L ZfxBF21eKI4LpsmWNhkK/YlWLvvBfkmhD8SEETM=
X-Google-Smtp-Source: AMsMyM5aqi7bMHY6spPFJAMz9CpHYdOcv5gsGZmHQlRZSayOjzFTyTUNRcgcE2PQ9Gr/PpVDE77RyrOnuuzSeVTWR+k=
X-Received: by 2002:a05:620a:454e:b0:6ec:61a0:1865 with SMTP id u14-20020a05620a454e00b006ec61a01865mr14734454qkp.414.1667327940065; Tue, 01 Nov 2022 11:39:00 -0700 (PDT)
MIME-Version: 1.0
References: <CAM4esxTyVT7WHmiS-TtDpZpzPZsHEcuZrFszGZFvJUFT5dqHpA@mail.gmail.com> <68b1280a-14ca-39e3-b3bc-ad850cf534a9@erg.abdn.ac.uk> <80ca57c5-69ec-a4b4-d88a-1a03982c9f29@erg.abdn.ac.uk> <BE1P281MB16528975C159363DF8BFDBBFFA369@BE1P281MB1652.DEUP281.PROD.OUTLOOK.COM>
In-Reply-To: <BE1P281MB16528975C159363DF8BFDBBFFA369@BE1P281MB1652.DEUP281.PROD.OUTLOOK.COM>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Tue, 01 Nov 2022 11:38:48 -0700
Message-ID: <CAM4esxSfEoP5HKRjQ7avL1P2P7cFZY4ysYPMX4p_97GvujHxWw@mail.gmail.com>
To: Markus.Amend@telekom.de
Cc: gorry@erg.abdn.ac.uk, tsvwg@ietf.org, tsvwg-chairs@ietf.org
Content-Type: multipart/alternative; boundary="000000000000977e1d05ec6d09fd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/VA_uKlJHdxYBA1Zicu61_nIPuT4>
Subject: Re: [tsvwg] Reminder: Advancing MP-DCCP towards a working group last call : Intended publication status
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Nov 2022 18:39:01 -0000

(With no hats on)

It's true that similar efforts are happening in TCP and QUIC, but those are
likely to get much more deployment experience, as the installed base is
much wider than DCCP.

How much deployment is this going to see in the near term (in production,
not research projects or proofs of concept)?

Martin

On Tue, Nov 1, 2022 at 8:37 AM <Markus.Amend@telekom.de> wrote:

> Dear Gorry, all,
>
>
>
> after we have seen feedback from Xiaomi, BT and Vodafone who are in favour
> of PS, I formally request as one of the MP-DCCP draft authors to consider
> the move from EXP to PS.
>
>
>
> The authors of the MP-DCCP draft sharing your view Gorry and the one from
> Tengmingxuan (Xiaomi), that MP-DCCP is close to existing MP efforts in IETF
> like MPTCP and MP-QUIC, which both follow PS track.
>
>
>
> We further know that Tengmingxuan and BT have experience in implementing
> MP-DCCP and MPTCP, which further strengthens their support for PS.
>
>
>
> That’s why we don’t see any reason to stay with EXP.
>
>
>
> Br
>
>
>
> Markus
>
>
>
> *From:* tsvwg <tsvwg-bounces@ietf.org> *On Behalf Of *Gorry Fairhurst
> *Sent:* Donnerstag, 13. Oktober 2022 11:55
> *To:* tsvwg@ietf.org
> *Cc:* tsvwg-chairs@ietf.org
> *Subject:* [tsvwg] Reminder: Advancing MP-DCCP towards a working group
> last call : Intended publication status
>
>
>
> We'd like to close this topic at the next meeting.
>
> If you would like to express thoughts on what experimental work would be
> needed if draft-ietf-tsvwg-multipath-dccp were too be published as an EXP
> spec rather than a Proposed Standard, please do so either on-list or
> privately to the chairs (at tsvwg-chairs@ietf.org <tsvwg-chairs@ietf.org>
> <tsvwg-chairs@ietf.org>).
>
> Best wishes
> Gorry, David and Marten
> (TSV WG Co-Chairs)
>
> On 28/09/2022 10:26, Gorry Fairhurst wrote:
>
> TSVWG,
>
>     When MP-DCCP was adopted in 2021, it proposed publication was EXP,
>
>     based on this needing experience to complete the design. This work
>     item has now progressed in TSVWG and seems to be approaching a WGLC.
>
>     The IETF has completed related work on multipath protocol extensions
> for
>     TCP (published in 2020 as PS in RFC8824), and more recently new work
> was
>     adopted in the QUIC WG on multipath (which currently also targets PS).
>     Bearing this in mind, and the additional implementation feedback from
>     developing MP-DCCP, the chairs would welcome thoughts on what
>     experimental work would still be needed - and whether this ID should
>     target EXP or PS for publication.
>
>
>
> Notes on this topic will help the chairs to prepare for the  anticpated WG
> last call of the MP-DCCP Spec.
>
>
>
> Best wishes,
>
>
>
> Gorry, David and Marten
>
> (TSV WG Co-Chairs)
>
>
>