Re: [quicwg/base-drafts] clarify what happens when consuming CIDs excessively (#2428)
erickinnear <notifications@github.com> Sat, 09 February 2019 00:48 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 8FAAD131066 for <quic-issues@ietfa.amsl.com>; Fri, 8 Feb 2019 16:48:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.597
X-Spam-Level:
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: 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 S7mrYVU7U6OK for <quic-issues@ietfa.amsl.com>; Fri, 8 Feb 2019 16:48:32 -0800 (PST)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAE75130F33 for <quic-issues@ietf.org>; 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; d=github.com; 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 <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abc141dd67e550f2faf4c39d1a44bf70947025b26d92cf000000011875e55e92a169ce184361c4@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2428/c461995108@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2428@github.com>
References: <quicwg/base-drafts/pull/2428@github.com>
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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/tCDRN8hPXay3clERJpcc72zAnFo>
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: 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: https://github.com/quicwg/base-drafts/pull/2428#issuecomment-461995108
- [quicwg/base-drafts] clarify what happens when co… Kazuho Oku
- Re: [quicwg/base-drafts] clarify what happens whe… Marten Seemann
- Re: [quicwg/base-drafts] clarify what happens whe… Kazuho Oku
- Re: [quicwg/base-drafts] clarify what happens whe… Martin Thomson
- Re: [quicwg/base-drafts] clarify what happens whe… Kazuho Oku
- Re: [quicwg/base-drafts] clarify what happens whe… Kazuho Oku
- Re: [quicwg/base-drafts] clarify what happens whe… Kazuho Oku
- Re: [quicwg/base-drafts] clarify what happens whe… Martin Thomson
- Re: [quicwg/base-drafts] clarify what happens whe… Martin Thomson
- Re: [quicwg/base-drafts] clarify what happens whe… MikkelFJ
- Re: [quicwg/base-drafts] clarify what happens whe… ianswett
- Re: [quicwg/base-drafts] clarify what happens whe… Martin Thomson
- Re: [quicwg/base-drafts] clarify what happens whe… MikkelFJ
- Re: [quicwg/base-drafts] clarify what happens whe… erickinnear
- Re: [quicwg/base-drafts] clarify what happens whe… MikkelFJ
- Re: [quicwg/base-drafts] clarify what happens whe… Martin Thomson
- Re: [quicwg/base-drafts] clarify what happens whe… Jana Iyengar
- Re: [quicwg/base-drafts] clarify what happens whe… Kazuho Oku
- Re: [quicwg/base-drafts] clarify what happens whe… Kazuho Oku
- Re: [quicwg/base-drafts] clarify what happens whe… Kazuho Oku
- Re: [quicwg/base-drafts] clarify what happens whe… Kazuho Oku
- Re: [quicwg/base-drafts] clarify what happens whe… Kazuho Oku
- Re: [quicwg/base-drafts] clarify what happens whe… Mike Bishop
- Re: [quicwg/base-drafts] clarify what happens whe… Martin Thomson
- Re: [quicwg/base-drafts] clarify what happens whe… Martin Thomson