IETF Logo Mail Archive

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

MikkelFJ <notifications@github.com> Fri, 04 January 2019 09:33 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 A2BD4130FCD for <quic-issues@ietfa.amsl.com>; Fri, 4 Jan 2019 01:33:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.065
X-Spam-Level:
X-Spam-Status: No, score=-8.065 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_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 OYQfREMXsdmL for <quic-issues@ietfa.amsl.com>; Fri, 4 Jan 2019 01:33:42 -0800 (PST)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39D5C130FCB for <quic-issues@ietf.org>; Fri, 4 Jan 2019 01:33:42 -0800 (PST)
Date: Fri, 04 Jan 2019 01:33:41 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1546594421; bh=APsaTSnEpimfoUR9mpWgxlCIFqObAfWvtt4QeN9Ug9w=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gaWOQa+PQvEW9HtRWc4RurBrvHGzc6b5lxnhbzFOzTzZEVc9IpGjRRhJeq/mwjXca xjbIbOONpnrk0nlalB6S4ta6nmTIv7YLAV8mXCG+VPI7SHBtxLI2Tmnlz7cJqS609l xgk8ZiDcamgQC/e5/m0U6yG7vlC/i0fY4oa5IqQA=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abbe345d5c944fca7d449fe88f76cec9ae99359ea492cf000000011846ea7592a169ce17801464@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/451395508@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_5c2f2875e717_15313feda48d45c411756f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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/V1ytmqDRnFpyQlPn2bsEDQqIB7c>
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: Fri, 04 Jan 2019 09:33:44 -0000

Regarding size vs offset, consider the hypothetical stream construct where you send every second 256 byte block. If you don't get a STOP_SENDING you continue with the gaps in order after sending the first 128 blocks. This is interleaved image transmission. Now, is the size the number of blocks sendt sent so far, or the end offset.

As @kazuho says, MAX_STREAM_DATA could be adapted either way, while MAX_DATA is more tricky.

But size is not unambiguous either unless you define it cover all unsent gaps as well.

As for interleaving, a better approach is to sent all even lines first, without gaps, then all uneven lines, which avoids the problem.

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

v2.23.0 | Report a Bug | By Email