Re: [quicwg/base-drafts] Possible HoL blocking due to co-mingling payload and metadata (header) address space. (#1606)

Mike Bishop <notifications@github.com> Fri, 27 July 2018 18:41 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A257E130E45 for <quic-issues@ietfa.amsl.com>; Fri, 27 Jul 2018 11:41:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.01
X-Spam-Level:
X-Spam-Status: No, score=-3.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
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 rx-xyqGSvFtL for <quic-issues@ietfa.amsl.com>; Fri, 27 Jul 2018 11:41:38 -0700 (PDT)
Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (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 EA00F12F1AB for <quic-issues@ietf.org>; Fri, 27 Jul 2018 11:41:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=QnzTIfk60el/yo8hhOeTqToQtas=; b=upJxgREtyt78gc5H 85JfUY4e92yb2FIZkUTjYdUewy8p+2GnOAoNKcaQn5zoPtHaadlEV8/6d3C5f8Mq yi5kIGA1+YecDsPrXFzM/ehbo/qVtCV82fvUzHqB2DlwhXFnICdKBzqoBiMz4wyx 7WEkcpG4/cv9/7Ls3UKJlch0dxU=
Received: by filter0723p1las1.sendgrid.net with SMTP id filter0723p1las1-9412-5B5B6760-7 2018-07-27 18:41:36.239548955 +0000 UTC m=+160268.369511616
Received: from github-lowworker12-cp1-prd.iad.github.net (unknown [192.30.252.42]) by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id 0562jBALQ9OvgnqLrqNi_A for <quic-issues@ietf.org>; Fri, 27 Jul 2018 18:41:36.035 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker12-cp1-prd.iad.github.net (Postfix) with ESMTP id 06A4440E63 for <quic-issues@ietf.org>; Fri, 27 Jul 2018 11:41:36 -0700 (PDT)
Date: Fri, 27 Jul 2018 18:41:36 +0000 (UTC)
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab0f868436d17c5054eb5c7b00962b7bb8c516b71992cf000000011773296092a169ce148a3cb6@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1606/408505493@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1606@github.com>
References: <quicwg/base-drafts/issues/1606@github.com>
Subject: Re: [quicwg/base-drafts] Possible HoL blocking due to co-mingling payload and metadata (header) address space. (#1606)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b5b67605327_187e3fe3410be61879090"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0eOwjhJHxscZ6t4Tg1sFOHPBKHUEqKqHWox3 cAp5z0RhXdNiOFsCzL7C0yW9z+pUSo3MsDJDMrBtJIjfpIqo4xs7zOwh1LkL61t9sD9xc8MERf6IMU j8XGnlQ7bWNBRUDzVoUpwCp12Mle1lL3o59pi4Xy/Cg5Ry49LE/s0g+kU4OyW+Pgq9DOrmJMqaPUjX Y=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/YUM7o0uvgDgPqhk5fefAlDSrc4M>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jul 2018 18:41:40 -0000

The design from one of the unidirectional forks, where DATA frames described on which other stream to expect that chunk is actually no better for you, because you still need the rest of the header stream to get appropriate correlation information.  Basically, for any design which permits the body not to be a single contiguous unit on its own stream, you'll have this problem.

As @martinthomson says, the current design also addresses real issues, and I don't know that we want to rework our stream mapping again at this point.  We decided in Paris to go to a single stream because we wanted to be able to provide ordering amongst metadata and body chunks.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/1606#issuecomment-408505493