Re: More context on ATSSS use case

Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be> Mon, 26 October 2020 08:29 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 565DB3A19BA for <quic@ietfa.amsl.com>; Mon, 26 Oct 2020 01:29:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.347
X-Spam-Level:
X-Spam-Status: No, score=-2.347 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.247, 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 eLKEMN_Si5PI for <quic@ietfa.amsl.com>; Mon, 26 Oct 2020 01:29:38 -0700 (PDT)
Received: from EUR05-DB8-obe.outbound.protection.outlook.com (mail-db8eur05on2120.outbound.protection.outlook.com [40.107.20.120]) (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 ECF5B3A19B9 for <quic@ietf.org>; Mon, 26 Oct 2020 01:29:37 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=LlgEAM1zT2MAlXCgmd07CnWlE34urURFj9R4cId4dn0973uHVGy1B5Ln+FGPB+gY1HxfzPaLp3zSjCkylKxMGjNdbWVFYRpqx2KSxQGu1x+En+f45T/nxx5zBdB404p+Sv/bqWMYw3NGKMjbv4vT8dbS0G0+LytZIHMhHAOZ9U6T4kOPBQQOOl8RcKPkhpyk2W/Nz1mZ0wPP4D5m2xULltmjuwx/Un1gISGUsl53h5j/kXP1RgNaaWghYmTQNM7rIUgPxxhhu2FuKr6FtgGX5mAlNTaKKVCBtjXOO0x2jJ5d/zhJD50nufGD5ky2LGbYcttotclRTJQ0OxCLpNLxWw==
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=6QYXNzyFcN2afYBHeDDersDCRuX6NRgOh6iZpEwTYsk=; b=WtBVlQ+g0CPC1nUP1QIvdisnFXCdZ6UtSv3SGRp74I0JYHNmZYLCDC18vnw9kKBpG4oE/t5ZD2VwCJlaV+8WNpubGfwca4y1Bym8BuUYr8ikZP6CBsABxkKf/D/EL49YHLtc92sBwhXcT/jEH3CnrSrsXQwSb5DqwVxMl6Meo9P2JMZbgQuBvkFWIC1DI6BxQj/B9gjnN3AGVyCn+jnFP16hYjaMoVhK0o00P6U8efD5Zr4sLjTluANVAVsAgJdvPAUHVE2V6wqpPidlBqet6IvjDFrquL2ysUK8qlJXJaIyUr/aa0fTWfW9heLEZd7Vc6lkxNdNzGFJHPfG5JCvuQ==
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=6QYXNzyFcN2afYBHeDDersDCRuX6NRgOh6iZpEwTYsk=; b=Fp2aw1jxp2c+mV1El1fAe/41oKVGBDW7KKMBidIgqsMIk3zGw+A0h8/q3MUwhfyxtT4JViIMnn3F22b56cXSsNX4QXYCEvUdXi4sKsti3gEf7cyRkz/38y+3//AX/bED4hf9LVOXwoDWFSBSq879M91o2+5/uBYEj+WZlyETbo4=
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 AM7PR03MB6278.eurprd03.prod.outlook.com (2603:10a6:20b:13b::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3477.27; Mon, 26 Oct 2020 08:29:35 +0000
Received: from AM7PR03MB6642.eurprd03.prod.outlook.com ([fe80::b03d:e09f:4450:31cd]) by AM7PR03MB6642.eurprd03.prod.outlook.com ([fe80::b03d:e09f:4450:31cd%5]) with mapi id 15.20.3477.028; Mon, 26 Oct 2020 08:29:35 +0000
Subject: Re: More context on ATSSS use case
To: David Schinazi <dschinazi.ietf@gmail.com>, Florin Baboescu <florin.baboescu@broadcom.com>
Cc: QUIC <quic@ietf.org>
References: <50316F2A-931B-483E-B2CC-023C91AE91F0@ericsson.com> <CAPDSy+6k13fW_oQuEhmyQsMY9PH2DrVvKQ-DnJ=kQk5tTsN7TA@mail.gmail.com> <77E53AF0-6435-492A-B20A-5C18372BD1F8@ericsson.com> <CAPDSy+5pc7bPDXUT0uNu2MtD-MgVD7fXpG22eYY+7pmVBi30pw@mail.gmail.com> <0d7b0483916b3876934ed195075d8d72@mail.gmail.com> <CAPDSy+5Rfy77=iNNeg--YinfKvhmSThDJ98sN6WNyNvhX-d9MQ@mail.gmail.com>
From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
Message-ID: <02207051-fed6-44d5-5d07-6590a9edf915@uclouvain.be>
Date: Mon, 26 Oct 2020 09:29:34 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
In-Reply-To: <CAPDSy+5Rfy77=iNNeg--YinfKvhmSThDJ98sN6WNyNvhX-d9MQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Originating-IP: [2a02:2788:484:585:c409:8f52:279d:5bbb]
X-ClientProxiedBy: AM3PR04CA0147.eurprd04.prod.outlook.com (2603:10a6:207::31) To AM7PR03MB6642.eurprd03.prod.outlook.com (2603:10a6:20b:1bf::6)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [IPv6:2a02:2788:484:585:c409:8f52:279d:5bbb] (2a02:2788:484:585:c409:8f52:279d:5bbb) by AM3PR04CA0147.eurprd04.prod.outlook.com (2603:10a6:207::31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.19 via Frontend Transport; Mon, 26 Oct 2020 08:29:35 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 2361f160-a184-4967-b36c-08d879894550
X-MS-TrafficTypeDiagnostic: AM7PR03MB6278:
X-Microsoft-Antispam-PRVS: <AM7PR03MB6278B2204CFE96D67F6C17B686190@AM7PR03MB6278.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: 3waMHsAjCJeTpxx2bAwJVqTkPfNAVqND8IwJTJKfR/iykkACvAQ+x88tdv+kxAkqwgAbMqEdMkmZqje9whrBU9ipSP/AAkl55LHjIOjDPkEwq0vDJkPcYuBJWQ3lMKxQoYNf1/3dRo4U7jrt1nHASAc+vLiq7W92nfLHZcRAs3LeZeWZoGw6B8OZQ+os5nK6/wT/8KBdqO2AMsNB+7ayVM/2nLN/Dl5ICVvQOJdx3c5TWrqKzB+j5F861KC1ZhYatrO800o3uBmgfFHd5mpTcdo2JK13NQbL5WR+8HZkSZdGy5HRYjH5cyiby2I5ou0yBhNcveeBoKUzbMtCIJXEHH5bfiq3q2QvCBYfXnDPsXSxtYQztls6GpcuL9RWZhe/4H5XOJuW8/qq57dbObWly2RuCQ5VFAMhu90tujH/DHyc4u1Jgi9L/r8R2kvhNDi4pHdbotRqHLmalSzHWoSFqg==
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)(346002)(39860400002)(376002)(396003)(136003)(366004)(186003)(2616005)(16526019)(86362001)(66476007)(8676002)(66556008)(66946007)(2906002)(4326008)(31696002)(6486002)(5660300002)(31686004)(36756003)(8936002)(110136005)(83380400001)(478600001)(786003)(52116002)(966005)(316002)(43740500002); DIR:OUT; SFP:1102;
X-MS-Exchange-AntiSpam-MessageData: GJix799pXYRVHOaY5jgK3ujOSKnufGhYCsVHGjaJtY+4tP5VL3egAw7YpCzkZsZgzdGM5DFwtRcmhhwBG392PvlWNMKWwB7go9nhD2qgJ6ebLb4a3BtS8Mgiv/nbRh2pn/m8Ak4+Lt9ZvCt6tYKmL+/3SrDO0K//lqv97C6KWDG0AF3KaOD7wBXXSij05+aQBad/lvcJTIoRgP8F7xCxchK2OdIQe9dEUCVgfRNPXEFJz9S5FO1OGPd3A/LTL7nsATmOWfkvVkCORhdA0j6X1yVRoMYrkH1o5fANmln+D2XVrYjCOL/E2+ciifk3KDhy7Ov0d4DSBpTN3VQGEVkGABlRrmxaS+iDbd84DGti+61fUoJiZyUtpwkOE5wMHyqTnnHAyVU+0z6GS+NopJkRD9+uQun/dW+ULJE/c0IpQANYmZBQ0papzfWnz/yozlr6MQQuiOh43PGGRGSRl3Ry2his2fCUuCShaz+wuybZYP7h6c608iJSK7wau7NthKMIZxhWNzoy3crAQHljOTimnF40OTSoB/rsXFBKjzMSlmus8qQhYnKI/YrOyPEXCf/v5oPE0GLaMdVRKoerOwJAChBm6g9vaNIo+PmqqSNc9XLx4LuVJlG3x7h8PXffuEsE5Z13CV7WIOMfPdQ18hHOLIuPK5yRJI61oobPGbxZIcOQHOSHu2Mzjlc0UnST0DVzV44Ubxzcbo08xAOqMlCd/Q==
X-OriginatorOrg: uclouvain.be
X-MS-Exchange-CrossTenant-Network-Message-Id: 2361f160-a184-4967-b36c-08d879894550
X-MS-Exchange-CrossTenant-AuthSource: AM7PR03MB6642.eurprd03.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 26 Oct 2020 08:29:35.5243 (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: Ch3+BNepYZmCLpaQgK3SIh59HwspMay/MMKGC9XHc+ztFiq/RfN2eb5P+4b4VLyLqv5neG7eW/h4yS2bM0NS6hsy6mLxZsv3ZBnjJhHPF3J/O2rpzyadvn3Pboeleb30
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM7PR03MB6278
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/NgOzthzyi8BWk6qHTS-LaZiV4KM>
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: Mon, 26 Oct 2020 08:29:40 -0000

David,

> 
>     1)Increased capacity, 2) increased coverage and 3) increased
>     reliability.
> 
>     Let’s assume for simplicity an user which would be charged for the
>     amount of data he/she would use over a cellular network using
>     licensed spectrum while for all the data exchanged over the WiFi.
>     While the user is under a good WiFi coverage all his traffic is
>     going to be routed over the WiFi, no data traffic is going over the
>     cellular. However, when the user is in an area of limited coverage
>     or the level of interference reaches a certain threshold the quality
>     of the communication over the WiFi access degrades. As a result the
>     achievable throughput over the WiFi may get below a certain
>     threshold. At this moment the WiFi access may not be able to sustain
>     the throughput the user may require. The user may either switch over
>     to the cellular (paying a higher penalty) or use both accesses, WiFi
>     and cellular. When both accesses are used,  all the traffic below a
>     maximum threshold will go over the WiFi access, while all the
>     leftover traffic will go over the cellular access.
> 
> 
> Thank you - this is exactly the kind of user benefit I was asking for. 
> In other words: the user can save on monetary costs when watching a high 
> quality video in this very precise scenario of functional but slow Wi-Fi 
> while in range of high speed but expensive cellular. We can debate how 
> common this scenario is and how impactful the solution would be, but I 
> agree that this is an actual end-user benefit.

Today, most of the WiFi networks that the user can access are:
- home Wi-Fi where he/she has manually added a WPA/WEP key
- enterprise/school WiFi that rely on 802.1x or similar technologies

In addition to these two isolated WiFi networks, there ongoing 
deployments of roaming solutions that will allow the users to 
automatically access millions of WiFi access points.

Those who are part of the academic community know eduroam (see RFC7593) 
that basically enables any student to use with his/her credentials the 
WiFi network of any university network throughout the world.

Several network operators have deployed authentication techniques that 
enable their customers to be authenticated in any of the WiFi access 
points that they have deployed in homes and in various locations like 
shopping malls, train stations, ...

In parallel, there are efforts to enable users to roam from one of these 
managed WiFi network to another. The openroaming initiative ( 
https://wballiance.com/openroaming/ ) is one example of these solutions.

With WiFi roaming, each user will be able to potentially access millions 
of WiFi access points. These WiFi access points will provide very 
different an unpredictable performance compared to a fully managed 
cellular network. With ATSSS, users will be able to use the roaming WiFi 
networks when they work well and automatically offload/switch to 
cellular when their performance is not sufficient.

We've all experienced the situation of been connected to a WiFi network 
in a pub and then need to manually disable WiFi to force the utilisation 
of the cellular network between the pub's DSL link is currently 
overloaded. ATSSS would make this seamless for the enduser for all 
applications and will also allow to use the WiFi network for part of the 
traffic which will be beneficial for the user's bill.

I expect that this scenario will be very common

Olivier