[quicwg/base-drafts] ambiguity on reaction to RST_STREAM (#1671)
mirjak <notifications@github.com> Thu, 16 August 2018 16:38 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 004EF1252B7 for <quic-issues@ietfa.amsl.com>; Thu, 16 Aug 2018 09:38:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
X-Spam-Status: No, score=-8.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_HI=-5, 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 JkQOlIdlgfel for <quic-issues@ietfa.amsl.com>; Thu, 16 Aug 2018 09:38:54 -0700 (PDT)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24DDA1277BB for <quic-issues@ietf.org>; Thu, 16 Aug 2018 09:38:54 -0700 (PDT)
Date: Thu, 16 Aug 2018 09:38:53 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1534437533; bh=sy+y6v/tRqNH1zr5dPAVDxP0am9zCSf2Us0e+Cbru78=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=zsoiNMFx3mqYGplT2ipG98IQaFPi4Bv/TZslgOh8PAbft1BgJw1hkAbzrU821QKjT yu0mAKtJTo+3Sszg+IHxuywVTR7qNFQHbqrOINMttTA9HN10wvxiX9A5D8/6Tkp1FW zipRDMDZ0LfxqQ7Wf2wY4EjAuzihyNSOaXKlv8Tk=
From: mirjak <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abbba0e109c7e54582690f7d08a18b9b37b93a4f9492cf00000001178d6a9d92a169ce14f025d9@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1671@github.com>
Subject: [quicwg/base-drafts] ambiguity on reaction to RST_STREAM (#1671)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b75a89d4acfc_5cac3feb9f6be624114423e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mirjak
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/CuBLgb-kZA5q6NPgv2o6LJyP5FA>
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: Thu, 16 Aug 2018 16:38:56 -0000
The transport draft leaves it currently open to the receiver to delivery outstanding and newly received data to the application after RST_STREAM was received. This introduces some ambiguity for flow control (see section "Edge Caeses and Other Considerations"). Further it may incentive wrong use of RST_STREAM and provide unepxected behavior between different quic implementation ("I always used RST here and data was correctly delivered...").
I would recommend to clearly specify that all data must be immediately dropped if RST_STREAM is received because that should only be send in an error case where that data is not useful anymore anyway.
(Effectly you don't even need the final offset in the RST_STREAM frame in that case anymore, but I guess that doesn't hurt.)
--
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/1671
- [quicwg/base-drafts] ambiguity on reaction to RST… mirjak
- Re: [quicwg/base-drafts] ambiguity on reaction to… MikkelFJ
- Re: [quicwg/base-drafts] ambiguity on reaction to… mirjak
- Re: [quicwg/base-drafts] ambiguity on reaction to… MikkelFJ
- Re: [quicwg/base-drafts] ambiguity on reaction to… mirjak
- Re: [quicwg/base-drafts] ambiguity on reaction to… MikkelFJ
- Re: [quicwg/base-drafts] ambiguity on reaction to… Mike Bishop
- Re: [quicwg/base-drafts] ambiguity on reaction to… Martin Thomson
- Re: [quicwg/base-drafts] ambiguity on reaction to… Martin Thomson