Re: [quicwg/base-drafts] Consider a new stream type to act like MAX_PUSH_ID (#2418)

Jana Iyengar <notifications@github.com> Tue, 05 February 2019 11:47 UTC

Return-Path: <noreply@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 D6EF9130F4C for <quic-issues@ietfa.amsl.com>; Tue, 5 Feb 2019 03:47:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.553
X-Spam-Level:
X-Spam-Status: No, score=-12.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] 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 lQqo3mjXE348 for <quic-issues@ietfa.amsl.com>; Tue, 5 Feb 2019 03:47:26 -0800 (PST)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DEE2F130E46 for <quic-issues@ietf.org>; Tue, 5 Feb 2019 03:47:25 -0800 (PST)
Date: Tue, 05 Feb 2019 03:47:24 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1549367244; bh=rwA47cDXiK0OjaW6GeZgwN4k8KO/5Yk2vAGEZ5YPVD8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pEcQT3nOybRgvgt4oBSY5Pnp0FMscH42h02rcpE/QdCx1NTICYUyoqqOolSbwoqHW /LNNe9n45RXZgmLd0YeFGTkeAFz9w68zkMQILnkUqfD35ju7e+2HOUJx2BFGr0daJW UKeycEBVqjjBJDleJ3JEqax+mCNc7pU9eVPbSpsI=
From: Jana Iyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abcf2c32996f1e4aaf4ffb724e87aa41868f2489b792cf00000001187139cc92a169ce183df2cd@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2418/460609051@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2418@github.com>
References: <quicwg/base-drafts/issues/2418@github.com>
Subject: Re: [quicwg/base-drafts] Consider a new stream type to act like MAX_PUSH_ID (#2418)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c5977cc99af4_66573fe5be8d45bc1340d5"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/4X9jn7x7h7CY-gqkZq2fkmQfYnw>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 05 Feb 2019 11:47:28 -0000

This is a nice idea.

Encoding deltas avoids the server having to check if the new MAX_PUSH_ID is
smaller, but meh.

The only issue I see here is HoL blocking. It would be nicer to not
introduce dependencies and send these updates in DATAGRAM frames, but of
course, we don't have those.

On Tue, Feb 5, 2019 at 5:01 PM Lucas Pardue <notifications@github.com>
wrote:

> If the sequence is monotonic increasing, a series of deltas will make it
> more efficient. Slightly. I mean, the stream overhead here will dominate
> anyway.
>
> Neat idea. unsigned deltas may actually be a more natural mapping for what
> the client is trying to express in terms of managing concurrent pushes.
> However, this might add some work for the server to reconstruct the push
> ID. Not sending explicit values seems like an easy way to misunderstand the
> clients intent.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/quicwg/base-drafts/issues/2418#issuecomment-460604870>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AKjg1I6DUGrP6xli1nutis540wJZ4rTzks5vKWudgaJpZM4ai5xW>
> .
>


-- 
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/2418#issuecomment-460609051