Re: [quicwg/base-drafts] Explain reason for having connection limits (#796)
MikkelFJ <notifications@github.com> Wed, 27 September 2017 06:17 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 31F1B132397 for <quic-issues@ietfa.amsl.com>; Tue, 26 Sep 2017 23:17:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7
X-Spam-Level:
X-Spam-Status: No, score=-7 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, 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 yflA15frGaZI for <quic-issues@ietfa.amsl.com>; Tue, 26 Sep 2017 23:17:50 -0700 (PDT)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext4.iad.github.net [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 A260D132076 for <quic-issues@ietf.org>; Tue, 26 Sep 2017 23:17:50 -0700 (PDT)
Date: Tue, 26 Sep 2017 23:17:49 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1506493069; bh=+QDVWzf0x28vjJfmof2+fdEzuLmGSwS4hOMHRvXKWig=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=teLz1L4EBwIiDmy1v92kVEV+tF0wSQQFcMjlQRTw9JAfw6Gu6U5+DFsl8B+VwQzNc 1CU8kNMwsQe4Ynk0DVLQBJEmAUPU6SAPhauruMZ3mcF/2KQcDtJnWtV/YtvEtoXRS7 O5B1uhnUb7t9N91rPom2ru0FpjOSb2WSWMaiO5T4=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab9d75b27767e99016b0733fb5af1d4b9bf4537c3a92cf0000000115e3048d92a169ce0f868d69@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/796/332420319@github.com>
In-Reply-To: <quicwg/base-drafts/issues/796@github.com>
References: <quicwg/base-drafts/issues/796@github.com>
Subject: Re: [quicwg/base-drafts] Explain reason for having connection limits (#796)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59cb428db1389_4b213f857bd30f78585d8"; 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/nBsG8enbLdAQgC4hQ3qdJA_GMHY>
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: Wed, 27 Sep 2017 06:17:52 -0000
It would also be possible to wrap 128-bit bumbers, which are practically unbounded, similar to how packet numbers are truncated on wire. So it must be an implementation complexity tradeoff or a technical difficulty in resolving representational conflicts, or a yagni. ________________________________ From: Martin Thomson <notifications@github.com> Sent: Wednesday, September 27, 2017 2:45:44 AM To: quicwg/base-drafts Cc: Subscribed Subject: Re: [quicwg/base-drafts] Explain reason for having connection limits (#796) The answer was: because those various numbers have maximums. That is in the draft. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<https://github.com/quicwg/base-drafts/issues/796#issuecomment-332376003>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AALzN2cu8Mpg3lsyKXemX3Wks9ZD2F85ks5smZq4gaJpZM4PjnCs>. -- 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/796#issuecomment-332420319
- [quicwg/base-drafts] Explain reason for having co… Dmitri Tikhonov
- Re: [quicwg/base-drafts] Explain reason for havin… Martin Thomson
- Re: [quicwg/base-drafts] Explain reason for havin… Dmitri Tikhonov
- Re: [quicwg/base-drafts] Explain reason for havin… Martin Thomson
- Re: [quicwg/base-drafts] Explain reason for havin… MikkelFJ
- Re: [quicwg/base-drafts] Explain reason for havin… Dmitri Tikhonov
- Re: [quicwg/base-drafts] Explain reason for havin… Dmitri Tikhonov
- Re: [quicwg/base-drafts] Explain reason for havin… Ryan Hamilton
- Re: [quicwg/base-drafts] Explain reason for havin… Mark Nottingham
- Re: [quicwg/base-drafts] Explain reason for havin… Dmitri Tikhonov
- Re: [quicwg/base-drafts] Explain reason for havin… Dmitri Tikhonov
- Re: [quicwg/base-drafts] Explain reason for havin… Dmitri Tikhonov