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

krasic <> Fri, 27 July 2018 17:49 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BA9B8131006 for <>; Fri, 27 Jul 2018 10:49:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.01
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 3VccY1d1-_ju for <>; Fri, 27 Jul 2018 10:49:44 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D838C130E0C for <>; Fri, 27 Jul 2018 10:49:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed;; 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=RdDPufC1l0TLHxEfMSFDjqyrzPc=; b=eTpGy1+pM93ng5FV 4vtuYb2oOcoKaA6yjE7wHNf2ZyqYc/M8skxU7XXZdXncy7yqYJfr9m8NSsyOrNzm plsr9seCG/mBvoCsIpAYS7ZweC+bddxF5EZl/KRQmZKdGgFxU4aWUchdh7F2W4k+ ypFTYMb/hOvivooIEivWBSmx3TU=
Received: by with SMTP id filter0783p1las1-1011-5B5B5B38-11 2018-07-27 17:49:44.461921187 +0000 UTC m=+157149.018343408
Received: from (unknown []) by (SG) with ESMTP id 4sXRKuCiQyuytzmOEJ78JA for <>; Fri, 27 Jul 2018 17:49:43.673 +0000 (UTC)
Received: from (localhost []) by (Postfix) with ESMTP id A0BE13E182F for <>; Fri, 27 Jul 2018 10:49:43 -0700 (PDT)
Date: Fri, 27 Jul 2018 17:49:44 +0000
From: krasic <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/1606/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
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_5b5b5b379e336_1a053ff1f9ad45b4338894"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: krasic
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3tlHV7upzkVRc7FfLrpo3kd2s6qtBQVW1uOL Sfj7Zdt8sjHNjgWpMQdEVFfexeWz+3ZPNk8xC5vTnM4UxtP8kqXBnWgA3hesOWwZGhlN0OgMcXg5y1 C10AwgIAGJrFRvbi/Cqv/Kn+QbQw1pTx+X5LLTvEzBwCP2JLzDqNs3TzHQ==
Archived-At: <>
X-Mailman-Version: 2.1.27
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 27 Jul 2018 17:49:47 -0000

To the questions about HTTP applicability, an example might be recent work on low latency DASH with cmaf.    For example,, esp. slide 9.   Existing variations  use HTTP 1.1 chunked transfer, with http chunks aligned to the fmp4 fragments, improving latency over conventional live DASH.     As I understand this thread, the idea is to improve further, reducing encoder/transcoder/origin latency closer/to the minimum (i.e. one media frame).   

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: