IETF Logo Mail Archive

[quicwg/base-drafts] What the maximum of TransportParameters.max_ack_delay? (#2282)

Kazuho Oku <notifications@github.com> Tue, 01 January 2019 21: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 7D2EE12D4EB for <quic-issues@ietfa.amsl.com>; Tue, 1 Jan 2019 13:38:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.447
X-Spam-Level:
X-Spam-Status: No, score=-6.447 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_24=1.618, 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 sR-uAIp_C7k0 for <quic-issues@ietfa.amsl.com>; Tue, 1 Jan 2019 13:38:53 -0800 (PST)
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 F0399129BBF for <quic-issues@ietf.org>; Tue, 1 Jan 2019 13:38:52 -0800 (PST)
Date: Tue, 01 Jan 2019 13:38:51 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1546378731; bh=nb79ZkklmxYEtwHcwORNOwCm/Bmqm0tUhe9oE5/3CaI=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=jZhYisybtfcyjrR5WY0qp3VZ8YBFn7K+cSr9MsmKhLMtPzJdPdXSrzvbx1T6gMoZr e4Y6EMjccUtAC+FPKlPUL5haTGAPW0+tsuFCuzSqFxzRHkxRBxm2YxKld9B4ApsAMa JHuL69lj2a3ZVxp0fDJzL3WC/KEXWLlOxf1Mfki8=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab079b89bbe16ad68dc1b5d37dc5068afde85de47092cf0000000118439feb92a169ce178cf63b@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2282@github.com>
Subject: [quicwg/base-drafts] What the maximum of TransportParameters.max_ack_delay? (#2282)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c2bddebc7487_311d3fe5ddcd45bc399180"; 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/az0Q7qiaQaV2cNNHzChsTRZfmE0>
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: Tue, 01 Jan 2019 21:38:55 -0000

Previously, the maximum was 255 milliseconds, because it was a 8-bit value. But now that the type is varint, the value can express up to 2<sup>62</sup> - 1 milliseconds.

Should we define a reasonable maximum for the value, like what we have for ack_delay_exponent? Capping it so somewhere well below 32-bit range makes sense to me.

I ask this in fear that QUIC stacks might ship with code that fails to handle unreasonably large values.

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

v2.23.0 | Report a Bug | By Email