Re: [quicwg/base-drafts] Remap STOPPING to something other than zero (#1804)

Kazuho Oku <notifications@github.com> Sat, 29 September 2018 08:51 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 92382130DFB for <quic-issues@ietfa.amsl.com>; Sat, 29 Sep 2018 01:51:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.455
X-Spam-Level:
X-Spam-Status: No, score=-8.455 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, 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, URIBL_BLOCKED=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 mPZCsnDXurib for <quic-issues@ietfa.amsl.com>; Sat, 29 Sep 2018 01:51:55 -0700 (PDT)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3D44126BED for <quic-issues@ietf.org>; Sat, 29 Sep 2018 01:51:55 -0700 (PDT)
Date: Sat, 29 Sep 2018 01:51:54 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1538211114; bh=5qOpuAyNACBUlOhyBa0IzclXBvKYwOIVaS9Dw9cONME=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=sVykpKC6GmuvTtVSXzab28obSUeyvHzHQv1aFdM1iJW7AesHLiklLCMsXVfgBM8lZ w3c8zLduSZjaYC/ZT7Vrb5AzncPlujKLkMHz5zhFtr3y46yhfQp+BfJJA+CxYiqmES V9FzIPyiBUCOVCgSZFNOVyZKc37PFZotFwTalhMw=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab50617377b1766c8c0006b8b9a60cae36c7c14d0c92cf0000000117c6ff2a92a169ce15b0cecf@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1804/425628690@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1804@github.com>
References: <quicwg/base-drafts/issues/1804@github.com>
Subject: Re: [quicwg/base-drafts] Remap STOPPING to something other than zero (#1804)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5baf3d2a66543_215f3f95d1ad45c0305310"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/ISX90speDiim-F4-kvk6PrDqisk>
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: Sat, 29 Sep 2018 08:51:58 -0000

@MikeBishop 
> If we required 0 to be NO_ERROR for all application protocols and specified that was the error code sent in response to a STOP_SENDING, would that address the concern?

No opposition from me. The existence of an RST_STREAM frame indicating NO_ERROR makes me a bit sad, because then we cannot use the 16-bit space to indicate both ordinary close (via FIN) _and_ a reset. But that is the same with the other approach (that requires all the QUIC stacks to ignore RST_STREAM after sending STOP_SENDING).

-- 
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/1804#issuecomment-425628690