IETF Logo Mail Archive

Re: [quicwg/base-drafts] handshake and 0rtt data in a single packet (#630)

ianswett <notifications@github.com> Thu, 09 November 2017 06:09 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 8EF8A12EB96 for <quic-issues@ietfa.amsl.com>; Wed, 8 Nov 2017 22:09:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.615
X-Spam-Level:
X-Spam-Status: No, score=-0.615 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_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 LKtR6w_k-WzT for <quic-issues@ietfa.amsl.com>; Wed, 8 Nov 2017 22:09:47 -0800 (PST)
Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 68D1812EB86 for <quic-issues@ietf.org>; Wed, 8 Nov 2017 22:09:47 -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=JObq/8p6gWDM2QpA3ZL+dNYNYM8=; b=LCQx8yf9PvAc8+Jc rYAm5mF0DndYE7Y9BnVDvwA94t1ltjovK1jdX7R3zyIU3PNoxoDwYtphUyrKOLiH dyffQ714n+Gw0BjN1ecwC/K3V94QtFxAGinCdnVm9DhGonkcgpDbbB9jP5q72fjj asOKpYoY2fqswsqV/H9zr9fzRdA=
Received: by filter0570p1mdw1.sendgrid.net with SMTP id filter0570p1mdw1-786-5A03F12A-3 2017-11-09 06:09:46.130000112 +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 ismtpd0007p1iad1.sendgrid.net (SG) with ESMTP id C1zAM_YBR6yHFJqQr2ENQg for <quic-issues@ietf.org>; Thu, 09 Nov 2017 06:09:46.177 +0000 (UTC)
Date: Thu, 09 Nov 2017 06:09:46 +0000
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab96d4e94f5c5e43bd2b36c3604b8e0d747ad5c9a892cf00000001161bb32a92a169ce0e0bd8dd@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/630/343056871@github.com>
In-Reply-To: <quicwg/base-drafts/issues/630@github.com>
References: <quicwg/base-drafts/issues/630@github.com>
Subject: Re: [quicwg/base-drafts] handshake and 0rtt data in a single packet (#630)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a03f12a17521_1823f88864d8f3435379b"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
tracking:
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1Vq1VGFabN7195ddcJIwYczfRiNw2Fc6rBQL mSIKaeieQBBBUi0WsAXuotZ5NLXe6N4sz7waU1W2sZiFgCCWOo5g7n2+oVYst5fAxmjCIPbuOJEa1m OWDvRF9xhEa/0dLwyfAPt9cqmVS+62MLxpTOjJJSCkH+CWuZ5KBrlfS1FQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/HzgzvMRyFi8FsBYLZ7uDgQ6F-VA>
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: Thu, 09 Nov 2017 06:09:48 -0000

Coming back around on this, I think we end up needing something like option 4 for a simple reason.  We need the ability to ack the cleartext data and not ack the 0RTT data if 0RTT fails.  So they need different packet numbers, even if they're in the same UDP packet.  At that point, sticking together two QUIC 'packets' in a single UDP packet would seem the obvious approach.

-- 
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/630#issuecomment-343056871

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