IETF Logo Mail Archive

[quicwg/base-drafts] Retiring connection IDs (#2085)

ekr <notifications@github.com> Sat, 01 December 2018 02:14 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 CAE4712D84C for <quic-issues@ietfa.amsl.com>; Fri, 30 Nov 2018 18:14:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.46
X-Spam-Level:
X-Spam-Status: No, score=-9.46 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, 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 d7hDa2LWSkFJ for <quic-issues@ietfa.amsl.com>; Fri, 30 Nov 2018 18:14:45 -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 2D2D512D4EF for <quic-issues@ietf.org>; Fri, 30 Nov 2018 18:14:45 -0800 (PST)
Date: Fri, 30 Nov 2018 18:14:44 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1543630484; bh=K2n4Vy+uOiHQqg+ggoBzwZbd/+ifum+FTEF+huOx9G0=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=olNcjFqmWkUKNEDPkgvQBAbGFQhasBa5abwEH4Ut6Og+8U35HfK5DIJSuhitfsqh1 WiP1VyAjVArin3kKevqHkkHapPJphrPCK0auOqclKegUt4CIXfEqYv3NeWGMPBNAzC 6h3lr+TYbvvAZZb5jO1iNZw6RAeQ7j7YmpA60yz4=
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab11911ae418b825eaf8928acce767d08e40eb679d92cf000000011819b09492a169ce17082c2a@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2085@github.com>
Subject: [quicwg/base-drafts] Retiring connection IDs (#2085)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c01ee94608ff_27023fbd68ed45bc39047b"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
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/sj0gswr8Aumj0iGfniU6Ys5_Q_M>
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, 01 Dec 2018 02:14:47 -0000

```An endpoint maintains a set of connection IDs received from its peer, any of
which it can use when sending packets.  When the endpoint wishes to remove a
connection ID from use, it sends a RETIRE_CONNECTION_ID frame to its peer,
indicating that the peer might bring a new connection ID into circulation using
the NEW_CONNECTION_ID frame.
```

This text is very weak. Don't we expect peers to bring new connection IDs into circulation when they receive RETIRE_CID? Shouldn't we say so.





-- 
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/2085

v2.23.0 | Report a Bug | By Email