[Qlog] qlog draft-01 released
Robin MARX <robin.marx@uhasselt.be> Tue, 22 October 2019 12:33 UTC
Return-Path: <robin.marx@uhasselt.be>
X-Original-To: qlog@ietfa.amsl.com
Delivered-To: qlog@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15235120013 for <qlog@ietfa.amsl.com>; Tue, 22 Oct 2019 05:33:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 eSgSBGMpW6bm for <qlog@ietfa.amsl.com>; Tue, 22 Oct 2019 05:33:23 -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 971D512008D for <qlog@ietf.org>; Tue, 22 Oct 2019 05:33:22 -0700 (PDT)
Received: by mail-lj1-x236.google.com with SMTP id n14so16980837ljj.10 for <qlog@ietf.org>; Tue, 22 Oct 2019 05:33:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uhasselt.be; s=google; h=mime-version:from:date:message-id:subject:to; bh=tzUupPKk2itFhRBcZkfXbN/INumETjX8k9Mf342XJQE=; b=INtk+IT/xXUeJ21nKuK5HYDBspuiTwcRLVhR0Wh3CxIAKVuy/QjTF/oYed3KTnBVR5 U1+Hw5BmJZLpAaD4OsVGoG4FMkogr9a54qANw99bX36Ckl/38jjeFG7dRH1np00AIA9g boqlkjUzxBy8RAi+PAv8+4XdEhyrOn0hx1MQY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=tzUupPKk2itFhRBcZkfXbN/INumETjX8k9Mf342XJQE=; b=UWf/Fnlh00Euv3NrvpwZR4YVrwXPlnw6KUlSoRedMAT3xJGJeBGoTTSBJe6gRUVSXY nSMkrQm13PJql422Etk2Vey3Kuye136u1q8FRsfe2DnpNiez+WVBmV3CgHoWiRV6cl+0 vIVN6Vck3fPvnU7OGgd9ooCQzg2HH7mjyDa7av1T7kjOdnPiGDyML3Db64a9WMGrIhhB CLGDMkBR0YczmHzCpauFnkEJh3C24Uafwxi/q25n+Gw7qcknim1iZCJYV5sXmzBY+rND FBBHEqjYvfDdfHfNbvKDnMtND6HcbkbwHQOeq1fLZGnD3H1dXj6V+uF7x/qXSu6lie7o 0Cig==
X-Gm-Message-State: APjAAAUovFcjn6KrX87Ensfv3Vbwmn3FpzGrThsp1nqVxVaFt+nEeIfr fGSlhXDJcb1kfXmlABNYchskSkli6Cme74uQydcSvTy7k8ndUw==
X-Google-Smtp-Source: APXvYqys4swqrpE9teXtjyzQoA7wgP6X1+9Rc8lIcB8Dk6t6r4M0aoTkEN7M8QZJamyXx8FQprYGO9zDD/NVg1AuRjM=
X-Received: by 2002:a05:651c:1066:: with SMTP id y6mr2091754ljm.96.1571747600216; Tue, 22 Oct 2019 05:33:20 -0700 (PDT)
MIME-Version: 1.0
From: Robin MARX <robin.marx@uhasselt.be>
Date: Tue, 22 Oct 2019 14:33:09 +0200
Message-ID: <CAC7UV9bRRgoNWBREJEyaj0kcOM91YVS1aCqvVp+RRbefg2FzpA@mail.gmail.com>
To: qlog@ietf.org
Content-Type: multipart/alternative; boundary="000000000000634ae405957f01e3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/qlog/a3B0svjdxyfbF-z7C_vcpGAKT-E>
Subject: [Qlog] qlog draft-01 released
X-BeenThere: qlog@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <qlog.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/qlog>, <mailto:qlog-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/qlog/>
List-Post: <mailto:qlog@ietf.org>
List-Help: <mailto:qlog-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/qlog>, <mailto:qlog-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Oct 2019 12:33:25 -0000
Hello everyone, As announced two weeks ago, draft-01 of the qlog documents has now been released and can be found at: - https://tools.ietf.org/html/draft-marx-qlog-main-schema-01 - https://tools.ietf.org/html/draft-marx-qlog-event-definitions-quic-h3-01 As such, any and all feedback on this new draft is welcome. I am primarily looking for ideas on: - How to log 0-RTT related events - How to log migration related events - How to address privacy and security concerns that some have voiced - How to make qlogs available in a default way (we are currently proposing a .well-known URI) - Other missing features that would have to be added specifically for the QUIC and HTTP/3 use case I will also in Singapore and look forward to discuss some of these items with you then as well. In the meantime, we will be working on our tools and visualizations for qlog at https://qvis.edm.uhasselt.be. We are also looking at expanding qlog to other protocols, first focusing on HTTP/2 and TCP. For the latter we are combining tcpdump/pcap traces with TCP metrics extracted via eBPF to get "feature parity" with what we've gotten for QUIC and HTTP/3. It's early days, but it looks promising. With best regards, Robin -- Robin Marx PhD researcher - web performance Expertise centre for Digital Media T +32(0)11 26 84 79 - GSM +32(0)497 72 86 94 www.uhasselt.be Universiteit Hasselt - Campus Diepenbeek Agoralaan Gebouw D - B-3590 Diepenbeek Kantoor EDM-2.05
- [Qlog] qlog draft-01 released Robin MARX