IETF Logo Mail Archive

Re: [quicwg/base-drafts] ClientInitial is special (#627)

MikkelFJ <notifications@github.com> Tue, 13 June 2017 10:42 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 2C98D12EC63 for <quic-issues@ietfa.amsl.com>; Tue, 13 Jun 2017 03:42:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.019
X-Spam-Level:
X-Spam-Status: No, score=-7.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_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 hKmz7z4M4Onb for <quic-issues@ietfa.amsl.com>; Tue, 13 Jun 2017 03:42:08 -0700 (PDT)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext1.iad.github.net [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 3B41512EE46 for <quic-issues@ietf.org>; Tue, 13 Jun 2017 03:33:31 -0700 (PDT)
Date: Tue, 13 Jun 2017 03:33:30 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1497350010; bh=D1upUvfCP7lHflbctS2La/o+CBKjW3qVb5dT4E/DEd4=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gSCDvR8BziTrGWb2WIaBVByiwVU44EF0N4f8rIL84DtsOBJgSWxVVIUh4bIbda7Qx CYq8SovgdibVaR+z6g40sgrRMLJQcVvEVqEHdD61FqRaJ61dzcEPmx5XqPwcSuuH5F /BWZEwA9O1Uu3jA+PLTYJolrQvgHaSjZw7t/+QoU=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab9da87424b9213980eca341c109c1355560c1342e92cf000000011557817a92a169ce0e090b03@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/627/308075737@github.com>
In-Reply-To: <quicwg/base-drafts/issues/627@github.com>
References: <quicwg/base-drafts/issues/627@github.com>
Subject: Re: [quicwg/base-drafts] ClientInitial is special (#627)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_593fbf7a61b6e_1a2d23fb1eae73c3c9503b"; 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/9kvC12Ugt4vUOX1Ok1DmjsrG0-0>
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: Tue, 13 Jun 2017 10:42:10 -0000

> It avoids double-encryption of the TLS handshake packets.

I may get the following wrong, as I haven't studied everything in detail yet, but my take is, ignoring 0RTT:

If the server was required to only respond with a single packet, and double encryption was acceptible (which I think is not problem at all), then the handshake could have the form:

@c ClientInitial ->
<-c ServerInitial
@1-> stream 0{EndOfEarlyData, Finished}, Optionally other streams ->

No ACKS in server to client, no acks in client to server.

If these initial packets are made special, as you suggest with ClientInitial, we can also drop packet numbering of these.

This also avoids the issue with ACKS of untrusted packets during handshake: https://github.com/quicwg/base-drafts/issues/624

-- 
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/627#issuecomment-308075737

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