IETF Logo Mail Archive

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

janaiyengar <notifications@github.com> Wed, 21 November 2018 23:52 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 C8EEC128CF3 for <quic-issues@ietfa.amsl.com>; Wed, 21 Nov 2018 15:52:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.46
X-Spam-Level:
X-Spam-Status: No, score=-9.46 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, 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 jhM67pFp23ea for <quic-issues@ietfa.amsl.com>; Wed, 21 Nov 2018 15:52:38 -0800 (PST)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4EE5112008A for <quic-issues@ietf.org>; Wed, 21 Nov 2018 15:52:38 -0800 (PST)
Date: Wed, 21 Nov 2018 15:52:37 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1542844357; bh=Wxz1CAdLEe3UT1NgDIiprwyM8TJ7dPDDE+tRlECFxcM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ectnIgZz6H45enQp89Ns68K9tHQCPveYDnX2rwFBFjYcMi9Sg+mzuZVMGyR8jRrG/ P44nfKpQVuYaGEXPPQG7U7a9kGlmV7v2KNuB0RJPQaDcTn837LX96rvxIS0ROcUTou GXekhfbv4P+jr0Q9lsdtA5kXmWNNplRu6FpgJUB4=
From: janaiyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abebd73ceec93f940bea54765e4cefddafbc3c0e4b92cf00000001180db1c592a169ce16d36b25@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/c440852969@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_5bf5efc552037_6b153fc3680d45c4373785"; 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
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/ui25vOAW00hTjIgVVgR-Q9Lqo3c>
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 23:52:40 -0000

What @MikeBishop said. I would expect ICE to be used alongside QUIC for P2P signaling, and ICE implementations expose  encapsulations  as interfaces to stacks, so QUIC will largely be out of the loop when it comes to migration and such. I think it is a larger project to figure out if ICE and QUIC can be combined in some interesting way to make P2P better.

-- 
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-440852969

v2.23.0 | Report a Bug | By Email