IETF Logo Mail Archive

Re: [quicwg/base-drafts] QUIC connection migration and IPv6 only NAT64/DNS64 Networks (#2122)

plakhera <notifications@github.com> Wed, 12 December 2018 15:02 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 1B0E4128C65 for <quic-issues@ietfa.amsl.com>; Wed, 12 Dec 2018 07:02:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.056
X-Spam-Level:
X-Spam-Status: No, score=-3.056 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_IMAGE_ONLY_28=1.404, 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 BjTciWUzfyaK for <quic-issues@ietfa.amsl.com>; Wed, 12 Dec 2018 07:02:45 -0800 (PST)
Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 8800512777C for <quic-issues@ietf.org>; Wed, 12 Dec 2018 07:02:45 -0800 (PST)
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=zf81M1no3DNyZmQIp0fdadMpbUw=; b=lC80nUX0ZmxO8XEx lHmG8kXAKDG/1WMz7EVWhT7ZN89iKwNaup7odvBKjqH/fbAIrrhHiBBJS6yR6ciH LaChIIrQQDW28M1eoRCnV52nFaEJ55Kh/DjARCW2TjIeenu7YeR2AnhhWogl3mHs NLN+hGPwGFpsb20ShaQCa9q5GUU=
Received: by filter0505p1iad2.sendgrid.net with SMTP id filter0505p1iad2-15313-5C112314-1C 2018-12-12 15:02:44.384894572 +0000 UTC m=+142965.485833553
Received: from github-lowworker-baaab27.cp1-iad.github.net (unknown [192.30.252.33]) by ismtpd0013p1iad2.sendgrid.net (SG) with ESMTP id axYvIJzPSymqDaMULQi_Mw for <quic-issues@ietf.org>; Wed, 12 Dec 2018 15:02:44.379 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-baaab27.cp1-iad.github.net (Postfix) with ESMTP id 56AF98083D for <quic-issues@ietf.org>; Wed, 12 Dec 2018 07:02:44 -0800 (PST)
Date: Wed, 12 Dec 2018 15:02:44 +0000
From: plakhera <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab95275f970e7d5f3658a2dcc7d0fed25bfc1affce92cf000000011828e51492a169ce1742d117@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2122/446618306@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2122@github.com>
References: <quicwg/base-drafts/issues/2122@github.com>
Subject: Re: [quicwg/base-drafts] QUIC connection migration and IPv6 only NAT64/DNS64 Networks (#2122)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c11231454c91_23103fb1010d45c0167595"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: plakhera
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak37QFjipY/eYY5KHcv6S0KoEXq9BCpC8oombd /4ua6PCoLNnFSj6yXNMns4H4n1HkmbzM16UqSvINIGYFffsmmf93XhVvBtM2AUQ1v0PK6eR6CGeJKx 6xXi/d1w9NvLTwUB/sFO7z535I07UsUqNae3aQicNituBIY6O9282VtDEaGXaVm516PhXarQRVCYNV U=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/ODMpptkSbJtvovfMMqT7IgUPswg>
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, 12 Dec 2018 15:02:48 -0000

> Although not strictly related to this problem, there are also concerns about DNS query privacy and host name exposure in TLS handshake. So a version x might look into the broader DNS / cert auth problem along with multiple server paths.

I was implying these frames to be sent post handshake, encrypted and protected and not exposing anything in the TLS handshake itself.

-- 
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/2122#issuecomment-446618306

v2.23.0 | Report a Bug | By Email