IETF Logo Mail Archive

[quicwg/base-drafts] Should retiring all CIDs be an error? (#2101)

Dmitri Tikhonov <notifications@github.com> Wed, 05 December 2018 16:15 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 E6510130E4C for <quic-issues@ietfa.amsl.com>; Wed, 5 Dec 2018 08:15:23 -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 tULxrB2XGrDV for <quic-issues@ietfa.amsl.com>; Wed, 5 Dec 2018 08:15:22 -0800 (PST)
Received: from out-14.smtp.github.com (out-14.smtp.github.com [192.30.254.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2DFC130E4B for <quic-issues@ietf.org>; Wed, 5 Dec 2018 08:15:22 -0800 (PST)
Date: Wed, 05 Dec 2018 08:15:21 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1544026522; bh=lCFxLQelh1lrcMfi0GDqXA8SqSNeyPXqG8ydKfOETfo=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=TtsHsH+W4HE9BcrRg6aOFjOYbYGWsIDacXo+MUOubI5mK9pXMljlF52ns7727fZ09 bJz/8MAIHuvC8zbCwCSSTiBOWrhd/H8DBNunCcmfw2y36vFsKtjH9DM86XNNgsiQR7 9mkdQUi15R8pib5iwxpgFd5sLJNxLg8GhDSF77TI=
From: Dmitri Tikhonov <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab3709443fc631ebadfa69cfd0dd7a0504b5c66ee892cf00000001181fbb9992a169ce171ddb1f@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2101@github.com>
Subject: [quicwg/base-drafts] Should retiring all CIDs be an error? (#2101)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c07f999d4cdc_5df3f86b26d45c0277589"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: dtikhonov
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/3XppwieZDVDryl1cadVRXs7NCY8>
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, 05 Dec 2018 16:15:24 -0000

Retiring all CIDs that have been issued makes the CID issuer unreachable. Should this be a connection error?

It is possible to imagine that the CID issuer may send a new CID to the peer after all its CIDs are retired and then the connection can continue.

Either way, this case should be covered in the draft.

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

v2.23.0 | Report a Bug | By Email