IETF Logo Mail Archive

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

Lucas Pardue <notifications@github.com> Tue, 05 February 2019 21:48 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 2D5691312F3 for <quic-issues@ietfa.amsl.com>; Tue, 5 Feb 2019 13:48:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.149
X-Spam-Level:
X-Spam-Status: No, score=-6.149 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_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 lX0UcmzOInLb for <quic-issues@ietfa.amsl.com>; Tue, 5 Feb 2019 13:48:05 -0800 (PST)
Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (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 523081312D1 for <quic-issues@ietf.org>; Tue, 5 Feb 2019 13:48:05 -0800 (PST)
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=0hVSZ4+UQaGA8pXUDSa/GzuEUa4=; b=RVA4F5NKdlJrrdkW jv1aNKG22PRGj96ttIbSzDGr3aYLPaSVWomwemRaL+mrHqJdZBQQJlyugz4I/iww oErdfo7Z16CzMT3i5gGfpmNwTXiB1AI7ZNbJ/bY1vmH+nsIWbdgj0ILWJK3BCQCx 9fMQMI5juCvIZ/LFCComSyrOODk=
Received: by filter1413p1mdw1.sendgrid.net with SMTP id filter1413p1mdw1-2215-5C5A0494-14 2019-02-05 21:48:04.263768086 +0000 UTC m=+3446.253427551
Received: from github-lowworker-89d05ac.cp1-iad.github.net (unknown [192.30.252.35]) by ismtpd0046p1iad1.sendgrid.net (SG) with ESMTP id Xeb0thOOQBGx5Le9ScBrQA for <quic-issues@ietf.org>; Tue, 05 Feb 2019 21:48:04.257 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-89d05ac.cp1-iad.github.net (Postfix) with ESMTP id 3BC26AE0438 for <quic-issues@ietf.org>; Tue, 5 Feb 2019 13:48:04 -0800 (PST)
Date: Tue, 05 Feb 2019 21:48:04 +0000
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab65fcf4b09dd2b85eac67df6f6aec5849140b0b7392cf000000011871c69492a169ce183df2cd@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/460816890@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_5c5a04943a391_3f9b3fe12ead45b81341d7"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3mpIK1/mFcUWeR/KEM9SHw4YD5kHtc4NxtGK XeF1uH5vGdSHb61u/kOYh669IXwuCscphCFshbFI58H8iYV7sKJoiogi/3LToyKNa9cF3xfOi3G89C flbkrDCv0PuT+7VHXeDYYsAUwkTA6eEiGVyuXnCo8Xc1FcV6pIp7g28+B8kJGbqs4p+2Q8ftbW7B8y w=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/XBWoJvyH8lBY0mF2FWEvaoDiCNs>
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 21:48:07 -0000

This is a valiant explanation, thanks Mike.

I don't see how unreliable DATAGRAM fixes the problem with handling MAX_PUSH_ID. I think it risks making the problem worse with the current rules. 

Consider a client that sends a ID 5, then ID 3 erroneously. If these are in separate DATAGRAMS, the error may go unnoticed if the first frame was lost. Furthermore, loss could effectively starve the server of Push ID credits, with neither endpoint being the wiser as to what happened.

-- 
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-460816890

v2.23.0 | Report a Bug | By Email