MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_JwaC84C52Z8AAw/+gFk7Dw)"
Sender: cawood@apple.com
From: Chris Wood <cawood@apple.com>
In-reply-to: <fbb16207-6910-95b1-b278-dbe9f3155012@akamai.com>
Date: Wed, 14 Jun 2017 20:09:01 +0200
Cc: tls@ietf.org
Message-id: <13099025-10E2-42B8-B331-2FE84BC08473@apple.com>
References: <0E6B6240-4F99-46D4-81D0-533473EBFD87@apple.com>
 <fbb16207-6910-95b1-b278-dbe9f3155012@akamai.com>
To: Benjamin Kaduk <bkaduk@akamai.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/T8k0ZT3jgdVY3LSGjxAtNC2nvJs>
Subject: Re: [TLS] TLS 1.3 (-18) at Apple
Precedence: list


--Boundary_(ID_JwaC84C52Z8AAw/+gFk7Dw)
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: quoted-printable


> On Jun 14, 2017, at 8:02 PM, Benjamin Kaduk <bkaduk@akamai.com> wrote:
>=20
>> On 06/14/2017 01:00 PM, Chris Wood wrote:
>> Hi folks,
>>=20
>> Last week at WWDC 2017, we (Apple) announced support for TLS 1.3 (-18) in=
 our platforms. It is not turned on by default. If you=E2=80=99re a member o=
f the developer seed, you may enable it on iOS by downloading and installing=
 the following profile:
>>=20
>>     https://developer.apple.com/go/?id=3Dtls13-mobile-profile
>>=20
>> You may also enable support on macOS with the following defaults write:
>>=20
>>     defaults write /Library/Preferences/com.apple.networkd tcp_connect_en=
able_tls13 1
>=20
> Is the plan to stay on draft-18 until it's time to move to the final RFC v=
ersion?

As of now, that is the most likely outcome. Though that may change if most o=
ther clients and servers move to a more recent version.

>> Our goal is maximal coverage in apps and networks. We encourage everyone w=
ho=E2=80=99s a member to opt in and start testing your services.=20
>>=20
>> Note, we currently do not have 0-RTT data support.
>>=20
>=20
> Seems prudent, given how much it's still in flux (and the lack of publishe=
d application profiles for its use).

Precisely.=20

Best,
Chris=20


--Boundary_(ID_JwaC84C52Z8AAw/+gFk7Dw)
Content-type: text/html; charset=utf-8
Content-transfer-encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div><br></div><div>On Jun 14, 2017, at 8:0=
2 PM, Benjamin Kaduk &lt;<a href=3D"mailto:bkaduk@akamai.com">bkaduk@akamai.=
com</a>&gt; wrote:<br><br></div><blockquote type=3D"cite"><div>
 =20
    <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8"=
>
 =20
 =20
    On 06/14/2017 01:00 PM, Chris Wood wrote:<br>
    <blockquote type=3D"cite" cite=3D"mid:0E6B6240-4F99-46D4-81D0-533473EBFD=
87@apple.com">
      <pre wrap=3D"">Hi folks,

Last week at WWDC 2017, we (Apple) announced support for TLS 1.3 (-18) in ou=
r platforms. It is not turned on by default. If you=E2=80=99re a member of t=
he developer seed, you may enable it on iOS by downloading and installing th=
e following profile:

    <a class=3D"moz-txt-link-freetext" href=3D"https://developer.apple.com/g=
o/?id=3Dtls13-mobile-profile">https://developer.apple.com/go/?id=3Dtls13-mob=
ile-profile</a>

You may also enable support on macOS with the following defaults write:

    defaults write /Library/Preferences/com.apple.networkd tcp_connect_enabl=
e_tls13 1
</pre>
    </blockquote>
    <br>
    Is the plan to stay on draft-18 until it's time to move to the final
    RFC version?<br></div></blockquote><div><br></div><div>As of now, that i=
s the most likely outcome. Though that may change if most other clients and s=
ervers move to a more recent version.</div><br><blockquote type=3D"cite"><di=
v>
   =20
    <blockquote type=3D"cite" cite=3D"mid:0E6B6240-4F99-46D4-81D0-533473EBFD=
87@apple.com">
      <pre wrap=3D"">Our goal is maximal coverage in apps and networks. We e=
ncourage everyone who=E2=80=99s a member to opt in and start testing your se=
rvices.=20

Note, we currently do not have 0-RTT data support.

</pre>
    </blockquote>
    <br>
    Seems prudent, given how much it's still in flux (and the lack of
    published application profiles for its use).<br></div></blockquote><div>=
<br></div>Precisely.&nbsp;<div><br></div><div>Best,</div><div>Chris&nbsp;</d=
iv><div><br></div></body></html>=

--Boundary_(ID_JwaC84C52Z8AAw/+gFk7Dw)--