From nobody Mon Jan 11 13:13:19 2021 Return-Path: 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 B3DA13A10FE for ; Mon, 11 Jan 2021 13:13:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.181 X-Spam-Level: X-Spam-Status: No, score=-2.181 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.262, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net 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 2ZfitD4kHtaK for ; Mon, 11 Jan 2021 13:13:16 -0800 (PST) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6BCC3A10FD for ; Mon, 11 Jan 2021 13:13:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1610399589; bh=8KBnbP1F0weunBoc1wbIrDfWPEjNfEiBbv2Isdkrj9E=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=LbfkAxS13VXMkpgpbxGq2dSw/Jjzo0vroH+au1foKvC6JVY1a9rhnsW27lNnv/p83 cDPF/UYIkQGQM8LB9XXnZDHcrFxLHZxsVgw5BItOIhl6ZtPq9bwImyDTL/nYhlsGti P/ofcOLVzSrcpWrdC3pfmrpa0PuTnyOty4bF0gPQ= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.178.182] ([91.61.48.191]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1Mzhj9-1k44041F6f-00vixp for ; Mon, 11 Jan 2021 22:13:09 +0100 Subject: Re: HTTP Delays To: quic@ietf.org References: From: Julian Reschke Message-ID: <26f18d06-c03e-c77f-5079-f742a32cd0fc@gmx.de> Date: Mon, 11 Jan 2021 22:13:07 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:oc1FjrTIuXVrh8wvW2dSdv30lH/+7/QfTLSzUJu/ekJfhoIF9Ax LopTfBqh3adXJBg7yZOrcuToGM8KK/ozGxIChnMGE2RwYBZWDmoQ29Y9CEbE1hS5WtWl9mk 2cYCi7etec1xfQXS5wT0K0e/1myIHPrd7rdXxN1ODxDKg3x14CZLkYtOmiVtXivT4+FoM9c de19ptGmthFNzoPaD1KVg== X-UI-Out-Filterresults: notjunk:1;V03:K0:v9UKV8zJ7kA=:Br6mGHmLT0huXR2cWV9Jga Q6UrwYd/97pSveiajJCnsXj/MkJFb2EjMiS/RO5+JSrv2ZED8Cz3lDLNDSt9CgpAAv6cxJOgx +YJIt6ZZyJHODZlgKWhHlZEdzGrsMnJoFb5Wss8galKp2vaSqKEqrr6yqBPAqMnoQHxWPQ7V+ imD2aS8g/qybvwjS07UociG94JO3nuwY3ChJXSEIAfosfb/s1eTgvFoXtQWsWOtCCAWNjVtlH 7QUfy+mL4z8t27t400z3W/QbMMDqDVVVyTkFdZFKuM2B2bq/PkRjsEoKqotADPp57wfavFP24 ykpTHIJhHx9umAGbP9lB6vOQQVTXCmYfYYZw9jtE4mgI3kngvqH5MNA7IbST8xkMdiZYPWQ2l NZmqYQ+/KHBqV1WdK4OmkyYVoFqEd0e9ra1UifHUW6htvwfdHFwecu3WAe6wMnMabof6sM47j 8lo7HITfZxtplD8Aass70kc+RSV1c7gpU1G4SvNQPqDN34JLrd97XRbPZo9dqjnFsx62HXSAD 4t4sMCVKcunBA/Z0CAOg0fzkNc/pzVcTp+EzvS1uUcKg4aEYcHVgAzktOzl/HDnaaiK0fW54o meKtf1HHBuHEv4B06JUMVlh6j7ppe8UmCxf/JzJm1Nfbr4XyvvkNdNwBALAeA/WZpoJqn5peO Zger8M2/ca5uYbsx+2PIC69cTugADssgOKope5SYnEEhu+xa0/iwURCCqB85qDCn1rD0z/r7b h2JIgPUAHcK4SxkgcfHYXuy0bY6Hmtg4qT3E2Kvje+lnS9hETmIJ73pkuQiR/oIIt7+Tf5EpP HGZX184ksdDdumuyDoelk5xjlQdJilrxeMhvyHUTz9TX2IaGSRAwzvVa0G0Y6vlA8R7ULIib0 K4EOzb0CrlfBuCzCpwSg== Archived-At: X-BeenThere: quic@ietf.org 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: Mon, 11 Jan 2021 21:13:18 -0000 Am 11.01.2021 um 21:56 schrieb Martin Duke: > I was disappointed to realize that quic-http has two normative > references (httpbis-cache and https-semantics) that are not even in WGLC= . We are trying to get to WGLC in the next few days. > This suggests that there will be significant delay (best case, months) > between QUIC and HTTP/3 finalizing as RFCs. In theory, once all of the specs are in the RFC Editor Queue, the IESG could ask the RPC nicely to fast-track the HTTP specs so that they do not delay the QUIC specs. > ... Best regards, Julian