Re: [quicwg/base-drafts] Restore CID sequence numbers (#1465)

Nick Banks <notifications@github.com> Wed, 20 June 2018 21:52 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 7C0B1130E26 for <quic-issues@ietfa.amsl.com>; Wed, 20 Jun 2018 14:52:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.01
X-Spam-Level:
X-Spam-Status: No, score=-3.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01] 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 AQY7FI8KqlWK for <quic-issues@ietfa.amsl.com>; Wed, 20 Jun 2018 14:52:41 -0700 (PDT)
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 06BF7130E18 for <quic-issues@ietf.org>; Wed, 20 Jun 2018 14:52:40 -0700 (PDT)
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=5JATcFoOqTrnRIDUILcvdn5eKQ4=; b=kWLRY0ZkU+HscjvN WfrwnKlgrtj+4g3Y7MqRrGWMifQMub2hII6doKSwij5iXztcUtDt//vISlaoA62/ MN1mB8NDvhbVa5PS0AoeWX/olBlUjEIrXcmG/jMJXP/6XQZuR0DJ9OHunjneCF+b xlbHdGdfQuiolT3M9d9pbApnzSc=
Received: by filter1088p1las1.sendgrid.net with SMTP id filter1088p1las1-16833-5B2ACCA8-16 2018-06-20 21:52:40.531763988 +0000 UTC
Received: from github-lowworker-c7d2ff2.cp1-iad.github.net (unknown [192.30.252.32]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id aA9mkzJmQgew7vFfStRKBQ for <quic-issues@ietf.org>; Wed, 20 Jun 2018 21:52:40.389 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-c7d2ff2.cp1-iad.github.net (Postfix) with ESMTP id 5C6DA4C0265 for <quic-issues@ietf.org>; Wed, 20 Jun 2018 14:52:40 -0700 (PDT)
Date: Wed, 20 Jun 2018 21:52:40 +0000
From: Nick Banks <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abbab6ee4b4ce7795f140bc423b54c2d0c56a08bd092cf0000000117428ea892a169ce13ec6080@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1465/review/130601503@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1465@github.com>
References: <quicwg/base-drafts/pull/1465@github.com>
Subject: Re: [quicwg/base-drafts] Restore CID sequence numbers (#1465)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b2acca859fb7_757c2b06c2494f5073298"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nibanks
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak01kJzRCgtMxX2yaM134n/R9g4GtOiLsWZAz2 M+kep9/pGKyT7YWGJguDRM/ngsr6V6dTthi80EKVUOU0fuVDNMWYN/Yc5NQ3wEsvPobzW9fw7QcDVN L9LFJE80AUZR0AAEsVDgoNoZFxxAnfl0nstkrIMLiIvQ3NhuPWWHCmAKfX2nknp8YroQMjwxy9z6cm c=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/K0q67C4KIOeDk_m26PrqjqhGZpE>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.26
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, 20 Jun 2018 21:52:44 -0000

nibanks requested changes on this pull request.

The text here is really confusing and I don't understand what it supposed to be going on. Perhaps you can explain more in the comments and we can figure out some better text.

> @@ -1834,7 +1834,12 @@ new connection IDs using the NEW_CONNECTION_ID frame.
 An endpoint might need to send packets on multiple networks without receiving
 any response from its peer.  To ensure that the endpoint is not linkable across
 each of these changes, a new connection ID is needed for each network.  To
-support this, multiple NEW_CONNECTION_ID messages are needed.
+support this, multiple NEW_CONNECTION_ID messages are needed.  Each
+NEW_CONNECTION_ID is marked with a sequence number.  Connection IDs MUST be used
+on only one local address, and each local address MUST advance to a connection
+ID with a later sequence number each time the connection ID changes.  Once a
+connection ID has been used, connection IDs with an earlier sequence number MUST
+NOT be used for packets with a greater packet number from that local address.

I'm confused as to how this works with probing a new path (but not moving to it). Assume I am currently on Path A using CID 1, then I probe Path B with CID 2. This text seems to state that I may not use CID 1 on Path A with any packet number greater than I used to probe Path B with  CID 2. Is that correct?

> @@ -2613,6 +2627,14 @@ The NEW_CONNECTION_ID is as follows:
 
 The fields are:
 
+Sequence:
+
+: A variable-length integer.  This value starts at 0 and increases by 1 for each
+  connection ID that is provided by the server.  The connection ID that is
+  assigned during the handshake is assumed to have a sequence of -1.  That is,

Is there a real reason we can consider the handshake CID `0` and start from there? I'd rather not have to deal with negative numbers in my code.

-- 
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/pull/1465#pullrequestreview-130601503