Re: New Liaison Statement, "LS on ATSSS Phase 2 conclusions"

Behcet Sarikaya <sarikaya2012@gmail.com> Fri, 04 December 2020 16:17 UTC

Return-Path: <sarikaya2012@gmail.com>
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 E4AAB3A0EF9 for <quic@ietfa.amsl.com>; Fri, 4 Dec 2020 08:17:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level:
X-Spam-Status: No, score=-1.847 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_ENVFROM_END_DIGIT=0.25, 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 pv1Qs24FnYKg for <quic@ietfa.amsl.com>; Fri, 4 Dec 2020 08:17:52 -0800 (PST)
Received: from mail-yb1-xb2c.google.com (mail-yb1-xb2c.google.com [IPv6:2607:f8b0:4864:20::b2c]) (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 1BE363A0F47 for <quic@ietf.org>; Fri, 4 Dec 2020 08:17:42 -0800 (PST)
Received: by mail-yb1-xb2c.google.com with SMTP id g15so5870609ybq.6 for <quic@ietf.org>; Fri, 04 Dec 2020 08:17:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=dUEzxfAvzXCwsaPU34MYOjzgiTPnukx2S8+nnvwoabA=; b=cj3B1r5iqA+9syoR98omAKXzxNIe+VCYN+4+TuqVYHWg6VQdBlKNAKjzE39XReR8Uu CgGM2J6yAZqq2lQX4+ecZcA4BD6X45yi9mqTs9a3C7FN6Y/mNGom182pMiKbV/2Exuw4 FkORea7dBZ9D/ISEwejdHQhHObsWNglERL6DQOEk1pM8bXRTOvx5m1DENdw2rOsnTFRE gYNY7TdakQygarOwT1bY9rXV0NvMiFX54R7dIkm3Db2qhL9bBSj8z8z23S8CdoeCHrzy HNM7VxaV91fGSWjjasRJdLvBCbRlMdGzTRSKwW6rtwKo+xpFNfqzmeCPeVwJNW21oZrd sa/Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=dUEzxfAvzXCwsaPU34MYOjzgiTPnukx2S8+nnvwoabA=; b=StOBatTm+TRECspklmEUEcn3V0C4mO7mHbKn/s4OzHDh84X6t5XDwb99LvxopDyerN 7HYg48CDW2z3Y8F+hLdpa4C+XPrMoknf0qPHHvNHRYZuwPbMCqI3IOFgOjm0tdMjp7aI 0K8cP0IkWFaVZn4u5Xfa3T8Oj4qI0UB7eO2dtrnfIub0evEtLo0nRbUcknALycIqdKER PFYirKv2MZmPUMIvFtQiRihrWEc5hZgffrljbdRaY4J56Ta6Jm16HvHXKbYz7AC+7diI HM9c12sRYjmmS043lmz8AzOnTc6GsAHN8ilPhvFs8GJAoXKjCz5UE894cwiW8S/Spm3o cVqw==
X-Gm-Message-State: AOAM532Ad77lgpXZ1gJZwCvuPgoFI2rywpuiTb9qO/eZeRyWHCX9xHAU cRLsHajSYBFw35HZKX6rqyRhPf+PnU0IRgAKrYA=
X-Google-Smtp-Source: ABdhPJwKMyt+HXfOh2/FG18WgYq3T7RVYuVUX7gbiVtwUiY4MApT7RWZ9IRRDZ+Sg7zZYF1byF08LCIw5WYBBAoIJD0=
X-Received: by 2002:a25:cad2:: with SMTP id a201mr6659357ybg.327.1607098661049; Fri, 04 Dec 2020 08:17:41 -0800 (PST)
MIME-Version: 1.0
References: <160675082221.16479.6130039061469494989@ietfa.amsl.com> <CAOYVs2ogM86kasog5T7-XG3Nx3kZGx6Vi1id=O=0yK6WK3LHOg@mail.gmail.com> <7047_1606815783_5FC61027_7047_384_1_6B7134B31289DC4FAF731D844122B36E3A64B1F1@OPEXCAUBM41.corporate.adroot.infra.ftgroup> <CANatvzwjyfrzoX6vA4S81hABQXcpYCJ7DWEDYBnNnRLFGWMgXg@mail.gmail.com> <LEJPR01MB0635396C6C147F869AFDCD14FAF40@LEJPR01MB0635.DEUPRD01.PROD.OUTLOOK.DE> <1927_1606850062_5FC6960E_1927_422_1_6B7134B31289DC4FAF731D844122B36E3A64C3E8@OPEXCAUBM41.corporate.adroot.infra.ftgroup> <CACpbDceeYDNV7mDcj1x4w21UE3nJggoxp0vNTd8M-yn3ShhYDg@mail.gmail.com> <BYAPR02MB5176090F48871DD8E9FB9904F7F20@BYAPR02MB5176.namprd02.prod.outlook.com> <LEJPR01MB0635AA0C1EF193B23922FFDFFAF20@LEJPR01MB0635.DEUPRD01.PROD.OUTLOOK.DE> <CACpbDccetebMK26uxGVVkn2HpONDoyTYSp0s=BApRN-FOr1SmQ@mail.gmail.com>
In-Reply-To: <CACpbDccetebMK26uxGVVkn2HpONDoyTYSp0s=BApRN-FOr1SmQ@mail.gmail.com>
Reply-To: sarikaya@ieee.org
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Fri, 04 Dec 2020 10:17:29 -0600
Message-ID: <CAC8QAcdMu0Dd89X7dFrbaLjs8+QQ8nnkdTgxKuhacBBw7e7SpQ@mail.gmail.com>
Subject: Re: New Liaison Statement, "LS on ATSSS Phase 2 conclusions"
To: Jana Iyengar <jri.ietf@gmail.com>
Cc: 3GPPLiaison@etsi.org, QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000cf9a4d05b5a5d099"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/q3FlUT2OpdpjtBEKkczPOSbSbiA>
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: Fri, 04 Dec 2020 16:18:02 -0000

Hi Jana,

There is a nice overview document on ATSSS that Olivier, et al. wrote:



https://tools.ietf.org/html/draft-bonaventure-quic-atsss-overview-00

Behcet

On Thu, Dec 3, 2020 at 11:59 AM Jana Iyengar <jri.ietf@gmail.com> wrote:

> Thanks for the clarification.
>
> Do I understand correctly that the UE-UPF connection is a multipath tunnel
> then? If so, and if ordered delivery is desired, was MPTCP considered as a
> solution?
>
> - jana
>
> On Thu, Dec 3, 2020 at 1:32 AM <Markus.Amend@telekom.de> wrote:
>
>> Full ACK. 3GPP requests MP-QUIC to be applied between UE and UPF.
>> Encapsulating the traffic from services on the UE into this MP-QUIC
>> connection allows communication with the respective remote servers.
>>
>>
>>
>> Br
>>
>>
>>
>> Markus
>>
>>
>>
>> *From:* Waqar Zia <wzia@qti.qualcomm.com>
>> *Sent:* Donnerstag, 3. Dezember 2020 09:49
>> *To:* Jana Iyengar <jri.ietf@gmail.com>; lionel.morand@orange.com
>> *Cc:* magnus.westerlund@ericsson.com; lars@eggert.org;
>> statements@ietf.org; Apostolis Salkintzis <salki@motorola.com>;
>> gonzalo.camarillo@ericsson.com; 3GPPLiaison@etsi.org; chair@ietf.org;
>> lucaspardue.24.7@gmail.com; martenseemann@gmail.com; Amend, Markus <
>> Markus.Amend@telekom.de>; quic@ietf.org; martin.h.duke@gmail.com;
>> kazuhooku@gmail.com
>> *Subject:* RE: New Liaison Statement, "LS on ATSSS Phase 2 conclusions"
>>
>>
>>
>> Hi Jana,
>>
>>
>>
>> The diagram is the correct depiction as I see: the MP-QUIC connection is
>> indeed expected to be between the UE and the UPF, not between the UE and a
>> (3GPP-) external server. Hence the reordering that may happen due to use of
>> two different access technologies between the UE and UPF needs to be fixed
>> at the UPF for the uplink and at the UE for the downlink.
>>
>>
>>
>> Best regards,
>>
>> Waqar.
>>
>>
>>
>> *From:* QUIC <quic-bounces@ietf.org> *On Behalf Of *Jana Iyengar
>> *Sent:* 03 December 2020 05:55
>> *To:* lionel.morand@orange.com
>> *Cc:* magnus.westerlund@ericsson.com; lars@eggert.org;
>> statements@ietf.org; Apostolis Salkintzis <salki@motorola.com>;
>> gonzalo.camarillo@ericsson.com; 3GPPLiaison@etsi.org; chair@ietf.org;
>> lucaspardue.24.7@gmail.com; martenseemann@gmail.com;
>> Markus.Amend@telekom.de; quic@ietf.org; martin.h.duke@gmail.com;
>> kazuhooku@gmail.com
>> *Subject:* Re: New Liaison Statement, "LS on ATSSS Phase 2 conclusions"
>>
>>
>>
>> *CAUTION*: This email originated from outside of the organization.
>>
>> Speaking only as a user of computer technology, thanks for making this
>> more palatable as a PDF. A few questions:
>>
>>
>>
>> - I am a bit confused by the picture, and Spencer or someone else can
>> point me to something that I haven't read yet -- I thought the QUIC
>> connection was between the remote server and the UE, not between the UPF
>> and the UE. Am I missing something?
>>
>> - Assuming that the QUIC connection is between the UE and the remote
>> server: Since only endpoints can see the packet numbers, how are the
>> packets supposed to be re-sequenced at any point in the middle (the UPF)?
>>
>>
>>
>> Thanks!
>>
>> - jana
>>
>>
>>
>> On Tue, Dec 1, 2020 at 11:14 AM <lionel.morand@orange.com> wrote:
>>
>> Including Apostolis into the loop.
>>
>>
>>
>> *De :* Markus.Amend@telekom.de [mailto:Markus.Amend@telekom.de]
>> *Envoyé :* mardi 1 décembre 2020 12:07
>> *À :* kazuhooku@gmail.com; MORAND Lionel TGI/OLN <
>> lionel.morand@orange.com>
>> *Cc :* magnus.westerlund@ericsson.com; statements@ietf.org;
>> gonzalo.camarillo@ericsson.com; 3GPPLiaison@etsi.org; chair@ietf.org;
>> lucaspardue.24.7@gmail.com; martenseemann@gmail.com; lars@eggert.org;
>> quic@ietf.org; martin.h.duke@gmail.com
>> *Objet :* RE: New Liaison Statement, "LS on ATSSS Phase 2 conclusions"
>>
>>
>>
>> Thanks for raising this topic. With
>> https://tools.ietf.org/html/draft-amend-iccrg-multipath-reordering-01 we
>> consider exactly that and try to provide input to develop/discuss different
>> re-ordering strategies. My personal belief is, that without any re-ordering
>> implementation in the UPF or UE the end-to-end delivery will be worse.
>>
>>
>>
>> *From:* QUIC <quic-bounces@ietf.org> *On Behalf Of *Kazuho Oku
>> *Sent:* Dienstag, 1. Dezember 2020 11:29
>> *To:* lionel.morand@orange.com
>> *Cc:* Magnus Westerlund <magnus.westerlund@ericsson.com>; Liaison
>> Statement Management Tool <statements@ietf.org>;
>> gonzalo.camarillo@ericsson.com; 3GPPLiaison@etsi.org; chair@ietf.org;
>> Lucas Pardue <lucaspardue.24.7@gmail.com>; Marten Seemann <
>> martenseemann@gmail.com>; Lars Eggert <lars@eggert.org>; QUIC Discussion
>> List <quic@ietf.org>; Martin Duke <martin.h.duke@gmail.com>
>> *Subject:* Re: New Liaison Statement, "LS on ATSSS Phase 2 conclusions"
>>
>>
>>
>> Lionel, thank you for converting the statement to PDF.
>>
>>
>>
>> Reading the document, I have one question.
>>
>>
>>
>> "The simultaneous transmission of a data flow across two accesses should
>> not result in out-of-order delivery"
>>
>> I wonder what this sentence means. Is it suggesting that UPF (and
>> possibly UE) would buffer packets that arrive on the faster path until the
>> packets that were sent on the slower path reach that node? To give an
>> example, let's say that UE has sent three packets: packet 1 sent using
>> WiFi, packet 2 using LTE, packet 3 using WiFi. UPF receives packets in the
>> order of 1, 3, 2. Is UPF expected to postpone the forwarding of packet 3
>> until it receives packet 2?
>>
>> I raise the question, because during the interim, some have pointed out
>> that such buffering has negative effects on loss recovery, and that we
>> should devote our efforts to designing an end-to-end multi-path design,
>> rather than having an intermediary that aggregates paths (in this case UPF).
>>
>>
>>
>>
>>
>> 2020年12月1日(火) 18:43 <lionel.morand@orange.com>:
>>
>> Hi,
>>
>>
>>
>> Here is a pdf version.
>>
>>
>>
>> Regards,
>>
>>
>>
>> Lionel
>>
>>
>>
>> *De :* Marten Seemann [mailto:martenseemann@gmail.com]
>> *Envoyé :* mardi 1 décembre 2020 05:17
>> *À :* Liaison Statement Management Tool <statements@ietf.org>
>> *Cc :* Lucas Pardue <lucaspardue.24.7@gmail.com>; Lars Eggert <
>> lars@eggert.org>; Magnus Westerlund <magnus.westerlund@ericsson.com>;
>> MORAND Lionel TGI/OLN <lionel.morand@orange.com>;
>> gonzalo.camarillo@ericsson.com; 3GPPLiaison@etsi.org; chair@ietf.org;
>> QUIC Discussion List <quic@ietf.org>; Martin Duke <
>> martin.h.duke@gmail.com>
>> *Objet :* Re: New Liaison Statement, "LS on ATSSS Phase 2 conclusions"
>>
>>
>>
>> Would it be possible to publish this document in a format that can be
>> opened by everyone without using proprietary software?
>>
>>
>>
>> Thank you,
>>
>> Marten
>>
>>
>>
>> On Mon, Nov 30, 2020 at 10:40 PM Liaison Statement Management Tool <
>> statements@ietf.org> wrote:
>>
>> Title: LS on ATSSS Phase 2 conclusions
>> Submission Date: 2020-11-30
>> URL of the IETF Web page: https://datatracker.ietf.org/liaison/1710/
>>
>> From: Susanna Kooistra <3GPPLiaison@etsi.org>
>> To: Lars Eggert <lars@eggert.org>,Lucas Pardue <
>> lucaspardue.24.7@gmail.com>
>> Cc: QUIC Discussion List <quic@ietf.org>,Martin Duke <
>> martin.h.duke@gmail.com>,Magnus Westerlund <
>> magnus.westerlund@ericsson.com>,Lucas Pardue <lucaspardue.24.7@gmail.com>,Lars
>> Eggert <lars@eggert.org>,gonzalo.camarillo@ericsson.com,chair@ietf.org
>> Response Contacts: lionel.morand@orange.com,3GPPLiaison@etsi.org
>> Technical Contacts:
>> Purpose: For information
>>
>> Body:
>> Attachments:
>>
>>     S2-2009400_8852r02
>>
>> https://www.ietf.org/lib/dt/documents/LIAISON/liaison-2020-11-30-3gpp-tsgsa-sa2-quic-ls-on-atsss-phase-2-conclusions-attachment-1.doc
>>
>>
>>
>> _________________________________________________________________________________________________________________________
>>
>>
>>
>> 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.
>>
>>
>>
>> --
>>
>> Kazuho Oku
>>
>> _________________________________________________________________________________________________________________________
>>
>>
>>
>> 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.
>>
>>