Re: Rechartering QUIC for Post Version 1 Work

Dmitri Tikhonov <> Tue, 26 January 2021 17:00 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 311473A0B05 for <>; Tue, 26 Jan 2021 09:00:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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 LQ1-mbucm4Ld for <>; Tue, 26 Jan 2021 09:00:58 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::f34]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DCF343A0AFB for <>; Tue, 26 Jan 2021 09:00:57 -0800 (PST)
Received: by with SMTP id u16so5739553qvo.9 for <>; Tue, 26 Jan 2021 09:00:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=date:from:to:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to; bh=dn33QsC9s6c+BlDcJZZClWFnwvRlmGV9L0eVBTxKMKM=; b=YTcvDiBRsaqDzoDIl6H3aluBeO8f8/QVqjNAdwQ86kN4STtGPRn3gXjm88M9vTwCwb WV1KwZmSaGOxVTbPqrsgsuflAUkSqzWmrs6FsyPRZFUro/dNlOS1VhAlPLAeLPU6dPG+ RNKYmfjtRwPDV8eYW4kcbpwNWjf3FK0yRPKcxdtOA0pSry0m3XVSdSRlinp3UVNrvkC2 YAiw+fvXd6wHYSTQt618T9OCDBq70ESWtCwc7wNV1dMbcCiz4LX1BLfJDyL+QWpU0dPC /gWpCNjIiozrGO8TzuDCsK1JtFXWkElwyg2+0+JDMqPVcAFz5Zm4QwLU/t1uhnDs/dfb MwaA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mail-followup-to :references:mime-version:content-disposition:in-reply-to; bh=dn33QsC9s6c+BlDcJZZClWFnwvRlmGV9L0eVBTxKMKM=; b=R5rw4l4t5FSCYyLEJ6DMuV+WMd6awEiy+I2YeZTANPw0P4Zfoulf5m9z3Wg7HlnJf3 hIu7lKbDrr6z6cCiY3jTZAqOiUM3gPrx9aUbrmB+a8DhT6LdqIv2mOq62gfsUaYtVyCZ cKQYPCvypXanDI+UzVO9cAiDMZ/D1kRA++hT+k0xtZpkXO5GBjQ09blC+T8H7CeDjkNv D/h8hHeu4bEjpmgCwNygyIzEm63LGPGJsJck5Y9GJjGggndCUrTv1mfLrXQhsZcU/cia 2BhE4irhaqYvSI9WNABJSwUTyS4pQOI74hl8jp8NVbDlBdwgetwZr9p96j/8ZBWn2RQ1 Lyww==
X-Gm-Message-State: AOAM532d2C/EjZr/rndnHxdNtSbQ9cHMhbdpQBlnERVaC+UtRk2yvQfN +blzS+/JHAr1q0+bUEkCcHwWFMZY0a2K5g==
X-Google-Smtp-Source: ABdhPJzu2OZgWUgIDgK8B8QPMhjbraBh0HIS1B3VrEDq0bncxk3tdIhkJwEuihZzXKH0ptCTyM6kuQ==
X-Received: by 2002:a05:6214:1148:: with SMTP id b8mr6390365qvt.17.1611680453149; Tue, 26 Jan 2021 09:00:53 -0800 (PST)
Received: from okhta ( []) by with ESMTPSA id o20sm13975398qki.93.2021. for <> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 26 Jan 2021 09:00:50 -0800 (PST)
Date: Tue, 26 Jan 2021 12:00:48 -0500
From: Dmitri Tikhonov <>
Subject: Re: Rechartering QUIC for Post Version 1 Work
Message-ID: <20210126170048.GB364092@okhta>
References: <>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <>
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: Tue, 26 Jan 2021 17:00:59 -0000

On Tue, Jan 26, 2021 at 04:45:23PM +0000, Lucas Pardue wrote:
> As you may have noticed, draft-iyengar-quic-delayed-ack,
> draft-marx-qlog-event-definitions-quic-h3, and
> draft-thomson-quic-bit-grease have,  based on interest to date, been marked
> as candidates for adoption by the WG. However, our current charter prevents
> us from formally adopting such work. The intention of the new charter is,
> among other things, to allow the WG to formally adopt and develop these
> drafts.

--- 8< --- snip --- 8< ---

> The second area of work is supporting the deployability of QUIC, which
> includes specifications and documents, such as it applicability and
> manageability statements, improved operation with load balancers, the
> specification of a logging format and schemas for QUIC and HTTP/3 endpoints
> (qlog), etc.

It would make the charter broader if the particular work areas were not
itemized here.  This way, a future work item, such as the (or "a") loss
bits extension (which obviosly addresses deployability concerns), cannot
be shut down with: "it is not in the second area items list and thus the
WG is not chartered to work on it."

  - Dmitri.