Re: [quicwg/base-drafts] Requiring per application data in session ticket seems wrong (#3028)

Kazuho Oku <notifications@github.com> Fri, 13 September 2019 06:41 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 A2BB31201EA for <quic-issues@ietfa.amsl.com>; Thu, 12 Sep 2019 23:41:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Level:
X-Spam-Status: No, score=-6.454 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, 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 izn0HlM9PNoo for <quic-issues@ietfa.amsl.com>; Thu, 12 Sep 2019 23:41:01 -0700 (PDT)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59CF91200BA for <quic-issues@ietf.org>; Thu, 12 Sep 2019 23:41:01 -0700 (PDT)
Date: Thu, 12 Sep 2019 23:41:00 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1568356860; bh=oSAFDFxQvo8ugX76w7Z6IfjTlw5g4dHykZ49Rp/ZsQQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=n+4WZ7mcPF8ePAQQf8/OVtFkR/X+KDX/rNMcijtpV13tMgSj+IXPFNceqyHb3dC8k cwjHXk6XKzvpZkX142zAdq1Vs09bAYB1FjeLj4YcrVlxb4rZtNeaUPz3xFBr1oqdAV LLUx0atQX31VjYrdR3ixV62AYFgeWvol1kr+UbJQ=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKY27GGBIBSVV465FFF3RBWHZEVBNHHB2ZES4M@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3028/531118450@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3028@github.com>
References: <quicwg/base-drafts/issues/3028@github.com>
Subject: Re: [quicwg/base-drafts] Requiring per application data in session ticket seems wrong (#3028)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d7b39fc617cc_61bd3f87a4ecd9649877"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/kKIwBTyE14kS75slMhqqOC8FgRg>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 13 Sep 2019 06:41:03 -0000

> So this means that 0-RTT does not work across protocols?

Correct. That is the restriction of TLS 1.3.

-- 
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/3028#issuecomment-531118450