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

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Wed, 02 November 2022 09:52 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
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 A233FC14F73A; Wed, 2 Nov 2022 02:52:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_TEMPERROR=0.01] 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 TSpXVJFbMmXw; Wed, 2 Nov 2022 02:52:17 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:42:150::2]) by ietfa.amsl.com (Postfix) with ESMTP id D2581C14CE20; Wed, 2 Nov 2022 02:52:16 -0700 (PDT)
Received: from [192.168.1.64] (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id C18761B00079; Wed, 2 Nov 2022 09:52:09 +0000 (GMT)
Content-Type: multipart/alternative; boundary="------------OYqL4fUN8myuUhRQP4SDTkx1"
Message-ID: <f67ab6eb-2fd9-38f0-5e61-a5f1dd9c1b77@erg.abdn.ac.uk>
Date: Wed, 02 Nov 2022 09:52:08 +0000
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:102.0) Gecko/20100101 Thunderbird/102.4.1
To: Markus.Amend@telekom.de, tsvwg@ietf.org
Cc: tsvwg-chairs@ietf.org
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>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
In-Reply-To: <BE1P281MB16528975C159363DF8BFDBBFFA369@BE1P281MB1652.DEUP281.PROD.OUTLOOK.COM>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/bR9z6fhpWem-wQe6d13DCRYlIac>
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: Wed, 02 Nov 2022 09:52:21 -0000

On 01/11/2022 15:36, 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
>
This topic will be discussed at IETF-115, and thanks again this is 
helpful input,

best wishes,

Gorry Fairhurst

TSVWG Chair


> *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> <mailto: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)
>