IETF Logo Mail Archive

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

Jana Iyengar <notifications@github.com> Wed, 27 March 2019 09:46 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 D48A61202A7 for <quic-issues@ietfa.amsl.com>; Wed, 27 Mar 2019 02:46:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3
X-Spam-Level:
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: 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 EocKQpsmCdJa for <quic-issues@ietfa.amsl.com>; Wed, 27 Mar 2019 02:46:12 -0700 (PDT)
Received: from o1.sgmail.github.com (o1.sgmail.github.com [192.254.114.176]) (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 3028C1202C4 for <quic-issues@ietf.org>; Wed, 27 Mar 2019 02:46:12 -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=Y14Cc1VMhMigf3s4IJw1jdL4rPE=; b=GK4NgViaCcpfWkxi p+Rwp411S8HcW/lbpJvuVUvf2OeywvbUOtvP1cP5oRgt96zUJXhfJm95TxCQ+L8T 3Uxy16+/hSqR9LfdMCDNS3WCwBuMw2KW+wETdgSkvTvW1XEKKhO64Wo4cplCyVYw rduJIXRd6QU5z77QmWMVsxXHUaI=
Received: by filter0357p1iad2.sendgrid.net with SMTP id filter0357p1iad2-10116-5C9B4663-2 2019-03-27 09:46:11.094031928 +0000 UTC m=+365860.284448044
Received: from github-lowworker-c7d2ff2.cp1-iad.github.net (unknown [192.30.252.32]) by ismtpd0026p1iad2.sendgrid.net (SG) with ESMTP id 3k8f6YcvS9GJCMFbueP4xA for <quic-issues@ietf.org>; Wed, 27 Mar 2019 09:46:11.050 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-c7d2ff2.cp1-iad.github.net (Postfix) with ESMTP id 022364C0306 for <quic-issues@ietf.org>; Wed, 27 Mar 2019 02:46:11 -0700 (PDT)
Date: Wed, 27 Mar 2019 09:46:11 +0000
From: Jana Iyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abfc89a64d28e07b9c56b9f8702b92b8322a0d39e192cf0000000118b3086292a169ce181e38a8@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/477066276@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_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-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak066y1MAEIRoxNtpq5YX32VQP5mbeIC+hV7Xh AFnP2zlMzs25ngbNF6mngjdEfF/0h7zXXqdzfmWMU1Ruq1n7kvywEkidV6S6ZoQV9Yf8DHJ2S3A44x qg/9WPFu3uWxDomrt6OpRZ2ne0ynQIXq70iaNsttl9rCwTLkXHmYn7vQ4YwS2q11OB+dSc5CLPIsb2 k=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/nFLHPH7wMqgD-enz5SmCa8mfF0o>
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: 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:
https://github.com/quicwg/base-drafts/issues/2389#issuecomment-477066276

v2.23.0 | Report a Bug | By Email