IETF Logo Mail Archive

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

Martin Thomson <notifications@github.com> Tue, 11 December 2018 01:04 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 4BBE5130EC5 for <quic-issues@ietfa.amsl.com>; Mon, 10 Dec 2018 17:04:17 -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 maAutARNKyF2 for <quic-issues@ietfa.amsl.com>; Mon, 10 Dec 2018 17:04:15 -0800 (PST)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 861B712DD85 for <quic-issues@ietf.org>; Mon, 10 Dec 2018 17:04:15 -0800 (PST)
Date: Mon, 10 Dec 2018 17:04:14 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1544490254; bh=xEpkc6oymmOGWrHnctUH/D34ZQuxye70tK2c7s8jrE0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=fzvYnVIgSmGsXGXCn8bwHLEUxClpkV2o0axq/Ed3e1YALj6ejsnHcjQu0eZE/3T5j QOwl6t7EHdirXrm+uAuoydypSw6sNsA4HyyI2r8aAZdEs+siKaUEGH80GGbYVnlE3h P8fzcOeZFosXHCvLpLnzLo/uFTD95N4Th/IUc6bg=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abf9876dc26fc34c0a0b5a311e28d49f52b107117092cf000000011826cf0e92a169ce171ddb1f@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/446033780@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2101@github.com>
References: <quicwg/base-drafts/issues/2101@github.com>
Subject: Re: [quicwg/base-drafts] Should retiring all CIDs be an error? (#2101)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c0f0d0e7ade7_3e563fdaf3cd45c0493b5"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/lJE3ZGkLXmovgTzkGRxWdK77lSY>
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: Tue, 11 Dec 2018 01:04:17 -0000

You can send CONNECTION_CLOSE, even if you can't accept an ACK, because it's the not peer that has no connection IDs that sends that packet.  Or you can send more NEW_CONNECTION_ID frames.

The only potentially interesting case is that you can't send a packet with a long header, but that's not a problem in this protocol version.

I'm somewhat biased toward silence on this issue.  We encourage the replacement of connection IDs, which works here.  And if an endpoint just made it impossible to keep sending packets, that's a problem that solves itself really.

-- 
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#issuecomment-446033780

v2.23.0 | Report a Bug | By Email