IETF Logo Mail Archive

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

krasic <notifications@github.com> Fri, 27 July 2018 17:49 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 BA9B8131006 for <quic-issues@ietfa.amsl.com>; Fri, 27 Jul 2018 10:49:46 -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 3VccY1d1-_ju for <quic-issues@ietfa.amsl.com>; Fri, 27 Jul 2018 10:49:44 -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 D838C130E0C for <quic-issues@ietf.org>; Fri, 27 Jul 2018 10:49:44 -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=RdDPufC1l0TLHxEfMSFDjqyrzPc=; b=eTpGy1+pM93ng5FV 4vtuYb2oOcoKaA6yjE7wHNf2ZyqYc/M8skxU7XXZdXncy7yqYJfr9m8NSsyOrNzm plsr9seCG/mBvoCsIpAYS7ZweC+bddxF5EZl/KRQmZKdGgFxU4aWUchdh7F2W4k+ ypFTYMb/hOvivooIEivWBSmx3TU=
Received: by filter0783p1las1.sendgrid.net with SMTP id filter0783p1las1-1011-5B5B5B38-11 2018-07-27 17:49:44.461921187 +0000 UTC m=+157149.018343408
Received: from github-lowworker-f6df7df.cp1-iad.github.net (unknown [192.30.252.41]) by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id 4sXRKuCiQyuytzmOEJ78JA for <quic-issues@ietf.org>; Fri, 27 Jul 2018 17:49:43.673 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-f6df7df.cp1-iad.github.net (Postfix) with ESMTP id A0BE13E182F for <quic-issues@ietf.org>; Fri, 27 Jul 2018 10:49:43 -0700 (PDT)
Date: Fri, 27 Jul 2018 17:49:44 +0000
From: krasic <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abbe9d95acd79aa41d2bfe87bad4d38bbd02688fee92cf0000000117731d3792a169ce148a3cb6@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/408491827@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_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-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3tlHV7upzkVRc7FfLrpo3kd2s6qtBQVW1uOL Sfj7Zdt8sjHNjgWpMQdEVFfexeWz+3ZPNk8xC5vTnM4UxtP8kqXBnWgA3hesOWwZGhlN0OgMcXg5y1 C10AwgIAGJrFRvbi/Cqv/Kn+QbQw1pTx+X5LLTvEzBwCP2JLzDqNs3TzHQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/TuJUWoTaPAqQm7PYW0Up0L8xVqg>
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 17:49:47 -0000

To the questions about HTTP applicability, an example might be recent work on low latency DASH with cmaf.    For example, https://www.slideshare.net/Akamaidev/the-road-to-ultra-low-latency, 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:
https://github.com/quicwg/base-drafts/issues/1606#issuecomment-408491827

v2.27.8 | Report a Bug | By Email | System Status