Re: [quicwg/base-drafts] Be clearer about the purpose of disable_migration (#2389)

Igor Lubashev <notifications@github.com> Mon, 13 May 2019 22:05 UTC

Return-Path: <noreply@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 C905912006E for <quic-issues@ietfa.amsl.com>; Mon, 13 May 2019 15:05:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.392
X-Spam-Level:
X-Spam-Status: No, score=-1.392 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_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 0ceiw_CjXm9V for <quic-issues@ietfa.amsl.com>; Mon, 13 May 2019 15:05:06 -0700 (PDT)
Received: from out-20.smtp.github.com (out-20.smtp.github.com [192.30.252.203]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FCAE120006 for <quic-issues@ietf.org>; Mon, 13 May 2019 15:05:06 -0700 (PDT)
Date: Mon, 13 May 2019 15:05:05 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1557785105; bh=eNeZbmyflCukr1Di2RFWN/1HrVoFIsedm3VfGP4FAWU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=uiqeGOdXh83fsy5inGRrT2ruf6v/6umyd63mhy5huQe8gK66rMfDxwNLja1ThAEQl /wrrYNW6CzummSjUfd+Ql7l8N59jOl/+SVp4YJcCJ2CqHlYQwW00a3+yGG+b5fauqY 9mjk72Mcvgp9KlimGJs8TLMkbdyTLqRE5sJgYpNM=
From: Igor Lubashev <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKY5FJ6BSIBMQLCCI5F244OJDEVBNHHBQHRYVA@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2389/492004255@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2389@github.com>
References: <quicwg/base-drafts/issues/2389@github.com>
Subject: Re: [quicwg/base-drafts] Be clearer about the purpose of disable_migration (#2389)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cd9ea112683d_30d03fef49ecd95c1349b9"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: igorlord
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/pDT7MRNUxOjkQu7sU4f9PQ7GrkQ>
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: Mon, 13 May 2019 22:05:08 -0000

> what a client might expect when it continues sending packets after switching networks to a server that has disable_migration set.

It is my understanding that "disable_migration set" means that packets sourced from a different IP or port are likely to be blackholed.  Hence, the client SHOULD reconnect instead of attempting a connection migration.

As for the servers that specified "disable_migration", they are free to blockhole packets for migrating connections or to honor connection migration (after an ordinary path validation).

-- 
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/2389#issuecomment-492004255