Re: [quicwg/base-drafts] Client port for new connections (#2061)
Kazuho Oku <notifications@github.com> Mon, 03 December 2018 01:34 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 7DEF1126F72 for <quic-issues@ietfa.amsl.com>; Sun, 2 Dec 2018 17:34:38 -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 12oRPz9JJ6Co for <quic-issues@ietfa.amsl.com>; Sun, 2 Dec 2018 17:34:37 -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 C5E41124D68 for <quic-issues@ietf.org>; Sun, 2 Dec 2018 17:34:36 -0800 (PST)
Date: Sun, 02 Dec 2018 17:34:35 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1543800875; bh=28G0g81byLoAXbvYi3N4ArMa7TcygKqg0A4z64BEVYE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=MXDp7OUcC94tyokmsichYXRx39wzAgWnUI+3EUTq6KMAsXS2hs3m/BIkz/hAgKcGK tbiEn/N48Ohn0ldatXo3J3qEBANHwUGwiTfmVOIwZbC6szfD6Ldq5e4b0ziWficcAR kBKqAKkqBTeHuEFit+8s35MPMf9AMMTYO8Rj+bpM=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abf7ac08e3618d310cb415ce3ed45f09bf76aa94f792cf00000001181c4a2b92a169ce16f48073@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2061/443563374@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2061@github.com>
References: <quicwg/base-drafts/issues/2061@github.com>
Subject: Re: [quicwg/base-drafts] Client port for new connections (#2061)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c04882b9e65b_2ef93fc88c0d45b411816f8"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/rU6zgFUMPr_6RbLCgMRlKcPWME0>
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: Mon, 03 Dec 2018 01:34:38 -0000
I think the fear we have with QUIC is that some NATs are going to run out of UDP ports, or that they would be reusing ports at a rate so fast that we would be seeing involuntary migrations with connections that are idle for just a small fraction of time. Reusing the client-side tuple for multiple connections do mitigate the issue. The trade-off here is the privacy concern that @martinthomson pointed out. I agree that it is a concern, however I might also argue that hiding who's behind does not have a practical benefit for small NATs (e.g. home routers). And huge NATs (e.g. carrier-grade) might have an observer within the NAT. -- 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/2061#issuecomment-443563374
- [quicwg/base-drafts] Client port for new connecti… janaiyengar
- Re: [quicwg/base-drafts] Client port for new conn… Marten Seemann
- Re: [quicwg/base-drafts] Client port for new conn… Martin Thomson
- Re: [quicwg/base-drafts] Client port for new conn… mirjak
- Re: [quicwg/base-drafts] Client port for new conn… ianswett
- Re: [quicwg/base-drafts] Client port for new conn… MikkelFJ
- Re: [quicwg/base-drafts] Client port for new conn… Kazuho Oku
- Re: [quicwg/base-drafts] Client port for new conn… hardie
- Re: [quicwg/base-drafts] Client port for new conn… janaiyengar
- Re: [quicwg/base-drafts] Client port for new conn… janaiyengar
- Re: [quicwg/base-drafts] Client port for new conn… janaiyengar