Re: [tsvwg] [Ecn-sane] Comments on L4S drafts

Dave Taht <dave.taht@gmail.com> Sat, 15 June 2019 17:54 UTC

Return-Path: <dave.taht@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 A58D21200EA for <tsvwg@ietfa.amsl.com>; Sat, 15 Jun 2019 10:54:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 qn6DjC439K1B for <tsvwg@ietfa.amsl.com>; Sat, 15 Jun 2019 10:54:37 -0700 (PDT)
Received: from mail-io1-xd29.google.com (mail-io1-xd29.google.com [IPv6:2607:f8b0:4864:20::d29]) (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 3C384120019 for <tsvwg@ietf.org>; Sat, 15 Jun 2019 10:54:37 -0700 (PDT)
Received: by mail-io1-xd29.google.com with SMTP id k20so12690155ios.10 for <tsvwg@ietf.org>; Sat, 15 Jun 2019 10:54:37 -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:content-transfer-encoding; bh=UVxnYT5jvNBdjHWqsoqVQvPbhrFAN45q6bVZ2zsACHA=; b=Hge/ueHp/G3dHu5PWMXe7MUHCk8aO0dMqiLNtmkY5RwqsxMRtCap59Z3eEzMQnzFIi cV348QytQ/HGegcRlybvpMFWxbiA/Qxc5k4yAsiPFn9bGx5ZPtdrjeTDNCdwpCuFRBaL KF1ROSJQKxRSA3PPK2OQvIlbvkYR8dzRgmNbq22K5UAK9btQRKwUYnrueyj2GpsDcRM9 pUIsfip5P89zV0gma2M9OeGhjFaswPIaH+j6zJJdd41AorEEr2H0vwnpBzES5u5X+6B6 8y25/P/SPr7csgsPKRPpRd10xyNgp2FG1c5SxsbrZo9OYi7LQ3A1cdb3NnFbd3PLTgHn YL0Q==
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:content-transfer-encoding; bh=UVxnYT5jvNBdjHWqsoqVQvPbhrFAN45q6bVZ2zsACHA=; b=id9K9JusyWzVjG4KcfRKT7H2Y5p57R7BH4ilJ1fSB3HLWPA/hOOkCI1G6WJmg094XL wFFik8vIUEAm9d6F3UDSbutxFrMyT5mxhvPrrLNOb59nIDF88lKhZV0kHnXpDB7AZEP3 Bo9QUXZu5NeBg4GRYAY2oNqDn9Gu+pz2m8U3K0oTe1e6Az+Bv2Sypi/r7sderwX6C8r9 mnjxsNYhgLaMcgniz1iTTHn08jhhhdhxLFPyjouW2xy9duLSKpYY9KaLzPfaRP8JVibL QSM3DCC3X8JjBE3H+N+iR1SPIF0aKkTP5/U6E3yAJDip3NAxZzj74OkiMX5R+iv1uq96 Vstw==
X-Gm-Message-State: APjAAAW6HHrccrYA2Ey7bp1VzzF1MKHtJidBKOjnQRmOXWGOO1vjmHb5 aDoFOH+aM/2g0fwXKyvcpNDZS/pvlYU4PQqh4K8=
X-Google-Smtp-Source: APXvYqxU22VLDrk5yvBUt/hMAFir3ZGqPP2CXKPAC9DkhsNN/+2Y5uRordvnjEF9ptqquEVKhnSMrrJCk2fVzL+YnCo=
X-Received: by 2002:a6b:790a:: with SMTP id i10mr43779625iop.150.1560621276447; Sat, 15 Jun 2019 10:54:36 -0700 (PDT)
MIME-Version: 1.0
References: <HE1PR07MB4425603844DED8D36AC21B67C2110@HE1PR07MB4425.eurprd07.prod.outlook.com> <8967E7D6-F8FB-4926-87B7-7B0F1F4CEBDF@akamai.com> <CAA93jw5vrtHS1yev8AZjesLBOetp7aWKkrbXOUHemC1MNy3TvQ@mail.gmail.com>
In-Reply-To: <CAA93jw5vrtHS1yev8AZjesLBOetp7aWKkrbXOUHemC1MNy3TvQ@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
Date: Sat, 15 Jun 2019 10:54:25 -0700
Message-ID: <CAA93jw5YFtyEK-VMG-CRu4RrzRmBGQCk69P4QcUQGgncRf+Y5A@mail.gmail.com>
To: "Holland, Jake" <jholland@akamai.com>
Cc: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>, Bob Briscoe <ietf@bobbriscoe.net>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/DPHAteCnV75wmodJnDthDzduolU>
Subject: Re: [tsvwg] [Ecn-sane] Comments on L4S drafts
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: Sat, 15 Jun 2019 17:54:40 -0000

On Sat, Jun 15, 2019 at 10:44 AM Dave Taht <dave.taht@gmail.com> wrote:
>
> On Fri, Jun 14, 2019 at 11:28 AM Holland, Jake <jholland@akamai.com> wrote:
> >
> > Hi Ingemar,
> > (bcc: ecn-sane, to keep them apprised on the discussion).
> >
> > Thanks for chiming in on this.  A few comments inline:
> >
> > On 2019-06-08, 12:46, "Ingemar Johansson S" <ingemar.s.johansson@ericsson.com> wrote:
>
> > > I see many applications that can benefit greatly from L4S, besides AR/VR,

I over reacted to the second part of this sentence. AR/VR - assuming
it's over a reliable short RTT isochronous transport, can benefit from
 L4S-style techniques.

> > > there is also an increased interest in the deployment of remote control
> > > capabilities for vehicles such as cars, trucks and drones, all of which
> > > require low latency video streaming.

but not this.

> This is a poor example of a use case for l4s. The link rates in these
> cases are *wildly variable*.
>
> - in the case of a realtime command and control video stream on cars,
> trucks, drones, uav or rockets, you *want* packet loss, you want the
> most current frame or fragments thereof as closely tied to actual
> event as possible. You want to drop from the head, not the tail of the
> queue, when the rate changes, so the most
> current data is available to the operator.
>
> See any launch video from spacex for this.
>
> You also want backpressure or preferably an out of band signal to the
> encoder (if you have one) so it
> drops the encoding resolution down to the data rate ASAP, if you
> exceed the capacity, while holding the video frame rate steady.
>
> And you want to be running well below the presently observed capacity
> of the link at all times, because it's precisely when things are going
> south that you want the most data, especially if you are also
> multiplexing control traffic over the same link.
>
> --
>
> Dave Täht
> CTO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-831-205-9740



-- 

Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740