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

Jana Iyengar <> Wed, 27 March 2019 09:46 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D48A61202A7 for <>; Wed, 27 Mar 2019 02:46:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3
X-Spam-Status: No, score=-3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id EocKQpsmCdJa for <>; Wed, 27 Mar 2019 02:46:12 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3028C1202C4 for <>; Wed, 27 Mar 2019 02:46:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed;; 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=Y14Cc1VMhMigf3s4IJw1jdL4rPE=; b=GK4NgViaCcpfWkxi p+Rwp411S8HcW/lbpJvuVUvf2OeywvbUOtvP1cP5oRgt96zUJXhfJm95TxCQ+L8T 3Uxy16+/hSqR9LfdMCDNS3WCwBuMw2KW+wETdgSkvTvW1XEKKhO64Wo4cplCyVYw rduJIXRd6QU5z77QmWMVsxXHUaI=
Received: by with SMTP id filter0357p1iad2-10116-5C9B4663-2 2019-03-27 09:46:11.094031928 +0000 UTC m=+365860.284448044
Received: from (unknown []) by (SG) with ESMTP id 3k8f6YcvS9GJCMFbueP4xA for <>; Wed, 27 Mar 2019 09:46:11.050 +0000 (UTC)
Received: from (localhost []) by (Postfix) with ESMTP id 022364C0306 for <>; Wed, 27 Mar 2019 02:46:11 -0700 (PDT)
Date: Wed, 27 Mar 2019 09:46:11 +0000
From: Jana Iyengar <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2389/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Be clearer about the purpose of disable_migration (#2389)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c9b466392f_525a3f9dd54d45c42806"; 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-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak066y1MAEIRoxNtpq5YX32VQP5mbeIC+hV7Xh AFnP2zlMzs25ngbNF6mngjdEfF/0h7zXXqdzfmWMU1Ruq1n7kvywEkidV6S6ZoQV9Yf8DHJ2S3A44x qg/9WPFu3uWxDomrt6OpRZ2ne0ynQIXq70iaNsttl9rCwTLkXHmYn7vQ4YwS2q11OB+dSc5CLPIsb2 k=
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 27 Mar 2019 09:46:17 -0000

Having re-read the minutes from Tokyo, I would re-articulate the problem statement a bit. As you said, disable_migration is an indication from a server that the serving infrastructure cannot handle client address changes. I don't think there's any confusion on this purpose. The pending question IMO is what a server should do if it disables migration and then receives packets on the connection from a different address.

@martinthomson : Do you agree?

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: