IETF Logo Mail Archive

Re: [quicwg/base-drafts] Servers can't migrate. Period. (#2031)

MikkelFJ <notifications@github.com> Wed, 21 November 2018 10:12 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 C5B89128CFD for <quic-issues@ietfa.amsl.com>; Wed, 21 Nov 2018 02:12:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.47
X-Spam-Level:
X-Spam-Status: No, score=-8.47 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 jitt4ysENfjG for <quic-issues@ietfa.amsl.com>; Wed, 21 Nov 2018 02:12:44 -0800 (PST)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B1E912958B for <quic-issues@ietf.org>; Wed, 21 Nov 2018 02:12:44 -0800 (PST)
Date: Wed, 21 Nov 2018 02:12:43 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1542795163; bh=vz5s3c+EYXGhVLRujFgDjPYc44Q72DWlsfcUD8XSaGw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=2DY7yg/+YjGM50gQZ3oSxjCG+xOefi2g4PzTdEdHNjGh6XDCyxNguG4l13LL881xm XVw76UQKEutK/9JNxdsLsv9It6Zd2gkZpObKW41tWsSYucRcXo/oHPd0nShbpFwygz f9H3cFNW5gZ8dp1D1n6LIdgWwZaJSRv9Xkp+BGKg=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab17fa60f910951c7c4edc4944bebdb8faf0ab75ec92cf00000001180cf19b92a169ce16d36b25@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2031/c440608670@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2031@github.com>
References: <quicwg/base-drafts/pull/2031@github.com>
Subject: Re: [quicwg/base-drafts] Servers can't migrate. Period. (#2031)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bf52f9b5dc49_59143fb0524d45bc580092"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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/KSmoBaxJj3tExhGWmgP0q1Ll3Ow>
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, 21 Nov 2018 10:12:46 -0000

I also dislike this asymmetry but the primary case for client server symmetry is in mostly static P2P server networks.

However, if two voice chat users connect via QUIC using NAT hole punching, this becomes difficult to manage without migration. But I see @martinthomson's point on ICE. How can QUIC realistically handle this use case, because I think it has to, in some version at least.

-- 
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/2031#issuecomment-440608670

v2.23.0 | Report a Bug | By Email