IETF Logo Mail Archive

Re: [TLS] The case for a single stream of data

"Salz, Rich" <rsalz@akamai.com> Tue, 09 May 2017 16:31 UTC

Return-Path: <rsalz@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 8E67212DDD2 for <tls@ietfa.amsl.com>; Tue, 9 May 2017 09:31:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] 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 gx8uM30djIP5 for <tls@ietfa.amsl.com>; Tue, 9 May 2017 09:31:45 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::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 65CC112948B for <tls@ietf.org>; Tue, 9 May 2017 09:31:45 -0700 (PDT)
Received: from pps.filterd (m0050096.ppops.net [127.0.0.1]) by m0050096.ppops.net-00190b01. (8.16.0.21/8.16.0.21) with SMTP id v49GRG6G018109 for <tls@ietf.org>; Tue, 9 May 2017 17:31:43 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-transfer-encoding : mime-version; s=jan2016.eng; bh=Ijb/HbJbMxlwEFdfgQ36Uyrl1o6oQUmKhzEavWiYKVM=; b=AWrHUiXBOFgKkaUfotOBs0pQMPdHYrVKmeQhL93uvgkgMBwK4GXRzWryzgITzB/e5VmZ Z5O3j4EMJjyWGdFVwg9TjWTeTj7C240dYTbIGiZXCO6Ba5Vyl+BWwj+vCfSGJcQs4AdG hZ4kDgLZqb00i594oAXhB4OsSyPgSeRD5ZKYdTvP0WAqtoCWJo7VvDBqNRVAiYt1wiUt 514uGQm3dsPIJx7fvoqv2s78j9CQYTB/NHbJ1rjbz2iCgBCpFKZxq9vG9w5MuRt65G7H cgpIitceNdjVI57L2QD6KR+6wBxtg2WdY2pOl7hOIt84wn3xDo4VLopzGcqaB+4owoBt ww==
Received: from prod-mail-ppoint1 (a184-51-33-18.deploy.static.akamaitechnologies.com [184.51.33.18] (may be forged)) by m0050096.ppops.net-00190b01. with ESMTP id 2abcamhx6m-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <tls@ietf.org>; Tue, 09 May 2017 17:31:42 +0100
Received: from pps.filterd (prod-mail-ppoint1.akamai.com [127.0.0.1]) by prod-mail-ppoint1.akamai.com (8.16.0.17/8.16.0.17) with SMTP id v49GQ0ll017959 for <tls@ietf.org>; Tue, 9 May 2017 12:31:42 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.33]) by prod-mail-ppoint1.akamai.com with ESMTP id 2a99tudfnw-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <tls@ietf.org>; Tue, 09 May 2017 12:31:42 -0400
Received: from USMA1EX-DAG1MB5.msg.corp.akamai.com (172.27.123.105) by usma1ex-dag1mb4.msg.corp.akamai.com (172.27.123.104) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 9 May 2017 12:31:40 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb5.msg.corp.akamai.com (172.27.123.105) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 9 May 2017 12:31:39 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1263.000; Tue, 9 May 2017 12:31:39 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: TLS WG <tls@ietf.org>
Thread-Topic: [TLS] The case for a single stream of data
Thread-Index: AQHSxbylbnClX7eBZUm2Z/AGF1sif6HsLwTAgABKdYD//73KwA==
Date: Tue, 09 May 2017 16:31:39 +0000
Message-ID: <1a5362f76c8e445ea03c425741790177@usma1ex-dag1mb1.msg.corp.akamai.com>
References: <CAAF6GDfm=voTt_=JrdGtiaYby1JG8ySU2s6myjjpHKeGvi0bMg@mail.gmail.com> <9f5858c8d86742b9aa82bdac46590c92@usma1ex-dag1mb1.msg.corp.akamai.com> <3510843A-8628-4859-B627-55C4EC7111D9@dukhovni.org>
In-Reply-To: <3510843A-8628-4859-B627-55C4EC7111D9@dukhovni.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.36.228]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-05-09_13:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1705090087
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-05-09_13:, , 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=1015 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1705090087
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/P2VbWNS9YeLpLdkqOge2HVRa4NY>
Subject: Re: [TLS] The case for a single stream of data
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 09 May 2017 16:31:48 -0000

> What would a receiver API then look like?  Would it be something like:
...
> Or did you have something else in mind?  What are your thoughts on the
> sender side?  Just enable 0-RTT and have the toolkit send as much 0-RTT data
> as "fits" and the rest 1-RTT, or an explicit request for a specific 0-RTT payload?

As implemented in OpenSSL; see 
   https://www.openssl.org/docs/manmaster/man3/SSL_read_early_data.html
(which also describes the "write" part, and the query and control functions.)

v2.23.0 | Report a Bug | By Email