Re: QUIC Version Negotiation Interim

Lucas Pardue <> Fri, 23 April 2021 12:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9A9703A1BB2 for <>; Fri, 23 Apr 2021 05:38:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Status: No, score=-1.848 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id tOabSXxyFCO5 for <>; Fri, 23 Apr 2021 05:38:04 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::634]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 31A963A1BB0 for <>; Fri, 23 Apr 2021 05:38:04 -0700 (PDT)
Received: by with SMTP id x12so52934810ejc.1 for <>; Fri, 23 Apr 2021 05:38:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=SsL39ILXZeuTdAdOOQkde7dO7pZN996LBgCIf897rxk=; b=WIq4SLon/qYZMjr6ogzSh+B7Ge5N37o1pGtq5vnyYMI3OqkkUwaR3x0a0TOxcQMdhs QDxsVqrzM0vKO+mCU+kGK2wrTJ+ju1kBUBcb6t52pXyqkZ40qyFabfRiL80q2FhBF6dC DFVlWE4wx8pLGq3YDdkYLLkmEVnW/vVGv8+7+lJiPA9iT4CT5oU3Blh0h1WfJgYqQMJ3 5yQKZbFtVBfhoysi3jONtFJmXD3vllml/eiOpFZQ8gZerU5Dyh++XBFjUSy9p7mqRyhW KXoAc+CSHaY78MbjdU9CwQ+5t5c0O5XfaPYdEtDCm7b3IFwzu5pAeZjLzLlnM56BeS0+ wBMw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=SsL39ILXZeuTdAdOOQkde7dO7pZN996LBgCIf897rxk=; b=QbXYZWvLwzbYqKJdhhKYJFsQJn06fDp8cUoVuaCvZHN7bep+VPnVLWxLLzPiZdV/rL p7bcQ7hNQbFRmkmid+O3oilsnP8FiJlaRTP62bRcptvEgwK4rHrOG13xSmhJMZS+fF3x bT7qMitJFYAz8T7XNdE4yKD5zxA/k3ZpYVPj59W5t3bBe0+Fmu0+yec2KHBoTdvh7pCY rOd4eXeSGbPL+CeDTgFI+wOBb344twORU9yy0COHjRaaR/fp+3So2H5/ciFBrU1Mmd0m r9MTmtydoRurO722rmZhzWfC9IVeD843Xq5fIA192EJPmt3oB2R4tfx7Z1vK+RD282Vy h7Ug==
X-Gm-Message-State: AOAM532o0WnWSGgcdj3HbpKFq0zHuOQlNBxd7REf8UfZsnEO+Ujzricy Sj6UJjau4w+SesvL/ENtt41skV/n0v7sdOo1stk=
X-Google-Smtp-Source: ABdhPJx6FWb8/S/h/L2RQNiVsXL/pkzdJb5utbRlHhhANkFNTgcxiRlQfCCQUhwtfLO/3GMiA5A7bVpUlb8NAysIl6k=
X-Received: by 2002:a17:907:10d8:: with SMTP id rv24mr3931836ejb.542.1619181481591; Fri, 23 Apr 2021 05:38:01 -0700 (PDT)
MIME-Version: 1.0
References: <> <> <> <> <>
In-Reply-To: <>
From: Lucas Pardue <>
Date: Fri, 23 Apr 2021 13:37:52 +0100
Message-ID: <>
Subject: Re: QUIC Version Negotiation Interim
To: Marten Seemann <>
Cc: QUIC WG <>
Content-Type: multipart/alternative; boundary="00000000000009889d05c0a311ef"
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 23 Apr 2021 12:38:06 -0000

Hi Marten,

On Fri, 23 Apr 2021, 13:19 Marten Seemann, <> wrote:

> Matt shared the recording with me and I was able to watch it today. Thank
> you for that.
> In general, a processing time of 10 working days seems way too long to be
> useful for people who want to actively participate in the work. Interim
> meetings usually cause a lot of activity on the mailing list, and it's hard
> to participate in a discussion if you know that you're missing all of the
> context. After 10 working days, most discussions will most likely have
> moved on or arrived at a conclusion.
> Is there any better way we can come up with for future meetings? Sharing
> the recording in a Google Drive wouldn't be a bad solution.

I appreciate your points and agree.  Everything we can do to make the WG
participation as equivalent as possible is useful.

10 working days is an upper limit based on some factors outside the
secretariat control (such as how long it takes WebEx to present the
recording, how long YouTube encoding takes) and some factors in their
control (such as batching the manual work to upload). Mirja pointed out to
the chairs that we can request the secretariat to expedite the upload part,
so leave that with us.

Looking ahead, there is work going on that would allow interim meetings to
be held via MeetEcho. I'm not sure if that affects the turnaround time for
YouTube upload, so I've asked the question.