IETF Logo Mail Archive

Re: [quicwg/base-drafts] SIN requirement (#794)

Martin Thomson <notifications@github.com> Mon, 25 September 2017 23:42 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 AC938134601 for <quic-issues@ietfa.amsl.com>; Mon, 25 Sep 2017 16:42:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.019
X-Spam-Level:
X-Spam-Status: No, score=-2.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 ME8-I4AiXWRO for <quic-issues@ietfa.amsl.com>; Mon, 25 Sep 2017 16:42:47 -0700 (PDT)
Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (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 DB41C1345FF for <quic-issues@ietf.org>; Mon, 25 Sep 2017 16:42:46 -0700 (PDT)
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=P7Ovb2s8Y5wZ/bl4frgLdI3OlZM=; b=wF2Yt9N6noZSmHN/ bQHmk1oYoUqZrYRiyNv1lpeQYwfBLQRWMFROXnS0A5g7U8cnsJ+sVm4iIZXPY8Cl iNJ15NLSLOBSP7IbRry2fR9l5dciSO1ajGCbvvNRhwr4d8tYExmQe1a1A0X5VwHS OG2NO2oXNGxslxpDl5MtZ1l2WUg=
Received: by filter0443p1mdw1.sendgrid.net with SMTP id filter0443p1mdw1-3705-59C99439-3 2017-09-25 23:41:45.028961867 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0007p1iad2.sendgrid.net (SG) with ESMTP id 20nOenBkQiWYrjcUxioq4Q for <quic-issues@ietf.org>; Mon, 25 Sep 2017 23:41:44.801 +0000 (UTC)
Date: Mon, 25 Sep 2017 23:41:45 +0000
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abc7352846ecbf896598e96e6054c60c44ce54f45e92cf0000000115e1563892a169ce0f85e734@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/794/332044373@github.com>
In-Reply-To: <quicwg/base-drafts/issues/794@github.com>
References: <quicwg/base-drafts/issues/794@github.com>
Subject: Re: [quicwg/base-drafts] SIN requirement (#794)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59c99438e597f_71033feea0d16f7c501c1"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3ed5m7ptoBsWW9/eR+p6Z4SSs+wurwM3Crhx Kwi5C79giWx4dY4askC117mVYKduUCAnDv5e4LsUwefSViekTYAzR/T0oyutUB8NuJIC38KyimxjIh qoAdfEDOWWHaqzR5aFHtAM3uc7xExAjbtu6VV0sxFknLkHcGVsE54LXZFAzm4rl3H4Ed5cx/F2R+YC Y=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/d_rfVUlx4UoosMsmoSfOgnJCCT0>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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, 25 Sep 2017 23:42:49 -0000

@hardie is correct in that QUIC makes TLS-in-TLS more difficult.  Though that is not the only alternative available.  It is not impossible to do TLS-in-TLS, but it would require some non-trivial effort.

But I think that we should first address the meta-comment.  Do we want to change the character of QUIC such that it can/MUST support SNI encryption?  That's a different question to the one that I think @igorlord had, which is probably just "should HTTP over QUIC require SNI?"  The answer to each might be different.

-- 
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/794#issuecomment-332044373

v2.39.1 | Report a Bug | By Email | System Status