Re: [quicwg/base-drafts] New connection ID message (#232)

ianswett <notifications@github.com> Fri, 31 March 2017 14:23 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 EDC0E1294EE for <quic-issues@ietfa.amsl.com>; Fri, 31 Mar 2017 07:23:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.02
X-Spam-Level:
X-Spam-Status: No, score=-2.02 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, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 Ny8WRNcfW7as for <quic-issues@ietfa.amsl.com>; Fri, 31 Mar 2017 07:23:01 -0700 (PDT)
Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (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 DD5BD129495 for <quic-issues@ietf.org>; Fri, 31 Mar 2017 07:23:00 -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=/k5BJh7hHM2/lgbbVsWJ7/sW94o=; b=vdrJu6qha5BGfcFm /fuzVotOozbpIu3va1Nvx1BcA5otI6AVffxIIztFdCQYAe6nIQbWukH0gqyo7Bvc v+N6iehAyG2fONDL7JDlUpR+N48LrO4uumCjAEHkM1bqIhY4WQ4xnODfA97WRFKC HRlaioS4m+i9Wc3A6fD+1T9QcVI=
Received: by filter0626p1mdw1.sendgrid.net with SMTP id filter0626p1mdw1-1976-58DE6614-9B 2017-03-31 14:22:12.892034846 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id ljljMV3MS5WswQ2KS-uLrA for <quic-issues@ietf.org>; Fri, 31 Mar 2017 14:22:12.878 +0000 (UTC)
Date: Fri, 31 Mar 2017 07:22:12 -0700
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab119ff4c5db0f87ee002313451992fb9013cb519692cf0000000114f6281492a169ce0c1a1553@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/232/290725692@github.com>
In-Reply-To: <quicwg/base-drafts/issues/232@github.com>
References: <quicwg/base-drafts/issues/232@github.com>
Subject: Re: [quicwg/base-drafts] New connection ID message (#232)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_58de6614b1d6c_71633f97e8c73c3c18092c"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0W3k8t1Vjx9mSDM+JeF2kEf/zfWO1/kaZPlP +pdJjUN/2XhQhXEHE3uAc1LcgUBuluOwxAYYDQQ2mTFTFxhuOcmhf6Q/+dK1eCBl5E5ra5sLePhJXO K5USibVyW2ktTKAu6QZmDTDgXYMpCs8mtoi9djdHr38ROCYOJU835Eq0JQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/Y7mtzjVcMT22wUyjALnaP1lOEhU>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 31 Mar 2017 14:23:03 -0000

Ok, now I understand exactly what you're saying, and it was originally what I had in mind, and I'm concerned about two potential issues:
1) You can't safely increase the packet number by more than ~2^31 today, because we only have 4 byte packet numbers on the wire.  Ideally you'd like the packet number gap introduced to be totally random within the full packet number range?  Or possibly we're ok with a single bit of correlation?
2) If you tried to migrate a second time before receiving an acknowledgement for the first time.  I guess that ends up being a sub-case of 1, where the amount you can further increase the packet number becomes limited because the peer hasn't acked the first migration.  Going back to the baseline is dangerous because you don't know if any packets on the intermediate path were received, and it would take some carefulness to avoid re-using packet numbers.

-- 
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/232#issuecomment-290725692