Transport Layer Security (TLS) Extension for Token Binding Protocol Negotiation
draft-ietf-tokbind-negotiation-14

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, ekr@rtfm.com, John Bradley <ve7jtb@ve7jtb.com>, unbearable@ietf.org, tokbind-chairs@ietf.org, ve7jtb@ve7jtb.com, draft-ietf-tokbind-negotiation@ietf.org, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'Transport Layer Security (TLS) Extension for Token Binding Protocol Negotiation' to Proposed Standard (draft-ietf-tokbind-negotiation-14.txt)

The IESG has approved the following document:
- 'Transport Layer Security (TLS) Extension for Token Binding Protocol
   Negotiation'
  (draft-ietf-tokbind-negotiation-14.txt) as Proposed Standard

This document is the product of the Token Binding Working Group.

The IESG contact persons are Benjamin Kaduk and Eric Rescorla.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-tokbind-negotiation/


Technical Summary

In order to use the Token Binding protocol [I-D.ietf-tokbind-protocol], the client and server need to agree on the Token Binding protocol version and the parameters (signature algorithm, length) of the Token Binding key.  This document specifies a new TLS [RFC5246] extension to accomplish this negotiation without introducing additional network round-trips in TLS 1.2 and earlier versions.  The negotiation of the Token Binding protocol and key parameters in combination with TLS 1.3 and later versions is beyond the scope of this document.

Working Group Summary

 This document achieved WG consensus and had no objections.

Document Quality

Multiple Implementations of Token Binding exist and have undergone informal interoperability testing.
Google has token binding behind a feature flag in Chrome that is currently defaulted off.  They have also implemented it in their reverse proxy infrastructure. They have also added support to the Boringssl open source project.
Microsoft added support in Windows 10 RS2 at the beginning of 2017 (later back ported to RS1) .  Edge and IE use that platform support.  It is also available to other applications via system API.  There is also support in ADFS. https://docs.microsoft.com/en-us/windows-server/security/token-binding/introducing-token-binding
NGINX has an open source module https://github.com/google/ngx_token_binding
Token Binding support for Apache https://github.com/google/ngx_token_binding
Openssl patches in opensource https://github.com/google/token_bind
Ping Identity has tested patches to Java and set up a test environment. https://www.ietf.org/mail-archive/web/unbearable/current/msg01332.html
A useful slide share overview https://www.slideshare.net/Identiverse/beyond-bearer-token-binding-as-the-foundation-for-a-more-secure-web-cis-2017
Drafts using token binding exist in the OAuth work group and for OpenID Connect.

Personnel

John Bradley is the document shepherd and the responsible area director is Eric Rescorla.