Re: [quicwg/base-drafts] Explain reason for having connection limits (#796)

Dmitri Tikhonov <notifications@github.com> Wed, 27 September 2017 10:02 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 9DDE113495D for <quic-issues@ietfa.amsl.com>; Wed, 27 Sep 2017 03:02:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.402
X-Spam-Level:
X-Spam-Status: No, score=-5.402 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_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 4UwZ7YtFXPqa for <quic-issues@ietfa.amsl.com>; Wed, 27 Sep 2017 03:02:36 -0700 (PDT)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext8.iad.github.net [192.30.252.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4AD0B134959 for <quic-issues@ietf.org>; Wed, 27 Sep 2017 03:02:32 -0700 (PDT)
Date: Wed, 27 Sep 2017 03:02:31 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1506506551; bh=Jd2dAhp2T8wqi61tdiykNlwABBk7P7XJ1V3uT6kb3uU=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=oPfd1iR5lvZwx5pwIeT75TntWmAQ2Gdy9ZBkabyWq4Z8LHrCbFasDXs4hYzYWxTzE kXh3BgEhOZFlF5abnIXeb/1G3gcRv0Z2cVlhM5ZcKVhySkryjfUrqLKM5U9ay29hy0 01eTYCSkwLGQrKjPXGg3pEuJL/qgfrO4NKCn2WNI=
From: Dmitri Tikhonov <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abbdcee2cedf9ded90e13375a356792ffc4fcd5a3b92cf0000000115e3393792a169ce0f868d69@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/332473219@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_59cb77379b24e_5ba43fe6a8ab6f8419965"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: dtikhonov
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/qGaQEFXbQESwnJ84hm7mKXVZTc4>
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 10:02:38 -0000

@mikkelfj, I agree with your analysis.  (For my money, a 64-bit number is practically unbounded as well.)  What I am proposing is that this verbiage or something to that effect -- _practical considerations... blah-blah-blah_ -- be put into the draft.

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