IETF Logo Mail Archive

Re: [quicwg/base-drafts] Can Finished be sent as 1-RTT data? (#785)

Christian Huitema <notifications@github.com> Wed, 20 September 2017 18:48 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 68D721342CB for <quic-issues@ietfa.amsl.com>; Wed, 20 Sep 2017 11:48:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.02
X-Spam-Level:
X-Spam-Status: No, score=-2.02 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_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 3Zd_a35iJRVf for <quic-issues@ietfa.amsl.com>; Wed, 20 Sep 2017 11:48:41 -0700 (PDT)
Received: from o1.sgmail.github.com (o1.sgmail.github.com [192.254.114.176]) (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 C6C611342D1 for <quic-issues@ietf.org>; Wed, 20 Sep 2017 11:48:41 -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=6vRlPeXuhrV154Fv/jThWgc3NK0=; b=OdDVbwxP/d7b+aPs Y/28kuHagti/atUES8pD4EN9iCnhxeBoXwYTA4W5VvFlOjPGo8mj1YRORl7AvWun Wp/tQ9gf7UQu97zEJZQ3eMvqQUscVq9YrbeT7jRHmrjBJfelPT8eng5m5EQ90YkV v5+qtznm8oDf6toX5CsW8oZedpg=
Received: by filter0961p1mdw1.sendgrid.net with SMTP id filter0961p1mdw1-28545-59C2B808-1E 2017-09-20 18:48:40.879943194 +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 ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id VcZkNtfCS8C_pZqO5kmgAA for <quic-issues@ietf.org>; Wed, 20 Sep 2017 18:48:40.879 +0000 (UTC)
Date: Wed, 20 Sep 2017 18:48:41 +0000
From: Christian Huitema <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abe36b94f59ffb37dd8a86255fd82fbfb2aceb6cf192cf0000000115da7a0892a169ce0f7388f0@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/785/330945860@github.com>
In-Reply-To: <quicwg/base-drafts/issues/785@github.com>
References: <quicwg/base-drafts/issues/785@github.com>
Subject: Re: [quicwg/base-drafts] Can Finished be sent as 1-RTT data? (#785)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59c2b8085d8b6_48163fa40978ef78784b"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: huitema
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3paEeYtZhphogMpzzO/IfnEbFdqgG1ZWfZp7 wVz0f0Luzj9ArvbyDvCAFWPP6fsQC//ty5R7eS1u0vXdrscFz6YkKItdiJ2aZ2QeiQORYHixbgyOpc oZ0J/i4DeVl+iUXHOq8pbt61O5bHDI2dCmf6ObG9GPqS8MiTUL4bPhKxFDMduRDb1Ks4tI0Bv8NhQq E=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/_N7frdPwkG3P5_LAgeUIZ0G5foQ>
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, 20 Sep 2017 18:48:43 -0000

Then look at this extract from the QUIC TLS draft:

> Important:
>     Until the handshake is reported as complete, the connection and key exchange are not properly 
> authenticated at the server. Even though 1-RTT keys are available to a server after receiving the first 
> handshake messages from a client, the server cannot consider the client to be authenticated until it 
> receives and validates the client’s Finished message.
>    The requirement for the server to wait for the client Finished message creates a dependency on that 
> message being delivered. A client can avoid the potential for head-of-line blocking that this implies by 
> sending a copy of the STREAM frame that carries the Finished message in multiple packets. This 
> enables immediate server processing for those packets. 

Howdo you do that if you cannot send the Finshed in 1-RTT packets?


-- 
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/785#issuecomment-330945860

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