Re: qlog: new streaming serialization format

Robin MARX <robin.marx@uhasselt.be> Tue, 26 October 2021 15:05 UTC

Return-Path: <robin.marx@uhasselt.be>
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 E86FA3A1262 for <quic@ietfa.amsl.com>; Tue, 26 Oct 2021 08:05:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, 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 (1024-bit key) header.d=uhasselt.be
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 BIkr5ivtcgLi for <quic@ietfa.amsl.com>; Tue, 26 Oct 2021 08:05:10 -0700 (PDT)
Received: from mail-wr1-x435.google.com (mail-wr1-x435.google.com [IPv6:2a00:1450:4864:20::435]) (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 614723A1264 for <quic@ietf.org>; Tue, 26 Oct 2021 08:05:01 -0700 (PDT)
Received: by mail-wr1-x435.google.com with SMTP id o14so2575831wra.12 for <quic@ietf.org>; Tue, 26 Oct 2021 08:05:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uhasselt.be; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=5jGa9kA9HMFB3kFo0ULwWAkg3Yn23yGxLTAVI/TKfWM=; b=eJ1W+A9KXMasNVftYuP2MXkQY/UWhUX5yUESq/blILneLLlvY6IyKWQbP1VdeeHJqL dNzU1q43e/OqSJ9dPDEEs9LJrq8a3E5tYuWqJkOqfNuWMveYPLTAwMGtcLmq9z/d5UBz eYuL93VPNDOpEU+EiSUIXj2R2vPdIXpTmorCE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=5jGa9kA9HMFB3kFo0ULwWAkg3Yn23yGxLTAVI/TKfWM=; b=v7lmXlJWszKFCAhgSAYbyW/zC9LfEzbSsZ211kG0Le4bstTEk3oHDbBUexOGJmcKUE Vi/tPmF/MWsIs87ynN7Qs6CpAry0dV0h+CSrEQksp9MEN22h0PLy8gsNT8xSSZNfQ5DH X7HWunnA+Xybc+0jgAbKRm2ekcx0Kwb0+XsLx03iaGN1yy6ldaRVQvtDNnjP+F1NxRcs WqJoddC0uWGEO40OTipM/xwVcmaP6h/KTqVXckHq6cuVMJnkCq77hBOz7DYS5mhhNRUV TbL47zZg7RGk6koYn7JdspA4nQg2DzaI4cn0AVc7sH7SLORNPJiVzHF0Yi7Eir6xY+bO ExBw==
X-Gm-Message-State: AOAM531FdaRxocR2hAYs6/1KoSgI1TJrGX6G3jvJyFquYd46jo4on6fl j3amVMnzNxCi0Iz9ifB/mU4tUdpjYw1mIWhLYY1EUDwVbY6z+A==
X-Google-Smtp-Source: ABdhPJzwPsolUSe3lfjhwDstGgiNEDNjUhVe+pF3Wuam1iPvKw4fPhAuwzWIYc1vcvIWnml10YxiRMWioHG4VP+2+8U=
X-Received: by 2002:a05:6000:110b:: with SMTP id z11mr5793985wrw.172.1635260694307; Tue, 26 Oct 2021 08:04:54 -0700 (PDT)
MIME-Version: 1.0
References: <CAC7UV9ZqyDKAVctj6Q=NfAG=-sXvBJ+2fwScrWd8qhkUkKjPLw@mail.gmail.com>
In-Reply-To: <CAC7UV9ZqyDKAVctj6Q=NfAG=-sXvBJ+2fwScrWd8qhkUkKjPLw@mail.gmail.com>
From: Robin MARX <robin.marx@uhasselt.be>
Date: Tue, 26 Oct 2021 17:04:48 +0200
Message-ID: <CAC7UV9Zx-2BaKHDSNWTNnbRQK-kpGHBm+hM_13gCvyh+Pg+UVw@mail.gmail.com>
Subject: Re: qlog: new streaming serialization format
To: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ccbb5b05cf42cc27"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/kwy7rscQFzXngHBMPEnQEWsLBus>
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: Tue, 26 Oct 2021 15:05:16 -0000

Hello all,

Thanks to everyone who provided feedback on the github issue.

We have now released a new draft of the qlog main schema detailing the new
streaming format [1].
qvis [2] has also been updated to support the new approach, so you can load
files using the new format/extension.
If you encounter any issues, please let me know.

I will be available during the hackathon next week for people who want to
implement this new setup and have questions/find bugs/etc.

I am also open to discuss qlog/qvis support for other emerging use cases,
such as multipath, masque, webtransport, etc. if people are interested.


[1]: https://www.ietf.org/id/draft-ietf-quic-qlog-main-schema-01.html
[2]: https://qvis.quictools.info/

With best regards,
Robin


On Wed, 20 Oct 2021 at 16:19, Robin MARX <robin.marx@uhasselt.be> wrote:

> Hello everyone,
>
> As discussed during IETF 111, we are looking to update qlog to move to a
> new streaming serialization format.
>
> The current version uses the "Newline Delimited JSON" (NDJSON) format for
> event streaming, which, while it works well, is not an official standard
> (in the IETF or elsewhere).
>
> As such, it was proposed we move to the "JSON text-sequences" format
> defined in RFC 7464 [1]. json-seq separates each record (qlog event in our
> case) with the Record Separator character (\x1E) and a \n at the end. As
> such, it should be easy to update an existing NDJSON implementation (as it
> just requires outputting one additional character per event).
>
> We have prototyped and tested this approach in qvis and various other
> tools like jq and the early outcomes are looking good [2].
>
> As such, we will be preparing a PR and associated draft-01 for IETF 112
> that introduces this change.
>
> In the meantime, it would be great if people interested in event streaming
> or with existing NDJSON qlog stacks could look at the proposal/early
> results [2] and provide feedback.
>
> [1]: https://datatracker.ietf.org/doc/html/rfc7464
> [2]: https://github.com/quicwg/qlog/issues/172
>
>
> With best regards,
> the qlog editors
>
> P.S. note that we also still plan to keep the normal JSON non-streaming
> format intact, leading to two "main" formats defined in the spec: 1) normal
> JSON and 2) JSON text sequences.
>
> --
>
> dr. Robin Marx
> Postdoc researcher - Web protocols
> Expertise centre for Digital Media
>
> *Cellphone *+32(0)497 72 86 94
>
> www.uhasselt.be
> Universiteit Hasselt - Campus Diepenbeek
> Agoralaan Gebouw D - B-3590 Diepenbeek
> Kantoor EDM-2.05
>
>
>

-- 

dr. Robin Marx
Postdoc researcher - Web protocols
Expertise centre for Digital Media

*Cellphone *+32(0)497 72 86 94

www.uhasselt.be
Universiteit Hasselt - Campus Diepenbeek
Agoralaan Gebouw D - B-3590 Diepenbeek
Kantoor EDM-2.05