Re: [quicwg/base-drafts] clarify what happens when consuming CIDs excessively (#2428)

erickinnear <> Sat, 09 February 2019 00:48 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8FAAD131066 for <>; Fri, 8 Feb 2019 16:48:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.597
X-Spam-Status: No, score=-6.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, 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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id S7mrYVU7U6OK for <>; Fri, 8 Feb 2019 16:48:32 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id BAE75130F33 for <>; Fri, 8 Feb 2019 16:48:31 -0800 (PST)
Date: Fri, 08 Feb 2019 16:48:30 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1549673310; bh=z7LKUFGQkAkJP73zMtsYqxJsC5GLT3YqcwsYW2ctKnA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=y0C/KzmoUqqOKcj78fU9kCM3kPCP9t5M27iDQncQnWGS3De0BTGWiW1ObjGAFIDu0 YeXP3aTZIThoCQnf892aL1JALIYFfL+yHoyMKHdafLx4bRHMW8SRtwZpdGGsLUlrJy qX3aoZcw+ngZA+v1ZzJLbjrIQ5GmUgDRpWUsRP5w=
From: erickinnear <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2428/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] clarify what happens when consuming CIDs excessively (#2428)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c5e235e7fb83_586d3f87552d45bc109694"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: erickinnear
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 09 Feb 2019 00:48:34 -0000

@mikkelfj I think we should have a separate discussion around a sensible default. Part of the idea here was to make sure that we were very unlikely to run out, even around lost/retransmitted packets on different paths. Choosing a very low number brings with it other potential issues which probably should hold up this change? 

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: