Re: [tsvwg] LS from 3GPP on QUIC network level troubleshooting capabilities

<lionel.morand@orange.com> Mon, 14 October 2019 10:14 UTC

Return-Path: <lionel.morand@orange.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 806B912016E; Mon, 14 Oct 2019 03:14:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level:
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 1SCpxUBWff9p; Mon, 14 Oct 2019 03:14:15 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87D8D120143; Mon, 14 Oct 2019 03:14:15 -0700 (PDT)
Received: from opfedar03.francetelecom.fr (unknown [xx.xx.xx.5]) by opfedar23.francetelecom.fr (ESMTP service) with ESMTP id 46sDtZ1D20zBrVq; Mon, 14 Oct 2019 12:14:14 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.70]) by opfedar03.francetelecom.fr (ESMTP service) with ESMTP id 46sDtY5kgbzCqkX; Mon, 14 Oct 2019 12:14:13 +0200 (CEST)
Received: from OPEXCAUBM41.corporate.adroot.infra.ftgroup ([fe80::857d:4f67:b0a7:10d7]) by OPEXCAUBM33.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0468.000; Mon, 14 Oct 2019 12:14:13 +0200
From: <lionel.morand@orange.com>
To: Ian Swett <ianswett@google.com>, Lars Eggert <lars@eggert.org>
CC: "httpbis-chairs@ietf.org" <httpbis-chairs@ietf.org>, "allison.mankin@gmail.com" <allison.mankin@gmail.com>, "quic-chairs@ietf.org" <quic-chairs@ietf.org>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>, "quic@ietf.org" <quic@ietf.org>, "quic-ads@ietf.org" <quic-ads@ietf.org>, "httpbis-ads@ietf.org" <httpbis-ads@ietf.org>, "tsvwg-chairs@ietf.org" <tsvwg-chairs@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: LS from 3GPP on QUIC network level troubleshooting capabilities
Thread-Index: AQHVgaDz8OgjCQSpfkiz3j/IjLIVhadZCDMAgADij6A=
Date: Mon, 14 Oct 2019 10:14:13 +0000
Message-ID: <7429_1571048053_5DA44A75_7429_244_1_6B7134B31289DC4FAF731D844122B36E3A24304B@OPEXCAUBM41.corporate.adroot.infra.ftgroup>
References: <20859_1570868686_5DA18DCE_20859_72_1_6B7134B31289DC4FAF731D844122B36E3A240FE0@OPEXCAUBM41.corporate.adroot.infra.ftgroup> <A5CA915A-9E0D-42CC-B1D6-54C3AC1B3DB0@eggert.org> <CAKcm_gObjr+EQQH1DKsvFWkJ8xkj_50NyzvLeYfkYbjw2X_K5A@mail.gmail.com>
In-Reply-To: <CAKcm_gObjr+EQQH1DKsvFWkJ8xkj_50NyzvLeYfkYbjw2X_K5A@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.247]
Content-Type: multipart/alternative; boundary="_000_6B7134B31289DC4FAF731D844122B36E3A24304BOPEXCAUBM41corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/CUJ_fYaathztsFs_fADM5oHpC7Y>
Subject: Re: [tsvwg] LS from 3GPP on QUIC network level troubleshooting capabilities
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 14 Oct 2019 10:14:19 -0000

Hi,

As said below, QUIC would be used only in the control plane and not for e2e user traffic.

Regards,

Lionel

De : Ian Swett [mailto:ianswett@google.com]
Envoyé : lundi 14 octobre 2019 00:35
À : Lars Eggert
Cc : MORAND Lionel TGI/OLN; httpbis-chairs@ietf.org; allison.mankin@gmail.com; quic-chairs@ietf.org; Gonzalo Camarillo; ietf-http-wg@w3.org; quic@ietf.org; quic-ads@ietf.org; httpbis-ads@ietf.org
Objet : Re: LS from 3GPP on QUIC network level troubleshooting capabilities

If the main concern is inability to passively measure packet loss and as Lars said this is not for end-to-end user traffic(so support for certain extensions could be assumed), then this could be a good test case for draft-ferrieuxhamchaoui-quic-lossbits<https://tools.ietf.org/html/draft-ferrieuxhamchaoui-quic-lossbits-01> to prove it works as intended and see if the mechanism needs any changes.

On Sun, Oct 13, 2019 at 4:34 AM Lars Eggert <lars@eggert.org<mailto:lars@eggert.org>> wrote:
Hi Lionel,

On 2019-10-12, at 11:24, <lionel.morand@orange.com<mailto:lionel.morand@orange.com>> <lionel.morand@orange.com<mailto:lionel.morand@orange.com>> wrote:
> Please find enclosed a liaison statement from the 3GPP CT WG 4 (CT4).

I do not see this liaison statement posted at https://datatracker.ietf.org/liaison/. Please make sure to submit it via the regular process, to keep all relevant entities in the loop.

> This WG is actually studying the introduction of QUIC as transport protocol instead of HTTP/2 in the 5G core network.
> The WG has some questions regarding the troubleshooting capabilities supported by QUIC compared to the ones available with TCP.

Based on my (limited) understanding of the 5G architecture, this use of QUIC would be as a protocol for carrying control information inside a 5G network control plane. In other words, it is not about the end-to-end use of QUIC over paths that traverse 5G networks. Is my understanding correct?

Thanks,
Lars

>  The LS is officially addressed to the QUIC WG. However, it was highlighted that httpbis WG could also be interested in. I will let you decide if only QUIC or both are relevant in the discussion.
>
> Next CT4 WG meetings:
> 3GPP TSG CT4#95           11th – 15th November 2019       Reno, US
> 3GPP TSG CT4#96           24th – 28th February 2020          Sophia Antipolis, FR
>
> It would be good to receive an official feedback at the latest for the February meeting, where the study will be concluded (at least for this release).
>
> Regards,
>
> <image001.jpg>
>
> Lionel Morand
> Chair of 3GPP TSG CT
> 3GPP Liaison Person to IETF
> Chair of IETF Dime and Radext WGs
> Core Network Senior Architect and Diameter expert
> Cell. +33 6 07 75 89 36<tel:+33%206%2007%2075%2089%2036>
> lionel.morand@orange.com<mailto:lionel.morand@orange.com>
>
>
>
>
> _________________________________________________________________________________________________________________________
>
> 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.
>
> <Liaison Statement on QUIC network level troubleshooting capabilities.docx>

_________________________________________________________________________________________________________________________

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.