Re: [quicwg/base-drafts] Split QUIC core from QUIC v1 (#600)

MikkelFJ <notifications@github.com> Wed, 07 June 2017 08:23 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 6F0BD12EB02 for <quic-issues@ietfa.amsl.com>; Wed, 7 Jun 2017 01:23:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.799
X-Spam-Level:
X-Spam-Status: No, score=-4.799 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_H2=-2.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 89f7L3PDTh7v for <quic-issues@ietfa.amsl.com>; Wed, 7 Jun 2017 01:23:13 -0700 (PDT)
Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (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 C0E2912EAF7 for <quic-issues@ietf.org>; Wed, 7 Jun 2017 01:23:12 -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=P3igbTUiRNpA/f6qd6h468VEZCA=; b=XRdMtFv8gns0/vx4 OwLnn0ZdFt6Oh/Ryh9niAANAUywomjpLakWbvCE43d7A1M28TiS5kpLwAMkteT7b MX+p/Yt1hGVBHYdNOwKQhZUpNr+FhgyxU/XEvHJrBYtech35l02RXNTGTKsilS3t YH3905mV/LbUEyzISSIi6tW2BSU=
Received: by filter0476p1mdw1.sendgrid.net with SMTP id filter0476p1mdw1-27358-5937B7EE-58 2017-06-07 08:23:10.971521566 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id 3JEIo3L1RqCmmVXhd4DwTQ for <quic-issues@ietf.org>; Wed, 07 Jun 2017 08:23:10.992 +0000 (UTC)
Date: Wed, 07 Jun 2017 01:23:10 -0700
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab47d08ac5455e4e31b3173724be4f73ce28210ae492cf00000001154f79ee92a169ce0df481a1@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/600/c306725562@github.com>
In-Reply-To: <quicwg/base-drafts/pull/600@github.com>
References: <quicwg/base-drafts/pull/600@github.com>
Subject: Re: [quicwg/base-drafts] Split QUIC core from QUIC v1 (#600)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5937b7eed9628_66d3fa2c0e05c34797b6"; 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
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2pKDv+k9pJjANFGToTdBFUivKl1QQARKaH3i glunFmmwg1cqdHvPWujwwB4VtSj89QdNxoHPHlH2eBMShu+WGI6Vg9EXhsnkNAXE5iP4DYLsi/BebF 4Z9y3PsEZj68tB20qnjm/JElz8d83AWlKFgG8j0EutpQzghxSlKn+fdV1yXG75JCjrLY+A0Fi5nla9 8=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/igLJP9lqWa6BuvZOccMfjoJEWm8>
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: Wed, 07 Jun 2017 08:23:14 -0000

> I'll note that it feels a little odd to have "core QUIC" not be multiplexed and have no concept of a crypto handshake.

Was wondering the same with the current draft text: there needs to be some requirements a custom crypto handshake must comply to. Such as as error handling, verifying the size of Client Initial Packet, how and when to accept clear text packets and how to transition to encryption. QUIC-TLS and TLS-1.3 covers this, but some information should probably be destilled in a general purpose handshake discussion.

-- 
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/600#issuecomment-306725562