IETF Logo Mail Archive

Re: [quicwg/base-drafts] Address validation for connection migration (#732)

janaiyengar <notifications@github.com> Tue, 17 October 2017 05:00 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 CE4F91320CF for <quic-issues@ietfa.amsl.com>; Mon, 16 Oct 2017 22:00:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.019
X-Spam-Level:
X-Spam-Status: No, score=-2.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 hA6_Ae7KX8HR for <quic-issues@ietfa.amsl.com>; Mon, 16 Oct 2017 22:00:54 -0700 (PDT)
Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 03817132332 for <quic-issues@ietf.org>; Mon, 16 Oct 2017 22:00:53 -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=WyKcHElDw63fE+cQ8JVAgEqHFxM=; b=NQMGPNJp35KXGlzg JDBdYv/os9OSKeRdydPYdLgMAwprX7oWBVwxJPPhB/e0j4ZK7wIAGwrbHBlh/Kdu sQxz7wQR0mMxvI+2II12D62oV3zLfKi3gZLv5fX7Ofk64IyU27aFI0mvAoUkJas9 XwVliLfvCrSsQj2Waq36hA1/+KQ=
Received: by filter0094p1iad2.sendgrid.net with SMTP id filter0094p1iad2-19973-59E58E84-30 2017-10-17 05:00:52.985576177 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0005p1iad2.sendgrid.net (SG) with ESMTP id lqw148lbSa25qIqal2f84w for <quic-issues@ietf.org>; Tue, 17 Oct 2017 05:00:53.010 +0000 (UTC)
Date: Tue, 17 Oct 2017 05:00:53 +0000
From: janaiyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abec412e46bb37df2c8b63486aae62a7636f3df0bb92cf0000000115fd508492a169ce0ee9dd49@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/732/c337118214@github.com>
In-Reply-To: <quicwg/base-drafts/pull/732@github.com>
References: <quicwg/base-drafts/pull/732@github.com>
Subject: Re: [quicwg/base-drafts] Address validation for connection migration (#732)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59e58e84d5934_76e13fb5fd268f3492060"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0UVW7aIzSeGz1BvHKPNm2iUwAS/3mZaaliwF sZE2bKgl3DWC+aLGYhUytTvozAtwxmwxcKrP9gtTU2+RVa96dZh02ofFkD1MXED+OfasIGNKyl8OsX S58TSp2LP8bgeErsqVssKrbqZxDUUBYYIrJjHvNRWwdhJCrBg/xHW3krJXfHYTGCTnWe3oFlXmC/NX Y=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/K73MLr9Z3K4xqxicnGlloA4rYNc>
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, 17 Oct 2017 05:00:56 -0000

Hm, yes, you're right. So, I do have articulated rules about when to switch, but it'll take a lot more to explain, and it is the "more detailed model" of switching. So, IIUC, in this simple case, client swithces and sends packet from new IP/port, server sees packet from new address and starts validation, during and after validation completes continues sending data to new IP/port. Is this correct? This is fine with me. (FWIW, this is exactly what GQUIC used to do/does right now, and we're working through its inadequacies.)

-- 
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/732#issuecomment-337118214

v2.43.4 | Report a Bug | By Email | System Status