[quicwg/base-drafts] Note that state probably needs to be maintained for each issued CID if the peer chooses to use it (#3557)

Eric Kinnear <notifications@github.com> Mon, 30 March 2020 17:46 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 []) by ietfa.amsl.com (Postfix) with ESMTP id D60AF3A093C for <quic-issues@ietfa.amsl.com>; Mon, 30 Mar 2020 10:46:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.473
X-Spam-Status: No, score=-0.473 tagged_above=-999 required=5 tests=[DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_28=0.726, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 90Ly9Hd5SXjb for <quic-issues@ietfa.amsl.com>; Mon, 30 Mar 2020 10:46:08 -0700 (PDT)
Received: from out-26.smtp.github.com (out-26.smtp.github.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 953583A0933 for <quic-issues@ietf.org>; Mon, 30 Mar 2020 10:46:08 -0700 (PDT)
Date: Mon, 30 Mar 2020 10:46:07 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1585590367; bh=+/wEoW2KujuBxC56YMsavSNMKOBXrj4t7uL+NEKvNxc=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=f/JngnPPJqE7xOwmOfyu0JW3i1leF14fD30v6KMO+StiJ/6CMxh7QKw8129TNWXAF ycwSRvQsM75BhfNXewmmp1wDqfyerzYn2t6bK2ktYi6yEXzKJnUOXnNmKaXO1nyKp0 TG/GjYSZX8F8OLw0Q2Pn5afnSciWqOu+DGZjrcOU=
From: Eric Kinnear <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKYVP3XO4DBAGNJHKM54RYIV7EVBNHHCGMPIX4@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3557@github.com>
Subject: [quicwg/base-drafts] Note that state probably needs to be maintained for each issued CID if the peer chooses to use it (#3557)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e82305fc923e_335c3fada30cd95c1176ec"; 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/UWLx3cXKDyhPLJ7dwbS-fh-2dBk>
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: Mon, 30 Mar 2020 17:46:10 -0000

Add another note when cautioning endpoints about how many CIDs to issue: in this case to note that if you issue a CID you need to be willing for the other endpoint to use 100% of the issued CIDs, which comes with an implicit willingness to maintain state for each path on which that CID could be used. (That&#39;s one per path, but # paths == # CIDs in the worst case.)

Fixes #3489.
You can view, comment on, or merge this pull request online at:


-- Commit Summary --

  * #3489: Note that state probably needs to be maintained for each issued CID if the peer chooses to use it

-- File Changes --

    M draft-ietf-quic-transport.md (11)

-- Patch Links --


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