Re: [tsvwg] path forward on L4S issue #16

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Thu, 11 June 2020 20:33 UTC

Return-Path: <spencerdawkins.ietf@gmail.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 170673A0823 for <tsvwg@ietfa.amsl.com>; Thu, 11 Jun 2020 13:33:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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_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 XC6LUqcDe_7p for <tsvwg@ietfa.amsl.com>; Thu, 11 Jun 2020 13:33:45 -0700 (PDT)
Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com [IPv6:2a00:1450:4864:20::236]) (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 2331E3A081D for <tsvwg@ietf.org>; Thu, 11 Jun 2020 13:33:45 -0700 (PDT)
Received: by mail-lj1-x236.google.com with SMTP id n24so8492613lji.10 for <tsvwg@ietf.org>; Thu, 11 Jun 2020 13:33:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=eHAfiBgeBJtM+cDnU6vxW4nTGKsdZ3oooisHwSlk8sM=; b=GzvKOynZq5+1TphEAx6NOAfOiPzUCGsQXuQYdcJiCiT2XHOAUTmHI238bse5e9TNZL AjMdSne+O/krpkp7XlCa2fJxl8rlf+GlGtn2+OBZxUT3UQ1Bmiibff+3pz0/ME2ldHTC NrQyHcsauaPEhO1yHZrZGqJdbOPjqnxFyaiMrsdJodbwAvwI5+D8xwNqZ/KUvJFbCJXH 3/igMdXxgAjrdT0G6/LH/SWhBeXn/nUxQtMFIlIDwjJ/Yd3anu3yPfctwChO0YMcl3OH 7IsfEsQD9Aj+3KONgVwAnzPdRtXzNFl7QIQfDKcENTBVkN9KU2o0Crd/gvqbHd85Z6mc tGEg==
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:from:date :message-id:subject:to:cc; bh=eHAfiBgeBJtM+cDnU6vxW4nTGKsdZ3oooisHwSlk8sM=; b=VyFoNvaG+SDcUQOhn4JDXYLnNAWLvryrV3LuK2N5J3WHrlOU5vAFQRfla2y3enlzPk YovSJ2PliL8lMBRSIawMppIVjQ+Sjibh0nAu8t/6KAUliWcbVuO8iDGgOR3MnsOb8Me2 C4cUQWoiMcqvIkZ3vTh6NGok2y03o1M2WyNjk/KmEBb5cZeDL9eKbZ9r//bTrM77V6Hs vSp80rV1cWBMO+xLBhsPrGey84aoPc44TQAFeMkOWtk6Iz+b4KNcd7ENyEqVWKBwpeRi 1SKuxUp+fpObSiQUiZ3IQgjGgWzDFQ4E+X5c25kI1oDJ6KVlQhA3//jBHuLB1h9PNnSh hg1Q==
X-Gm-Message-State: AOAM532pd903pSeVyV2Lv1RxzSsFj1Gj98bKnOwjghfUbbEidyxYBNVv uEd3BkthAAEjsKE37djgNOM1kJh1F3vF8YVZvSQ=
X-Google-Smtp-Source: ABdhPJw/2lBK1F3DTjZg0cMDzftMPVVeZCzDR1EmSoSY+Ah53okbNrtdD9deSPAsJ+wy87Tr+1sgk5fQefwsYVZk0n4=
X-Received: by 2002:a2e:3314:: with SMTP id d20mr5159660ljc.359.1591907623229; Thu, 11 Jun 2020 13:33:43 -0700 (PDT)
MIME-Version: 1.0
References: <HE1PR0701MB2876AA3CBBA215B9FB895B0AC2820@HE1PR0701MB2876.eurprd07.prod.outlook.com> <3637517F-63A0-4862-9885-AB5EA7E6C273@gmail.com> <VI1PR0701MB2877E21B7F406C3DFCFF08BCC2820@VI1PR0701MB2877.eurprd07.prod.outlook.com> <92525827-39B6-4E88-B453-660F8FE22523@gmx.de> <VI1PR0701MB287768D465C37DC46A459C12C2820@VI1PR0701MB2877.eurprd07.prod.outlook.com> <57D7632A-594E-47BC-B6B0-5FBC22AAFE37@gmail.com> <DF67B660-DE2B-4EB8-AD77-5FECF27D1BAC@gmx.de> <HE1PR0701MB287679D1842F15FCDAC6223EC2820@HE1PR0701MB2876.eurprd07.prod.outlook.com> <7EEF7075-396F-4565-89C6-674CBB1E6CB8@gmx.de> <HE1PR0701MB28767A1E570A705EBC65EFC4C2830@HE1PR0701MB2876.eurprd07.prod.outlook.com> <5ADEBD56-1A2C-4C34-9132-E50A4A7A4A42@gmx.de> <HE1PR0701MB287695F2245A480A43DB5F9BC2830@HE1PR0701MB2876.eurprd07.prod.outlook.com> <EEB9B5D1-5F06-4BA6-A078-BE9C26D0EAD6@gmail.com> <HE1PR0701MB2876726FC67BD2850B5D39FAC2830@HE1PR0701MB2876.eurprd07.prod.outlook.com> <E17FCDCD-6D2D-4773-98AA-44EB54A79F62@gmx.de> <HE1PR0701MB287670627208FB1075F78F6DC2830@HE1PR0701MB2876.eurprd07.prod.outlook.com> <E127BDE9-0249-47CD-ACBD-1C4296258B08@gmx.de>
In-Reply-To: <E127BDE9-0249-47CD-ACBD-1C4296258B08@gmx.de>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Thu, 11 Jun 2020 15:33:16 -0500
Message-ID: <CAKKJt-faGPnkhG8NBx+k0+-a28A_FSOYsX5j8n5xLKRtmH0fZg@mail.gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000065db6f05a7d4e030"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/aThk6U9zbDJTRd7-NVzFY28Qykw>
Subject: Re: [tsvwg] path forward on L4S issue #16
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: Thu, 11 Jun 2020 20:33:47 -0000

For what it's worth ...

On Wed, Jun 10, 2020 at 3:05 PM Sebastian Moeller <moeller0@gmx.de> wrote:

> Hi Ingemar,
>
> more below in-line.
>
> > On Jun 10, 2020, at 19:15, Ingemar Johansson S <
> ingemar.s.johansson@ericsson.com> wrote:
>

snipped down to


> > 1) Do you have any public sources that confirm the numbers you quote
> below
> > ?. I tried to look up data on this but it surely is not easy.
>
>         [SM] I do not know where Jonathan's numbers come from. But
> https://datatracker.ietf.org/meeting/98/materials/slides-98-maprg-tcp-ecn-experience-with-enabling-ecn-on-the-internet-padma-bhooma-00
> has some numbers from Apple, I believe Bob cited these numbers multiple
> times in the past.
> Given the fact that 3gpp contains quite a lot of large carriers maybe that
> would be a forum to ask for numbers?
>

I have my suspicions about the likelihood of getting numbers from 3GPP
carriers, but I note that the 3GPP-IETF coordination team is becoming more
active. If someone wants to ask formally, I suppose sending a liaison
statement to 3GPP before the 3GPP plenary meetings in July would be one way
to do that.

If TSVWG thinks that's attractive, I believe the TSVWG co-chairs know more
about that process than I do, so I'll let them take it from here.

Most of my experience with asking for information like this from wireless
operators was actually with GSMA, not 3GPP itself, during and after the IAB
MARNEW workshop (https://www.iab.org/activities/workshops/marnew/ ) in
2015, and my understanding was that operators weren't willing to disclose
operational measurements to other operators, let along anyone else, because
of concerns that competitors would use that information to attract
customers away from the disclosing operator.

But maybe this could end differently in 2020.

Best,

Spencer