Re: [Ext] Consensus call for qlog serialization format (issue #144)

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Thu, 05 August 2021 17:18 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7A903A1A4A; Thu, 5 Aug 2021 10:18:31 -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 TTpmstQ5ZTxZ; Thu, 5 Aug 2021 10:18:27 -0700 (PDT)
Received: from mail-vs1-xe2c.google.com (mail-vs1-xe2c.google.com [IPv6:2607:f8b0:4864:20::e2c]) (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 54D5A3A1A45; Thu, 5 Aug 2021 10:18:27 -0700 (PDT)
Received: by mail-vs1-xe2c.google.com with SMTP id a8so3525464vsl.4; Thu, 05 Aug 2021 10:18:27 -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=ea4JzK1tfZUTy7hhKWENSgfuDWf6DrDv691FgdB59+o=; b=mT9/CF1l3dPn+pf5IS0QBIRURJlMBPlsNDpZ0Bq4LQL+CZ3k7USOg+dVyI10mWSTCr jRpfgCwpfxc9ztOGl7YoJFF0gG0kbcQpX9Fk18b/yeVH51BZLbj/X3mIqPH4VSxPQQ41 EN3L18Rjj72wK22+MH8ELeOAzu0WNoHtUpIj7TEGroVyZD/FsUQLxIY96GxmmsU5dtSK yuPTxcqD0qgKnuxmbxEZSD9Pl7jiB3KBvsfgB78oHrnildY58/w50ymkJL0J+PBHwrsG mAjSEedMlGmqnFQeTE9Q006knpWOovggMZ2aPHVLDGHb+DUr0vNU7+viPDphxwbrdJjy btEw==
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=ea4JzK1tfZUTy7hhKWENSgfuDWf6DrDv691FgdB59+o=; b=i6KrjOiwyHzfBnEO0z45kRjkNRlWOuOGU3expQMdxhIsUbIQbkbKBlkoZGLa4LxEjV BRsAN31JSJKYrQ/qEd+HqIWCMSGmKe1lHKopEF7fTNkurSPOoSnKcsg8KnSL6ESv7LBS l7HC3mMcvGKiWWkIV4hQJuwlJnIG8OoTSFBqKJ36lS4PBcx/ei/tJEDezZwJEiUQ4TxL lEMq2JzeBEHhCap/4hEJ7aggfgWhShbrmSzXQE6twoxLUBhI/T1Kt5r34e8Z+45nhavu bNBjLLJGk/dFFUEKFNMfHoMM5gFf1fATCsJBYwi3zLw5lgfM6juqZDl5qdDXxOWQrPj+ i58Q==
X-Gm-Message-State: AOAM5336UVnLBH8pm4eBLYGwm/AQxOO6NL816lyUNfcpUACJiUGx2Dqd o8wjVSTi2HmR1Jz2tk2phj7HyRSA04ba0cPouBo=
X-Google-Smtp-Source: ABdhPJzEnCeyCit3EQ61Jw3kJp4wwHFP5Gh7rKAHzCKh8so+02/0tJMEmW4dveCF+X35s+c1szwYf3M+6x0PeNbjgmA=
X-Received: by 2002:a67:7f48:: with SMTP id a69mr5897228vsd.58.1628183905926; Thu, 05 Aug 2021 10:18:25 -0700 (PDT)
MIME-Version: 1.0
References: <CALGR9oZS=k8XhyfugHH6VmdMVAAj6ER8s18g5eaZqX_3hie4ig@mail.gmail.com> <46CBE180-6B80-4B29-AAE3-BABBC59A02C4@icann.org> <CALGR9obnuPNYcFh1tZanFoLE1FCRSfQ1WoEEcSL+uc_5usGNSA@mail.gmail.com> <89EE247B-A26C-4C58-863C-6C938A6BA023@icann.org> <CALGR9oa0Q=N+E3ycDMBPM6HLkeGa4anWA+taJ3f088fxbo3S4Q@mail.gmail.com> <29322B1C-D2E9-4FAD-922D-F7937F822DE2@fb.com>
In-Reply-To: <29322B1C-D2E9-4FAD-922D-F7937F822DE2@fb.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Thu, 05 Aug 2021 12:17:59 -0500
Message-ID: <CAKKJt-e_t8YGBnRrQeq2q64rT5eTotiYHmJK6vhp9rK-JEYsUg@mail.gmail.com>
Subject: Re: [Ext] Consensus call for qlog serialization format (issue #144)
To: Roberto Peon <fenix=40fb.com@dmarc.ietf.org>
Cc: Lucas Pardue <lucaspardue.24.7@gmail.com>, Paul Hoffman <paul.hoffman@icann.org>, QUIC WG <quic@ietf.org>, QUIC WG Chairs <quic-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000057828805c8d31b55"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/PrsIc6yPBw_rCqKdVcsD-yEfQSM>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Aug 2021 17:18:32 -0000

On this point ...

On Thu, Aug 5, 2021 at 11:55 AM Roberto Peon <fenix=40fb.com@dmarc.ietf.org>
wrote:

> Including at least one interoperable format is good.
> Having it be ascii is annoying (not very performant, requires more I/O,
> and thus decreases the fidelity at which we can ultimately capture events)
> …but it is probably better than nothing.
>

Having at least one interoperable format is excellent, since you and I can
always exchange data using that format.  Not having something that's fairly
widely implemented, at least among early implementers, really is "nothing",
so this is "better than nothing".

Having the baseline format be annoying can be OK, because that motivates
people to explore other formats while using the baseline format, if it's
TOO annoying.

I'm not saying it would have been a great plan, but at IETF 83 during
discussions about RTCWeb codec selections, when the choice between VP8 and
H.264 seemed deadlocked, the working group had a serious conversation about
picking H.261 as an annoying (or worse) baseline so that we didn't have
complete communication breakdowns, and then implementations could negotiate
for a better choice if that seemed necessary.

(see https://www.ietf.org/proceedings/83/minutes/minutes-83-rtcweb.txt for
proof).

Best,

Spencer