IETF Logo Mail Archive

Re: Draft response to Liaison Statement, "LS on ATSSS Phase 2 Requirements to IETF QUIC Working Group"

Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be> Wed, 30 September 2020 09:23 UTC

Return-Path: <olivier.bonaventure@uclouvain.be>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 879223A0400 for <quic@ietfa.amsl.com>; Wed, 30 Sep 2020 02:23:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.313
X-Spam-Level:
X-Spam-Status: No, score=-2.313 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, MSGID_FROM_MTA_HEADER=0.001, NICE_REPLY_A=-0.213, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=uclouvain.be
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 leo6D_6TcQby for <quic@ietfa.amsl.com>; Wed, 30 Sep 2020 02:23:49 -0700 (PDT)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-eopbgr150099.outbound.protection.outlook.com [40.107.15.99]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 556343A03F5 for <quic@ietf.org>; Wed, 30 Sep 2020 02:23:48 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=cCj+6y0h0FosN2aa4UDi/zxW9lTNp7LbPfhoHPQVaAy8woavEa/gUzbLYU+ZPOHjavnB3ut9xk9btOsSdLS1xOBCDQ3Ys3ZpcgdnkwRKEdcp6sMI3t5kkxPMMOtGAtl4jAwgMFqmAQNE2YIMChBLLBKJLL/Ns/po+JbH8ssO9ZUbUGhpkRHNC3ysWhZTsGMH9BvlvNrjbb56ZftwT6ZTIuLinJC5JPw5vk10Zum7ujVV++bKkAXwtefslM/xHxB2ygFzg4O4oMx3MGZBX2kxoiwsvrvyxhN33w8arSEjDSewixXla5m2spRYWyLaRDK9Wzfz17FKc/AUTYgXbSdURw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ssjvOgc7atedD4N+b5G3EzImEbMvEhHShemRaHIU3I8=; b=cRXrugzRXntA4JgmYTYbKmGvZRKp/DpRB2N6Fim3Fw4h+6vUYKyWJPGFyCnA/wrTGVRzUkhiCfKQb0+2pRmdNF1LCWAVxz5biWxOZu5JdKlYCqzvPcfF4xqCvOof9O6y2jA/xJ7EuBV1fZviaBgwtQ0N9/L/VZUDYzGUGbPGgJDr/8h3E5QF99X52FBSOz38qEC7NIPtoognlAC+aFiAFGB/3YRmaYCTNmFDu0Pc+DuXa9FF5f20DzldG6dGPpAOKN/fwD1I9ggesZRqu7fELZLSEJonmP7NwrVdUw5dqfvP4a3j2vi+av8e3V8Cw7igNg5MNF74uvvQCU32mSkyTQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=uclouvain.be; dmarc=pass action=none header.from=uclouvain.be; dkim=pass header.d=uclouvain.be; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uclouvain.be; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ssjvOgc7atedD4N+b5G3EzImEbMvEhHShemRaHIU3I8=; b=wK2de4bwKfX1O20ug+fKLVylmW2Oymw8V17bF5T0CSxJB1aEimS6NuVE1za+HkIucyIa3oWcdziDU6XLHacjrIFi6iedBr0T9UoJUfbXAAueQJAhaXMKe5qzZyLIIeHhFmp7bLSmS8QizxJOp+ZicBp5N0U0tO34/hF3kbMNH58=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=uclouvain.be;
Received: from AM7PR03MB6642.eurprd03.prod.outlook.com (2603:10a6:20b:1bf::6) by AM6PR03MB4277.eurprd03.prod.outlook.com (2603:10a6:20b:2::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3412.25; Wed, 30 Sep 2020 09:23:46 +0000
Received: from AM7PR03MB6642.eurprd03.prod.outlook.com ([fe80::1cd6:a808:56a3:e868]) by AM7PR03MB6642.eurprd03.prod.outlook.com ([fe80::1cd6:a808:56a3:e868%6]) with mapi id 15.20.3412.029; Wed, 30 Sep 2020 09:23:46 +0000
Reply-To: Olivier.Bonaventure@uclouvain.be
Subject: Re: Draft response to Liaison Statement, "LS on ATSSS Phase 2 Requirements to IETF QUIC Working Group"
To: Lars Eggert <lars@eggert.org>, QUIC WG <quic@ietf.org>
References: <5530E619-F6A8-4ECA-A9E9-3DE4B5DECA97@eggert.org>
From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
Message-ID: <a50d0abd-e7fd-164b-3249-8c50f37f1573@uclouvain.be>
Date: Wed, 30 Sep 2020 11:23:45 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.12.0
In-Reply-To: <5530E619-F6A8-4ECA-A9E9-3DE4B5DECA97@eggert.org>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Language: fr-classic
Content-Transfer-Encoding: 7bit
X-ClientProxiedBy: AM4PR0101CA0066.eurprd01.prod.exchangelabs.com (2603:10a6:200:41::34) To AM7PR03MB6642.eurprd03.prod.outlook.com (2603:10a6:20b:1bf::6)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from mbpobo.dhcp.info.ucl.ac.be (2001:6a8:308f:2:e98c:ad51:86a3:11b3) by AM4PR0101CA0066.eurprd01.prod.exchangelabs.com (2603:10a6:200:41::34) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.34 via Frontend Transport; Wed, 30 Sep 2020 09:23:45 +0000
X-Originating-IP: [2001:6a8:308f:2:e98c:ad51:86a3:11b3]
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 25c5d902-a73b-4571-35a5-08d865228823
X-MS-TrafficTypeDiagnostic: AM6PR03MB4277:
X-Microsoft-Antispam-PRVS: <AM6PR03MB4277F7F27B4EF7403F0C24E586330@AM6PR03MB4277.eurprd03.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:10000;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: w1wn88sJtXHO8Zguv5+/dAKtR/efWptepxsCP2lkZFb335VwRbXI+bRcCMwVUxwpWSAwY26d43Nsvd9WiGqAKkqIs1ldOvnnA919ZT4UbB1cBs8CxqcxGNMdIsSkEFjAmyPYwF+kjlpZnK92NOaUZGNUpSYhFcPE9dnyKpGr1W8vIydpgadEMxfA573K3/5R3mzMcDhmM584RKrTgcngOSoH1bfM69TAsn+TXUS89lZkdK6TLBUzVcXjbPB46KYGxZQ0E3ddayk5Y/rOcCx9lUpQd8k10lyeqyYrjAa7XLt3+hSjjOZVUlLvSA7WxJdPXW2gEskxF1yDs4fJDD73YCdKKQhVQDgG9KJonXkcVmZokLHI1gawcuHfJWG+S9zagy2r0lgQAKKELkZfpgGrFPRqlfQ0bvpJQD37On+4iNCPg1KNbxhToL0PSgO76ORY
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM7PR03MB6642.eurprd03.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(366004)(346002)(376002)(136003)(39860400002)(396003)(3450700001)(2906002)(6506007)(66556008)(66476007)(52116002)(16526019)(186003)(5660300002)(31686004)(786003)(110136005)(478600001)(316002)(8676002)(6486002)(36756003)(8936002)(6512007)(31696002)(2616005)(86362001)(83380400001)(66946007)(43740500002); DIR:OUT; SFP:1102;
X-MS-Exchange-AntiSpam-MessageData: YXgmQrt2jx6AG2OayY2fwKPjjVWPBLYAYCV128E7JcEPKkRRjwVQCdyHT6x4jRTUYjcllAXe2vK3v2dIYJwnEm14klBGgeDYgjkEj+P4bc86B2IjuN1xYousDhZU98LYHEDu6K5li7BAIoIqjGyG9zdqXvIQzZmmnxbaBFB5581bA6fPlFPOHKaTNYTBZ+ETfo8d+ZnxsVc/34IFX+wUowaDYsG0ieSCjyIwiO+OCZXQwv9cde2CeBv8DK68EHV8Kit5HAZv+qt2apfaVz6B0pU3y0gb55BcXxIrGeylwpRZK6lLDpJYu7p2PCU9uXb/+Wm7Y2kQzG5NXWlsR1lQzQ1GHRIOw1cxFy8C6WZG+tWac0DDgNX54Tcvd1+kW9dprOGROMjZ9cvWlOBEx4P/aCIsKw/nsr802HY2lWGS6B50ObAMDKx0/bC6YkQPE4Xl0Ol0/sfwh9XRzqev+ddfceX+XMkWufbW1SW8dDwsg2A8KfHsFB9Rh7/WLvKbKQXUtlQ76rsDd/V7ArRDpUiZAqIlmUk6c6CjR0AaT+h7ngKbbcJOBsj98M+PmEPbdmDJL8ChaMw04qr45vDlDJL62PshXHaIZVNINvJ4OlFrpq5MPg0Mx2o6Gr3VpYBDV6k2pR0O/jiW/RzhZAHbz62txcCfdwi4b0Md9KN3H8m+uWd8XSj/t9X6GJfFZcWBW3MRLu0L2TzoHmnW8MgtyKpTMQ==
X-OriginatorOrg: uclouvain.be
X-MS-Exchange-CrossTenant-Network-Message-Id: 25c5d902-a73b-4571-35a5-08d865228823
X-MS-Exchange-CrossTenant-AuthSource: AM7PR03MB6642.eurprd03.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 30 Sep 2020 09:23:46.2089 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 7ab090d4-fa2e-4ecf-bc7c-4127b4d582ec
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: kDpw9JOG4qcgG08pH3hLH4hUnWTQ931Ls0kd/xUFIZq61bNpu3AjwkbbSsUNGJU/DUZY6lSim9TJfx/DW+YVxTzVGBUcaDhdqBcNMrAhLkscz3m+aqI6hFCo32xlZ5Pe
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM6PR03MB4277
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/VKVRGx2kubw8Hp2Gh67_nvORbio>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Sep 2020 09:23:52 -0000

Lars, Lucas and Mark,
> 
> FYI, below is a draft of our intended response to the Liaison Statement "LS on ATSSS Phase 2 Requirements to IETF QUIC Working Group" which we intend to send next week.
> 
> Please feel free to send comments.
> 
> Thanks,
> Lars, Lucas and Mark
> 
> --
> 
> Thank you for the update on your progress and your questions. Please find our
> responses below.
> 
> On Qn-1: The future of multipath support for QUIC is currently under active
> discussion in the IETF QUIC working group. While it was part of the original
> charter due to its inclusion in the pre-IETF "Google QUIC" protocol, several

I'm very surprised by this sentence. It gives the impression that 
multipath was a feature of Google's proprietary QUIC protocol. My 
understanding based on the public documents that Google released and the 
source code is that multipath was considered by Google as they reserved 
one bit in the header to indicate multipath but that this was not fully 
implemented nor tested within Google QUIC. If Google had a specification 
of multipath QUIC, I'd be very interested in seeing this document.

My understanding of the initial charter discussion was that multipath 
was a desired feature by many of the participants in the initial charter.

> participants have argued during the last year that QUIC's connection migration
> support is sufficient for the majority of our use cases, and that full-blown
> support for multipath QUIC should consequently be abandoned as a WG deliverable.
> Other WG participants remain of the opinion that multipath support for QUIC is
> very important. Due to this active ongoing discussion, we do not have an estimate
> at this time whether WG drafts for multipath QUIC will be available in 1Q2021.
> 
> On Qn-2: The QUIC WG is chartered to provide an encrypted transport protocol.
> An option to disable encryption will hence not be standardized.
> 
> Kind regards,
> Mark Nottingham, Lucas Pardue and Lars Eggert, QUIC Working Group chairs
> 

Best regards,


Olivier

v2.23.0 | Report a Bug | By Email