LS from 3GPP on QUIC network level troubleshooting capabilities

<> Sun, 27 October 2019 21:28 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DC70F120052 for <>; Sun, 27 Oct 2019 14:28:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.649
X-Spam-Status: No, score=-2.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id tQPrjtZGMwuL for <>; Sun, 27 Oct 2019 14:28:20 -0700 (PDT)
Received: from ( [IPv6:2603:400a:ffff:804:801e:34:0:38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 34EF3120046 for <>; Sun, 27 Oct 2019 14:28:19 -0700 (PDT)
Received: from lists by with local (Exim 4.89) (envelope-from <>) id 1iOq2h-0006tT-D8 for; Sun, 27 Oct 2019 21:25:43 +0000
Resent-Message-Id: <>
Received: from ([2603:400a:ffff:804:801e:34:0:4c]) by with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <>) id 1iOq2f-0006sb-EQ for; Sun, 27 Oct 2019 21:25:41 +0000
Received: from ([]) by with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <>) id 1iOq2d-00032I-Ds for; Sun, 27 Oct 2019 21:25:41 +0000
Received: from ([] helo=[]) by with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <>) id 1iOq2c-0001nA-Kk for; Sun, 27 Oct 2019 21:25:39 +0000
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Content-Type: multipart/alternative; boundary="Apple-Mail=_FA437583-9250-496E-8CFD-D1F2766D8117"
From: <>
Resent-From: Yves Lafon <>
Date: Mon, 14 Oct 2019 12:09:15 +0000
Cc: "" <>, "" <>, "" <>, "" <>, "" <>, Gonzalo Camarillo <>, "" <>, "" <>
Resent-Date: Sun, 27 Oct 2019 22:25:35 +0100
Message-Id: <5634_1571046317_5DA443AC_5634_110_18_6B7134B31289DC4FAF731D844122B36E3A242ED0@OPEXCAUBM41.corporate.adroot.infra.ftgroup>
Resent-To: HTTP Working Group <>
X-Name-Md5: efe3dad792d606410c9cc49cedaffc94
To: "" <>, "" <>, "" <>
X-Mailer: Apple Mail (2.3445.104.11)
X-W3C-Hub-Spam-Status: No, score=-0.7
X-W3C-Scan-Sig: 1iOq2d-00032I-Ds 382d08601f7af65030b4c9670ff9fdaa
Subject: LS from 3GPP on QUIC network level troubleshooting capabilities
Archived-At: <>
X-Mailing-List: <> archive/latest/37074
Precedence: list
List-Id: <>
List-Help: <>
List-Post: <>
List-Unsubscribe: <>

Resending to include TSVWG chairs and ensure that the LS will be listed on the IETF datatracker.
Envoyé : samedi 12 octobre 2019 10:25
À : ' <>'; ' <>'
Cc : ' <>'; ' <>'; ' <>'; ' <>'; ' <>'; Gonzalo Camarillo
Objet : LS from 3GPP on QUIC network level troubleshooting capabilities
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).

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  <> <>

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.