IETF Logo Mail Archive

Re: [TLS] 0-RTT profiles

Benjamin Kaduk <bkaduk@akamai.com> Mon, 06 August 2018 18:20 UTC

Return-Path: <bkaduk@akamai.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE852130EA2 for <tls@ietfa.amsl.com>; Mon, 6 Aug 2018 11:20:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.711
X-Spam-Level:
X-Spam-Status: No, score=-2.711 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.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 prK-wnN7lSWy for <tls@ietfa.amsl.com>; Mon, 6 Aug 2018 11:20:37 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E61A6130E1C for <tls@ietf.org>; Mon, 6 Aug 2018 11:20:36 -0700 (PDT)
Received: from pps.filterd (m0050095.ppops.net [127.0.0.1]) by m0050095.ppops.net-00190b01. (8.16.0.22/8.16.0.22) with SMTP id w76IH7b3032624; Mon, 6 Aug 2018 19:20:36 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=date : from : to : cc : subject : message-id : references : mime-version : content-type : in-reply-to; s=jan2016.eng; bh=kK2U9KphwAZlMqI4ztFefd17554Mtd1P+A2m7Tq8E6k=; b=Zj19B9PXfJTnVklk2PkoDVKLTWBvxJCf0Sn7fX4Cuf/wSGdqHwSUiZ84WCovo225fJor I4KWD4hgfRA4Gv+zpdIY5CX92NA5+/KYfVamlUKo8mY2rnVhMRiEVAej2iqn4yE8DEEg rmp/cICIpDz1zVg7iIlrmkYo/CM/EjmsdsvpZb7zHS33a1TsYXgEihNKZ7InNgXE22QG rQIDWhOqZBwnLb9JuBha71addjZhIW3EdLH1/W9q6aKihZe7HPOpLPYSP5evZUUeDPV1 lfn7979BqjfclF7wfCwkq9E78F0+xfb2eVlm68Y3FMglLvFe6P22BUJ4X0ekwq5w8FTl Pw==
Received: from prod-mail-ppoint4 (a96-6-114-87.deploy.static.akamaitechnologies.com [96.6.114.87] (may be forged)) by m0050095.ppops.net-00190b01. with ESMTP id 2kn3p372wt-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 06 Aug 2018 19:20:35 +0100
Received: from pps.filterd (prod-mail-ppoint4.akamai.com [127.0.0.1]) by prod-mail-ppoint4.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w76IKJ6K031839; Mon, 6 Aug 2018 14:20:34 -0400
Received: from prod-mail-relay15.akamai.com ([172.27.17.40]) by prod-mail-ppoint4.akamai.com with ESMTP id 2kn7fvqtbe-1; Mon, 06 Aug 2018 14:20:34 -0400
Received: from bos-lpczi.kendall.corp.akamai.com (bos-lpczi.kendall.corp.akamai.com [172.19.17.86]) by prod-mail-relay15.akamai.com (Postfix) with ESMTP id 6663A20070; Mon, 6 Aug 2018 18:20:34 +0000 (GMT)
Received: from bkaduk by bos-lpczi.kendall.corp.akamai.com with local (Exim 4.86_2) (envelope-from <bkaduk@akamai.com>) id 1fmk7N-00011g-ID; Mon, 06 Aug 2018 13:20:33 -0500
Date: Mon, 06 Aug 2018 13:20:33 -0500
From: Benjamin Kaduk <bkaduk@akamai.com>
To: Joseph Birr-Pixton <jpixton@gmail.com>
Cc: "<tls@ietf.org>" <tls@ietf.org>
Message-ID: <20180806182033.GO28516@akamai.com>
References: <CACaGApm=q9aJqeioiHax-G=mZPqnhqzdG=q7iunGWWYSvfsdcQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CACaGApm=q9aJqeioiHax-G=mZPqnhqzdG=q7iunGWWYSvfsdcQ@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-08-06_08:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=505 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1808060191
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-08-06_08:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=548 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1808060190
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/h_y7SUB6vF84p5lKPxDQ187TKQ4>
Subject: Re: [TLS] 0-RTT profiles
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Aug 2018 18:20:39 -0000

On Mon, Aug 06, 2018 at 07:01:42PM +0100, Joseph Birr-Pixton wrote:
> Hello,
> 
> > Application protocols MUST NOT use 0-RTT data without a profile that defines its use.
> > That profile needs to identify which messages or interactions are safe to use with 0-RTT
> > and how to handle the situation when the server rejects 0-RTT and falls back to 1-RTT.
> 
> 0-RTT has now at least two large deployments on the public internet
> that I know of. Are there any such "profiles" published or being
> worked on?

draft-ietf-httpbis-replay is in the RFC Editor's queue.

-Ben

v2.23.0 | Report a Bug | By Email