[quicwg/base-drafts] clarify what happens when consuming CIDs excessively (#2428)
Kazuho Oku <notifications@github.com> Wed, 06 February 2019 03: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 9530C128D09 for <quic-issues@ietfa.amsl.com>; Tue, 5 Feb 2019 19:38:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.553
X-Spam-Level:
X-Spam-Status: No, score=-12.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 Xmg_O5aM-Wzr for <quic-issues@ietfa.amsl.com>; Tue, 5 Feb 2019 19:38:48 -0800 (PST)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [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 CB14A1288BD for <quic-issues@ietf.org>; Tue, 5 Feb 2019 19:38:47 -0800 (PST)
Date: Tue, 05 Feb 2019 19:38:46 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1549424326; bh=ahvtTjdTbwlaaqPqAnJJYiMN8spu2gAYeT4EGCxiFEY=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=Kx/6IGsTT1PuWVNVDVnRFdJyHqecI38edr21aq7Pv4xPL3tlTKZreec1C5FjcMQTI 02JNkTnmj3m9VAEMRfBUelDC3VFfb2wL5ETBwKKUSz3ESOrA+wx52y+WHR4Upi8Zla Dd1UCohNU6HpuUNeXULtVAVUjgFoe2oDoNi7M34U=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abccf89ab27bd69150a56f63b6e1a4333b9675659592cf00000001187218c692a169ce184361c4@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@github.com>
Subject: [quicwg/base-drafts] clarify what happens when consuming CIDs excessively (#2428)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c5a56c6ceeac_42723fa02d4d45c488983"; 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/0GbeBwCbSnL3oLDCI2SuUGCSkhE>
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: Wed, 06 Feb 2019 03:38:50 -0000
While we allow the consumer to start using new CIDs anytime, there are consequences of consuming them excessively, as discussed in #2403 starting from [this comment]( https://github.com/quicwg/base-drafts/issues/2403#issuecomment-460255684) The text clarifies that excessive consumption is not what the issuer needs to support. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/2428 -- Commit Summary -- * clarify what happens when consuming CIDs excessively -- File Changes -- M draft-ietf-quic-transport.md (7) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/2428.patch https://github.com/quicwg/base-drafts/pull/2428.diff -- 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
- [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