Re: [TLS] Separate APIs for 0-RTT

Eric Rescorla <ekr@rtfm.com> Tue, 13 June 2017 12:28 UTC

Return-Path: <ekr@rtfm.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 AEC08131808 for <tls@ietfa.amsl.com>; Tue, 13 Jun 2017 05:28:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 5_H-3fCP0Dbf for <tls@ietfa.amsl.com>; Tue, 13 Jun 2017 05:28:12 -0700 (PDT)
Received: from mail-yw0-x230.google.com (mail-yw0-x230.google.com [IPv6:2607:f8b0:4002:c05::230]) (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 8373013180A for <tls@ietf.org>; Tue, 13 Jun 2017 05:28:11 -0700 (PDT)
Received: by mail-yw0-x230.google.com with SMTP id 63so47899420ywr.0 for <tls@ietf.org>; Tue, 13 Jun 2017 05:28:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=HBCUNJT7M1zn6eavzTy7m6hNLRc3GQP0+v1Hest0KCo=; b=T84lOtofILRMWN/aDLgJ25WJMSA8Lk8OYw3ylGZpbvxXas0OWKCx7ndfqWCYF+L4G8 XPRFIEAX/f13wfYR9kQX6mFQvv74YZkVsBnG9+YQE5P1eYFMRLZW/WVu7pQZxmGND0e6 DVG/wJmk0uRncpvEXHkkCEq4dkAYhkugMQmkUl8YRMSHITKhdjQ5UmL3OPV6MFOqduRb pzvwWGeGwhz9CQlSsDtHDwLPMJWYrKdLKJACInb3vJtpZZagmcjsQVRNWXZpsPPDk6Br xylgQ5HoDVD/eeRe7pZmjVXxXh3Afq/owYP0SvaDmopMpCHFn1EhTfYvQ+docNaHi7NV 2YVg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=HBCUNJT7M1zn6eavzTy7m6hNLRc3GQP0+v1Hest0KCo=; b=MD5qV7u00bvtrRexKCOx9WO5/WvpOeCSJ7tZnu+A145Wz9CXYoBt9HzD8pd6BtcCV0 qitDql9mhLA4+fum6moyC5zauODe4n2PS5eJ36MjzFEkyg9hq+X0OFiZAgiR7zDNMqeT Wj6cmOI1E5oVNVVAcdFyC6703v/VTcqO8PbujMP+JVWB5vdZlN8ydan+pD/ag8GF7kxh /qnVUN+V7X39aD/LqdInNEIH9WiALjJ6A0CFM8xUFkR8shc0e5i01dTFSqEzsh8tc62C jEu7B7tAQbqZgQFzRbs9BS68wY5gCgM0Db0LL66l5zs3xEZe3tMxgnljnofWqdt5JRUd Qarg==
X-Gm-Message-State: AKS2vOzrczR9tZM3JYOwnG9OU0qCPAwRD0wjtIxP/TSfQreYKzNC/qxj 9wblGAEfLs5M3aUQS84hGhRwsvTZl3Kg
X-Received: by 10.129.43.68 with SMTP id r65mr2832470ywr.24.1497356890568; Tue, 13 Jun 2017 05:28:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.13.215.144 with HTTP; Tue, 13 Jun 2017 05:27:29 -0700 (PDT)
In-Reply-To: <0a4f3f85fa80423ea72d3eec4c7710aa@usma1ex-dag1mb1.msg.corp.akamai.com>
References: <CABcZeBPkRhjLNT2QKO+DgfjE8-e-KrJ5XOLbA9bR24R1Fd96MQ@mail.gmail.com> <0a4f3f85fa80423ea72d3eec4c7710aa@usma1ex-dag1mb1.msg.corp.akamai.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 13 Jun 2017 13:27:29 +0100
Message-ID: <CABcZeBMpeBhcKoJYuMwLyER0VBh+RtVr6amWMPos3CJipXYHcA@mail.gmail.com>
To: "Salz, Rich" <rsalz@akamai.com>
Cc: "tls@ietf.org" <tls@ietf.org>
Content-Type: multipart/alternative; boundary="001a1141e79890ad9e0551d69111"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/ndA6VqKPnCtdpk7qCHXCe_2wbd8>
Subject: Re: [TLS] Separate APIs for 0-RTT
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, 13 Jun 2017 12:28:14 -0000

On Tue, Jun 13, 2017 at 1:22 PM, Salz, Rich <rsalz@akamai.com> wrote:

> Microsoft also has a separate API for 0RTT data.  I would characterize
> things as the two most popular browsers have stated their intention to have
> a single API, and the two most popular system libraries have two.  Outlier
> is clearly wrong.
>

I did not know that about Microsoft. Thanks for the update. I take back
"outlier"



> I agree we don’t have consensus, but do make sure that any wording change
> accommodates the fact that the split isn’t all-versus-one.
>

I was intending to use wording that was neutral between the two options
without any claims about popularity.

Thanks,
-Ekr