Re: [quicwg/base-drafts] A more complete connection migration (#1012)

Christian Huitema <notifications@github.com> Tue, 26 December 2017 00:12 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 54016126CE8 for <quic-issues@ietfa.amsl.com>; Mon, 25 Dec 2017 16:12:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.03
X-Spam-Level:
X-Spam-Status: No, score=-2.03 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_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-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 BIMYLKuFb560 for <quic-issues@ietfa.amsl.com>; Mon, 25 Dec 2017 16:12:17 -0800 (PST)
Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (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 5EF9F126C2F for <quic-issues@ietf.org>; Mon, 25 Dec 2017 16:12:17 -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=0fKUhSYUOutzLSQHHRvcbMvpZk0=; b=eClSkSNl9vwKMsna gR8l2+agUIs6kpd8uHSxZb8HFV3OTufrF5iRjIpbGFjXXGvLbrbhEg/pq/uJ9GIu YtomOg+ggqYtZnqLH9EFEtW4ZcuGsV/bM/4noWlsDuXj5ITEGdTvfmqAIz8btYBh aAcoey0qfo9TaDomfMjl0wjOB1E=
Received: by filter0632p1las1.sendgrid.net with SMTP id filter0632p1las1-28370-5A4193E0-E 2017-12-26 00:12:16.245575072 +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 ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id tWi-SA_jTia_6wjDFDhElg for <quic-issues@ietf.org>; Tue, 26 Dec 2017 00:12:16.140 +0000 (UTC)
Date: Tue, 26 Dec 2017 00:12:16 +0000
From: Christian Huitema <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abeec4d3434c2fab4d83bb83f72cbfe77fbae4487692cf00000001165955e092a169ce10c89c07@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1012/c353897083@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1012@github.com>
References: <quicwg/base-drafts/pull/1012@github.com>
Subject: Re: [quicwg/base-drafts] A more complete connection migration (#1012)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a4193e07fbf_4cc03ffa896d4f34224701"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: huitema
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0+jenUJ8imzbcAUfiqGcOXhvLx9rdauhCdVm QdVoV9zroDGrQNqcimwe6lqqwmr4khJ89GQwwLcM4wGvy6hpX2Wn+l8jrM3mcWNiS5ULn1YWg1+Dj6 Wc/1InlTp7/0Qu4XzOv0RtjP3cnHoVBDDyDt+EmmnlRDNZaLJ+wyN4BoobxFZgTNw+sAg8ctNREUSA I=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/pcK1Q2lJfFXKPFAoALjPO_vvEa4>
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: Tue, 26 Dec 2017 00:12:19 -0000

I have mixed feelings about this. First, I am not sure that this belongs to the frame layer. The path challenge is in many ways similar to a client initial packet. It requires the same kind of padding, for the same reason. And it carries similar content restrictions such as "no other frame allowed". A new packet type might be more appropriate than a frame type.

Second, this probably requires a three ways handshake, not just a question response. And it would be better served with a symmetric structure -- 
Maybe "your nonce, my nonce", so as to allow symmetry.

Then, there maybe a need for more attributes than nonces, especially if we want to handle NAT rebinding. Like, echoing the address from where this was sent.

-- 
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/1012#issuecomment-353897083