[quicwg/base-drafts] Do we really need a "final offset" in the Reset Stream frame? (#749)

Christian Huitema <notifications@github.com> Thu, 24 August 2017 02:00 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 2D9EF1321EA for <quic-issues@ietfa.amsl.com>; Wed, 23 Aug 2017 19:00:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.754
X-Spam-Level:
X-Spam-Status: No, score=-7.754 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.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 y07qPpyykdMM for <quic-issues@ietfa.amsl.com>; Wed, 23 Aug 2017 19:00:49 -0700 (PDT)
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext3.iad.github.net [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07D311321D9 for <quic-issues@ietf.org>; Wed, 23 Aug 2017 19:00:48 -0700 (PDT)
Date: Wed, 23 Aug 2017 19:00:48 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1503540048; bh=W5Ivi6qqeJuWDeEHuKs7+MrP1XCYLU29gBVD87WuGkw=; h=From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=rNKgiei10UBzBSxs8h1jYPDtUi9Ti/VdQUX7s1lGrUcxYUuI28vel8gHUJKoQ7xU9 S1wUIJBbmRwghTCg8nMqQyefuS0oDntFyMn21smQA+9CIS9wZNDBfoaZVT2huYEfXw FU/5CS4aas16KA2hUUblKbHMTh1Dw1Kow8zdtfBo=
From: Christian Huitema <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abe5e8bb9f586d822d3bb1b69098071c8fdd011e7592cf0000000115b5f55092a169ce0f0c50c6@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/749@github.com>
Subject: [quicwg/base-drafts] Do we really need a "final offset" in the Reset Stream frame? (#749)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_599e335027c47_52a53f8dbe049c386725e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: huitema
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/uuyoVvp-eltZ-lmsrXPC8dGyP34>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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, 24 Aug 2017 02:00:51 -0000

Or, what is the node that receives the Reset Stream supposed to do with the Final Offset?

The text says, "discard immediately". That rules out any idea of receiving the bytes up to the final offset before closing. So, what's the point, exactly?

-- 
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/749