IETF Logo Mail Archive

Re: HTTP Delays

Julian Reschke <julian.reschke@gmx.de> Thu, 14 January 2021 14:46 UTC

Return-Path: <julian.reschke@gmx.de>
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 49BAF3A12C2 for <quic@ietfa.amsl.com>; Thu, 14 Jan 2021 06:46:05 -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_H3=-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 It1itSdYGFgb for <quic@ietfa.amsl.com>; Thu, 14 Jan 2021 06:46:03 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (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 2067C3A12D4 for <quic@ietf.org>; Thu, 14 Jan 2021 06:46:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1610635559; bh=eDj1NJ5DsP3/fHunRzLKHgZxnL9vW2YazxWlBK4qcpk=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=RihnmmiOh8TXecMilO3PdV1GxSk/ek6qbNvT12wcPrBIWNSbGwX1eoMbmIPja5SjP vWc3mgPMlbJCZLAgV/+Eb+rawt8ACtl1BbbOhLSAZ5RbsFi6RC0//sOtUOyev0+mhQ xjUph93AJP6Nah471R0iOAAxGPZ9N2r7bbbok0Rs=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.1.236] ([217.91.35.233]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1N3siA-1lzlH51Mu0-00znM7; Thu, 14 Jan 2021 15:45:59 +0100
Subject: Re: HTTP Delays
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, "quic@ietf.org" <quic@ietf.org>
References: <CAM4esxSObWwLfzRWazAg+Q+9=BHGzXaSSduONozHF_zGCqC-kg@mail.gmail.com> <CA+9kkMA++3QYnXiVwuKSPZDYycERRrC11b-jHTG6JcyjngDhqA@mail.gmail.com> <CAM4esxQ9w0h2-rZ1ynhEMKAxwq0gfSVJtfGXV8ydGdUTEefMuA@mail.gmail.com> <029bd6e66fb81e2ecf16e35adf30b90c816c9962.camel@ericsson.com> <CAM4esxQeFaYytwyeB+m_yDrn8SSR8Yy4BHTsvxngTjG3=y0Zag@mail.gmail.com> <4459A34C-ED70-4354-9653-BA5165EC887A@gbiv.com> <CA+9kkMAqj2B8VprF_j=jLJ2CKbWvR6oO+ciHaTCSF1Sd3f_KtQ@mail.gmail.com> <f64ca7ca-0f54-3a8d-b5aa-428835bef6bb@gmx.de> <7b3fe48634ddd2c93172656c44cf64ec0e3cdd3f.camel@ericsson.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <0e93da91-1d4f-bbd1-4be3-cd3ce16433bc@gmx.de>
Date: Thu, 14 Jan 2021 15:45:58 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <7b3fe48634ddd2c93172656c44cf64ec0e3cdd3f.camel@ericsson.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:jgBqhvjEfMtFMX28BsC9lBQ33Wwh2gCyN/NAOixC2R/l7gwXA4i OTwsj3Bu1QzhfiZ4J4z0P6mJlYgD5RGpfhZSzqKRqyN8bw3gZIr7oe8l2e4ENHxAveNWFWx TfUTkjieogo9wnBIUBjbj9DsnR9nNV4HmQXcHeWwYyPuIDuVfKGBW8a9m+hvt8/Aj6M8toH 6aVymPLvcJVZnEtrkLOSQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:yafOUEY4RVA=:K2KSuyoUqviGQHF94tF5Vb tgOEyAf6IaNqF1NFH4O3yv9UtYITIj1OwAYWLgmepa7d3JB/v/h5extA73mzn8cO4J7OhgilX W9GebmHAJ2V3QLY5z6UopQhbzXu1cex4Ct+R38S1KJrCjYUMLG8nnwKlGYvC0JFn/LVBtCu6u UZJ94ux6BnOve97HlwH2jFOhezJFNIccRJfqdCHdD+R6uLJDhqOYFoaK0De/5HJc8aA6o2exC 8975G8ruJnHgSPweH58KTLHqtUhIfMDcTjn1I/mbzPoG+1I4i8uyq567dqFL0bKcOrSRnkHYX lP8jvUlW/AQScA79c0q5GrU6MsDuOTpGLS5PYTkkJXo6LU+hzblLVPZRAjuokHqc2tcEMZJRy TZABujwdjmK5OtnMlzUn7VM84CtDzBF4//RHPIhrELfUUICIe86bCtPpm/GP6TgGsvq7ngWyU 9UuJbdDw3beUOensXbrp91+hvqikXGoPmUVRly9OXwA0dh1ylVn1/UbACLJn1LNRcsbexpJ3C Dzk0d7O2QSt/2r4xdYYQChmw9OD+/ltPlTIGR35XxAtuQbnHCG4HiNC7hLiBf6WrBEGLeNnBv 7ErT6y3zLdyTuvuRommuKS+xlvmRUNvUJnKkaPue/6O5l4GQb9iSno0NcFoCvMyRYrinLadtR z74jXvV3YHBMnk9nqGs//sd+wWa2ehN84XjxMgQunLV6f7ijivp4IJK4nFdTdBxjLfcgXS9xq Ikh5K5bq9RVQNdXfkquFK1sPX0l0oXopfRZwPbA8GW5UjNYrL+/DR2pe/OV144KAQJqS/tmHl eOYvwYLzNZSSNWmiTDPuJTx6M5ahY4kdQL05+iGL/T+9PJeZh5UOYRv3MvEXUP6MAe7BzooiS V+atbNbYhzh/aLOmqNVw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/g3gSiJ5qohQhsXUc4fCfEBgk1CM>
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: Thu, 14 Jan 2021 14:46:05 -0000

Am 14.01.2021 um 14:53 schrieb Magnus Westerlund:
> Hi,
>
> On Wed, 2021-01-13 at 20:06 +0100, Julian Reschke wrote:
>> Am 13.01.2021 um 19:55 schrieb Ted Hardie:
>>> ...
>>> While they could theoretically pre-assign it, the RFC Editor won't
>>> publish the document without the documents actually being available for
>>> retrieval.  That's a big reason you get clusters.  This is why we do
>>> downrefs to the drafts; since there is an onward pointer from the
>>> referenced draft to the final RFC in the tools, that's considered okay
>>> as anyone who seriously wants the reference can readily find it.  [Note:
>>> my opinion on that is separate from my recitation of what I think the
>>> facts are.]
>>> ...
>>
>> Maybe we need a separate discussion about easily (or even
>> semi-automatically) updating published RFCs when their downrefs become RFCs.
>
> Which isn't done at all. The main body of the RFC when published is inmutable.
> Thus, if you want to align any language changes or anything with the new HTTP
> specs when going for do a "downref" means a new RFC.
> ...

I understand that this is the current state of things - but it might
makes sense to discuss in the context of other conversations we'll
hopefully have about RFC "immutability".

(and yes, that doesn't help with the current problem)

Best regards, Julian

v2.23.0 | Report a Bug | By Email