attachment
<div dir="ltr"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br>From: <b class="gmail_sendername" dir="auto">The IESG</b> <span dir="auto"><<a href="mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.org</a>></span><br>Date: Wed, Apr 22, 2020 at 3:29 PM<br>Subject: [TLS] WG Action: Rechartered Transport Layer Security (tls)<br>To: IETF-Announce <<a href="mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a>><br>Cc: <<a href="mailto:tls@ietf.org">tls@ietf.org</a>>, <<a href="mailto:tls-chairs@ietf.org">tls-chairs@ietf.org</a>>, The IESG <<a href="mailto:iesg@ietf.org">iesg@ietf.org</a>><br></div><br><br>The Transport Layer Security (tls) WG in the Security Area of the IETF has<br>
been rechartered. For additional information, please contact the Area<br>
Directors or the WG Chairs.<br>
<br>
Transport Layer Security (tls)<br>
-----------------------------------------------------------------------<br>
Current status: Active WG<br>
<br>
Chairs:<br>
Christopher Wood <<a href="mailto:caw@heapingbits.net" target="_blank">caw@heapingbits.net</a>><br>
Joseph Salowey <<a href="mailto:joe@salowey.net" target="_blank">joe@salowey.net</a>><br>
Sean Turner <<a href="mailto:sean%2Bietf@sn3rd.com" target="_blank">sean+ietf@sn3rd.com</a>><br>
<br>
Assigned Area Director:<br>
Benjamin Kaduk <<a href="mailto:kaduk@mit.edu" target="_blank">kaduk@mit.edu</a>><br>
<br>
Security Area Directors:<br>
Benjamin Kaduk <<a href="mailto:kaduk@mit.edu" target="_blank">kaduk@mit.edu</a>><br>
Roman Danyliw <<a href="mailto:rdd@cert.org" target="_blank">rdd@cert.org</a>><br>
<br>
Mailing list:<br>
Address: <a href="mailto:tls@ietf.org" target="_blank">tls@ietf.org</a><br>
To subscribe: <a href="https://www.ietf.org/mailman/listinfo/tls" rel="noreferrer" target="_blank">https://www.ietf.org/mailman/listinfo/tls</a><br>
Archive: <a href="https://mailarchive.ietf.org/arch/browse/tls/" rel="noreferrer" target="_blank">https://mailarchive.ietf.org/arch/browse/tls/</a><br>
<br>
Group page: <a href="https://datatracker.ietf.org/group/tls/" rel="noreferrer" target="_blank">https://datatracker.ietf.org/group/tls/</a><br>
<br>
Charter: <a href="https://datatracker.ietf.org/doc/charter-ietf-tls/" rel="noreferrer" target="_blank">https://datatracker.ietf.org/doc/charter-ietf-tls/</a><br>
<br>
The TLS (Transport Layer Security) working group was established in 1996 to<br>
standardize a 'transport layer' security protocol. The basis for the work was<br>
SSL (Secure Socket Layer) v3.0 [RFC6101]. The TLS working group has completed<br>
a series of specifications that describe the TLS protocol v1.0 [RFC2246],<br>
v1.1 [RFC4346], v1.2 [RFC5346], and v1.3 [RFC8446], and DTLS (Datagram TLS)<br>
v1.0 [RFC4347], v1.2 [RFC6347], and v1.3 [draft-ietf-tls-dtls13], as well as<br>
extensions to the protocols and ciphersuites.<br>
<br>
The working group aims to achieve three goals. First, improve the<br>
applicability and suitability of the TLS family of protocols for use in<br>
emerging protocols and use cases. This includes extensions or changes that<br>
help protocols better use TLS as an authenticated key exchange protocol, or<br>
extensions that help protocols better leverage TLS security properties, such<br>
as Exported Authenticators. Extensions that focus specifically on protocol<br>
extensibility are also in scope. This goal also includes protocol changes<br>
that reduce TLS resource consumption without affecting security. Extensions<br>
that help reduce TLS handshake size meet this criterion.<br>
<br>
The second working group goal is to improve security, privacy, and<br>
deployability. This includes, for example, Delegated Credentials and<br>
Encrypted SNI. Security and privacy goals will place emphasis on the<br>
following:<br>
<br>
- Encrypt the ClientHello SNI (Server Name Indication) and other<br>
application-sensitive extensions, such as ALPN (Application-Layer Protocol<br>
Negotiation).<br>
<br>
- Identify and mitigate other (long-term) user tracking or fingerprinting<br>
vectors enabled by TLS deployments and implementations.<br>
<br>
The third goal is to maintain current and previous version of the (D)TLS<br>
protocol as well as to specify general best practices for use of (D)TLS,<br>
extensions to (D)TLS, and cipher suites. This includes recommendations as to<br>
when a particular version should be deprecated. Changes or additions to older<br>
versions of (D)TLS whether via extensions or ciphersuites are discouraged and<br>
require significant justification to be taken on as work items.<br>
<br>
The working group will also place a priority in minimizing gratuitous changes<br>
to (D)TLS.<br>
<br>
Milestones:<br>
<br>
Jul 2020 - Submit "Deprecating MD5 and SHA-1 signature hashes in TLS 1.2"<br>
to the IESG<br>
<br>
Sep 2020 - Submit "Delegated Credentials for TLS" to the IESG<br>
<br>
Nov 2020 - Submit "TLS Ticket Requests" to the IESG<br>
<br>
Nov 2020 - Submit "A Flags Extension for TLS 1.3" to the IESG<br>
<br>
Jan 2021 - Submit "Importing External PSKs for TLS" to the IESG<br>
<br>
Mar 2021 - Submit "Encrypted Server Name Indication for TLS 1.3" to the IESG<br>
<br>
Mar 2021 - Submit "Batch Signing for TLS" to the IESG<br>
<br>
Jul 2021 - Submit "Semi-Static Diffie-Hellman Key Establishment for TLS<br>
1.3" to the IESG<br>
<br>
Jul 2021 - Submit "Compact TLS 1.3" to the IESG<br>
<br>
Nov 2021 - Submit "Hybrid key exchange in TLS 1.3" to the IESG<br>
<br>
<br>
<br>
_______________________________________________<br>
TLS mailing list<br>
<a href="mailto:TLS@ietf.org" target="_blank">TLS@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/tls" rel="noreferrer" target="_blank">https://www.ietf.org/mailman/listinfo/tls</a><br>
</div></div>