IETF Logo Mail Archive

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

MikkelFJ <notifications@github.com> Wed, 21 November 2018 19:09 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 62B90130DFB for <quic-issues@ietfa.amsl.com>; Wed, 21 Nov 2018 11:09:45 -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 2iSmeEovXYJt for <quic-issues@ietfa.amsl.com>; Wed, 21 Nov 2018 11:09:44 -0800 (PST)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EAAC6130DDC for <quic-issues@ietf.org>; Wed, 21 Nov 2018 11:09:43 -0800 (PST)
Date: Wed, 21 Nov 2018 11:09:43 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1542827383; bh=Lo2I84nnaAb5My8XHZKM9StFxmajdcYT98llrBepHtM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=bWWVhgN1kdWJrOp9k8Hl5YZ4Wje0TJWWSQD+CttOo8K99smnylWXK5wvJ73pml+j2 IVCx8PRzAByWxBRGNK+XHM1C7ZTFtLr6kbrIqB4izUQKDXTEG2WGIRQj22Fpf4piLd 5mfBZr/MFkP7kxOBnbIADLKtMpCedz3M6YVL/8iI=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab181924043c2ba80e65fc5f029a8fc7c049ad3b7692cf00000001180d6f7792a169ce16d36b25@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/c440778341@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_5bf5ad77621a_462a3f83f82d45b835710"; 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/QuqB-l7JNZBgDobHZU4QaSDWOE8>
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 19:09:46 -0000

I'm not up to speed on all the punc techs, but my impression is that you often want to end up in a situation where there is no middle man involved after the initial connection is established. Any local NAT boxes would have been punched. I'm not sure this is possible with just QUIC, but some driver logic should be able to provide an IP/port combo to the other end. But this is for stationary NAT.

You can also imagine an intial rendezvous service that is not necessarily punching NAT but rather provides a location service. Once you connect using driver logic, the IP/port is handed to QUIC, and then migration becomes an issue because there is only the endpoints to track the migrations. This is the two traveller scenario as opposed to domestic Skype or Bittorrent.


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

v2.23.0 | Report a Bug | By Email