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

<lionel.morand@orange.com> Mon, 14 October 2019 09:45 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 AA55012016E; Mon, 14 Oct 2019 02:45:20 -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 tUYbwG2e7N4B; Mon, 14 Oct 2019 02:45:19 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77A30120143; Mon, 14 Oct 2019 02:45:18 -0700 (PDT)
Received: from opfednr04.francetelecom.fr (unknown [xx.xx.xx.68]) by opfednr25.francetelecom.fr (ESMTP service) with ESMTP id 46sDF90nQyzCrLV; Mon, 14 Oct 2019 11:45:17 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.73]) by opfednr04.francetelecom.fr (ESMTP service) with ESMTP id 46sDF86JSQz1xpF; Mon, 14 Oct 2019 11:45:16 +0200 (CEST)
Received: from OPEXCAUBM41.corporate.adroot.infra.ftgroup ([fe80::857d:4f67:b0a7:10d7]) by OPEXCAUBM23.corporate.adroot.infra.ftgroup ([fe80::9108:27dc:3496:8db3%21]) with mapi id 14.03.0468.000; Mon, 14 Oct 2019 11:45:16 +0200
From: <lionel.morand@orange.com>
To: "quic@ietf.org" <quic@ietf.org>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
CC: "quic-chairs@ietf.org" <quic-chairs@ietf.org>, "httpbis-chairs@ietf.org" <httpbis-chairs@ietf.org>, "quic-ads@ietf.org" <quic-ads@ietf.org>, "httpbis-ads@ietf.org" <httpbis-ads@ietf.org>, "allison.mankin@gmail.com" <allison.mankin@gmail.com>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>, "statements@ietf.org" <statements@ietf.org>, "tsvwg-chairs@ietf.org" <tsvwg-chairs@ietf.org>
Thread-Topic: LS from 3GPP on QUIC network level troubleshooting capabilities
Thread-Index: AdWA0hpjWJ/tXLvVSCu8fqJq00l+9ABoMxcg
Date: Mon, 14 Oct 2019 09:45:16 +0000
Message-ID: <5634_1571046317_5DA443AC_5634_110_18_6B7134B31289DC4FAF731D844122B36E3A242ED0@OPEXCAUBM41.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.247]
Content-Type: multipart/mixed; boundary="_006_6B7134B31289DC4FAF731D844122B36E3A242ED0OPEXCAUBM41corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/6WKzpYVhvv8bami6niUq4QvNgvU>
Subject: [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 09:45:21 -0000

Resending to include TSVWG chairs and ensure that the LS will be listed on the IETF datatracker.

Regards,

Lionel

De : MORAND Lionel TGI/OLN
Envoyé : samedi 12 octobre 2019 10:25
À : 'quic@ietf.org'org'; 'ietf-http-wg@w3.org'
Cc : 'quic-chairs@ietf.org'org'; 'httpbis-chairs@ietf.org'org'; 'quic-ads@ietf.org'org'; 'httpbis-ads@ietf.org'org'; 'allison.mankin@gmail.com'com'; Gonzalo Camarillo
Objet : LS from 3GPP on QUIC network level troubleshooting capabilities

Hi,

Please find enclosed a liaison statement from the 3GPP CT WG 4 (CT4).
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.

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,

________________________________
[http://www.orange.com/sirius/logos_mail/orange_logo.gif]
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 <https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootService%3DSIGNATURE%26to%3D0607758936>
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.