Re: [quicwg/base-drafts] Why are we bothering to number CIDs? (#2159)

ekr <notifications@github.com> Thu, 13 December 2018 22:47 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 91DF6130EA2 for <quic-issues@ietfa.amsl.com>; Thu, 13 Dec 2018 14:47:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.46
X-Spam-Level:
X-Spam-Status: No, score=-4.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_NONE=-0.0001, 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 V9a3BQYhmyxR for <quic-issues@ietfa.amsl.com>; Thu, 13 Dec 2018 14:47:40 -0800 (PST)
Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F929130EA9 for <quic-issues@ietf.org>; Thu, 13 Dec 2018 14:47:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=gOO0moNikjGDJv2/dfIqluBDLo4=; b=Fw1+o5OLewkzbNiT b5JRg9Lb4V9TPGQI+Mlx+/2T0RLAVI2iJV6Zbh/X+vC3nSPnH1zACiivPCGH8dVi hKBNZrIWKOdf3OtgLgR/SK332uOyRnRxZRpExSUdV5OD1hMPFJt2D00jUvjmpSWS 8aklrK1aIN7koCW9gTJtmpqHyq0=
Received: by filter1292p1mdw1.sendgrid.net with SMTP id filter1292p1mdw1-12922-5C12E18B-17 2018-12-13 22:47:39.385457967 +0000 UTC m=+9235.251049731
Received: from github-lowworker-f6df7df.cp1-iad.github.net (unknown [192.30.252.41]) by ismtpd0036p1mdw1.sendgrid.net (SG) with ESMTP id qXG3NTOPTfSLgQpa8zw3GA for <quic-issues@ietf.org>; Thu, 13 Dec 2018 22:47:39.335 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-f6df7df.cp1-iad.github.net (Postfix) with ESMTP id 2D9623E031D for <quic-issues@ietf.org>; Thu, 13 Dec 2018 14:47:39 -0800 (PST)
Date: Thu, 13 Dec 2018 22:47:39 +0000
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab8d57b67168ab1efa470b67576c6931fde3a83bbc92cf00000001182aa38b92a169ce174c07b8@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2159/447149186@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2159@github.com>
References: <quicwg/base-drafts/issues/2159@github.com>
Subject: Re: [quicwg/base-drafts] Why are we bothering to number CIDs? (#2159)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c12e18b2b5cc_549d3fe0316d45c4972c1"; 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
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2BUABrYMcTt5KQij8bS9A3NUrGX6JLpD1iSL x4m8VGYYvOV94zJLPxlrhqgwzntCLwSg24ZfDsRR3fUg80DBv+JRbIo6Z2cukW7COX6f4J4qDteJ2T kKYdZN5kqQjX2wlPdFmHJksVdcfDBg/cDtIz/yn22Vraf18Is/3bLa9cQw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/SL8vwUvqz3Joo4NyuU53Guj15fI>
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: Thu, 13 Dec 2018 22:47:43 -0000

I'm not persuaded by this. There are two cases:

1. An erroneous duplicate NCID.
2. Duplicated packets in the network.

If the other side is broken, there's no guarantee of consistency between
the sides in any case. So, we're only talking about the second case. And I
don't think it's particularly difficult to pick a timeout here, because
we're talking about the race between RETIRE_CONNECTION_ID and the packets
duplicate in the network, so a timeout on the order of 2MSL is basically
fine.





On Thu, Dec 13, 2018 at 2:33 PM Mike Bishop <notifications@github.com>
wrote:

> Because you're not realistically going to retain a total history of all
> CIDs you've ever seen. You MAY treat it as an error if you notice that one
> recurs, so that servers are disincented from doing so, but you're not
> obliged to check that over the whole connection lifetime. However, without
> maintaining that history for a sufficiently long time, you then can't
> differentiate for certain between a retransmission of an old NCID frame and
> a new issuance of the same CID (an error, but one you might miss).
> Therefore, you could wind up in a state where the peers disagree about
> whether a CID is still live.
>
> The options were a requirement to keep history for a certain length of
> time (and hope that packets don't get delayed longer than whatever
> arbitrary timeout we pick) or using sequence numbers and allowing tracking
> with a similar data structure as that which tracks whether Stream IDs are
> not-yet-open, open, or closed.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/quicwg/base-drafts/issues/2159#issuecomment-447145188>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ABD1oceRNi0ITMvVBtKHr-pt0lwaBKKxks5u4tXMgaJpZM4ZSa1C>
> .
>


-- 
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/2159#issuecomment-447149186