IETF Logo Mail Archive

Re: [quicwg/base-drafts] RESET_STREAM.final_offset is ambiguous (#2262)

Marten Seemann <notifications@github.com> Thu, 03 January 2019 05:08 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 B500A1310E3 for <quic-issues@ietfa.amsl.com>; Wed, 2 Jan 2019 21:08:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.661
X-Spam-Level:
X-Spam-Status: No, score=-6.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.065, 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_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 PzydcWVAFfd0 for <quic-issues@ietfa.amsl.com>; Wed, 2 Jan 2019 21:08:20 -0800 (PST)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [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 804A71310D1 for <quic-issues@ietf.org>; Wed, 2 Jan 2019 21:08:20 -0800 (PST)
Date: Wed, 02 Jan 2019 21:08:19 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1546492099; bh=jdUQz19UFBVj3s/S2gJVt6PflzjmFwfusKDdzbnPJLs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=FR9Y06mnjeNH+gma54B59nQzMoYxiWD2+MBMfbPJ0xzbn2U+/JWEH0Kj9wlQNsHTU eR9tFFr/TuqqnkJbSp+5QNEbAvTOUdZzN/zDpVu4edcfIhVjX+jzfqhuaCEV8cp/OP UTfmLljsNQIFl4iqn+d88qeizGcGJfKX6NUVuwPM=
From: Marten Seemann <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abc3a6f5b3e5e6fc8f9abff4b82d0542e76f49675e92cf0000000118455ac392a169ce17801464@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2262/451056963@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2262@github.com>
References: <quicwg/base-drafts/issues/2262@github.com>
Subject: Re: [quicwg/base-drafts] RESET_STREAM.final_offset is ambiguous (#2262)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c2d98c3cc356_78fe3fab712d45b81432af"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: marten-seemann
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/CKzLMHsH-m76HOwFpxfQQ1Ho_rg>
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: Thu, 03 Jan 2019 05:08:23 -0000

Looks like this has nothing to do with retransmissions at all, but just with the definition of "offset". I still like it better than "size" though, because one could reasonably expect the size to change when data is retransmitted, or when sending data with gaps.
Maybe we can define the stream offset as the offset of the next byte that would be sent on the stream would have.

-- 
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/2262#issuecomment-451056963

v2.23.0 | Report a Bug | By Email