draft-ietf-tokbind-ttrp-01.txt   draft-ietf-tokbind-ttrp-02.txt 
Internet Engineering Task Force B. Campbell Internet Engineering Task Force B. Campbell
Internet-Draft Ping Identity Internet-Draft Ping Identity
Intended status: Standards Track August 2, 2017 Intended status: Standards Track January 29, 2018
Expires: February 3, 2018 Expires: August 2, 2018
HTTPS Token Binding with TLS Terminating Reverse Proxies HTTPS Token Binding with TLS Terminating Reverse Proxies
draft-ietf-tokbind-ttrp-01 draft-ietf-tokbind-ttrp-02
Abstract Abstract
This document defines common HTTP header fields that enable a TLS This document defines common HTTP header fields that enable a TLS
terminating reverse proxy to convey information about the validated terminating reverse proxy to convey information about the validated
Token Binding Message sent by the client to a backend server, which Token Binding Message sent by the client to a backend server, which
enables that backend server to bind, or verify the binding of, enables that backend server to bind, or verify the binding of,
cookies and other security tokens to the client's Token Binding key. cookies and other security tokens to the client's Token Binding key.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 3, 2018. This Internet-Draft will expire on August 2, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Notation and Conventions . . . . . . . . . . 3 1.1. Requirements Notation and Conventions . . . . . . . . . . 3
2. HTTP Header Fields and Processing Rules . . . . . . . . . . . 3 2. HTTP Header Fields and Processing Rules . . . . . . . . . . . 3
2.1. Token Binding ID HTTP Header Fields . . . . . . . . . . . 3 2.1. Encoding . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Processing Rules . . . . . . . . . . . . . . . . . . . . 4 2.2. Token Binding ID HTTP Header Fields . . . . . . . . . . . 4
2.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . 5 2.3. Processing Rules . . . . . . . . . . . . . . . . . . . . 4
2.3.1. Provided Token Binding ID . . . . . . . . . . . . . . 5 2.4. Examples . . . . . . . . . . . . . . . . . . . . . . . . 5
2.3.2. Provided and Referred Token Binding IDs . . . . . . . 6 2.4.1. Provided Token Binding ID . . . . . . . . . . . . . . 6
3. Security Considerations . . . . . . . . . . . . . . . . . . . 6 2.4.2. Provided and Referred Token Binding IDs . . . . . . . 6
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 3. Security Considerations . . . . . . . . . . . . . . . . . . . 7
4.1. HTTP Message Header Field Names Registration . . . . . . 7 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
4.1. HTTP Message Header Field Names Registration . . . . . . 8
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
5.1. Normative References . . . . . . . . . . . . . . . . . . 8 5.1. Normative References . . . . . . . . . . . . . . . . . . 8
5.2. Informative References . . . . . . . . . . . . . . . . . 9 5.2. Informative References . . . . . . . . . . . . . . . . . 9
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 9 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 9
Appendix B. Document History . . . . . . . . . . . . . . . . . . 9 Appendix B. Document History . . . . . . . . . . . . . . . . . . 10
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
Token Binding over HTTP [I-D.ietf-tokbind-https] provides a mechanism Token Binding over HTTP [I-D.ietf-tokbind-https] provides a mechanism
that enables HTTP servers to cryptographically bind cookies and other that enables HTTP servers to cryptographically bind cookies and other
security tokens to a key held by the browser or other HTTP client, security tokens to a key held by the browser or other HTTP client,
possession of which is proven on the TLS [RFC5246] connections over possession of which is proven on the TLS [RFC5246] connections over
which the tokens are used. When Token Binding is negotiated in the which the tokens are used. When Token Binding is negotiated in the
TLS handshake [I-D.ietf-tokbind-negotiation] the client sends an TLS handshake [I-D.ietf-tokbind-negotiation] the client sends an
encoded Token Binding Message [I-D.ietf-tokbind-protocol] as a header encoded Token Binding Message [I-D.ietf-tokbind-protocol] as a header
skipping to change at page 3, line 35 skipping to change at page 3, line 35
bind, or verify the binding of, cookies and other security tokens to bind, or verify the binding of, cookies and other security tokens to
the client's Token Binding key. The usage of the headers, both the the client's Token Binding key. The usage of the headers, both the
reverse proxy adding it and the application server using them to bind reverse proxy adding it and the application server using them to bind
cookies or other tokens, are to be configuration options of the cookies or other tokens, are to be configuration options of the
respective systems as they will not always be applicable. respective systems as they will not always be applicable.
1.1. Requirements Notation and Conventions 1.1. Requirements Notation and Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in RFC "OPTIONAL" in this document are to be interpreted as described in BCP
2119 [RFC2119]. 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
2. HTTP Header Fields and Processing Rules 2. HTTP Header Fields and Processing Rules
2.1. Token Binding ID HTTP Header Fields 2.1. Encoding
The Token Binding Protocol [I-D.ietf-tokbind-protocol] recommends The field-values of the HTTP headers defined herein utilize the
that implementations make Token Binding IDs available to the following encoded forms.
application as opaque byte sequences, enabling those applications to
use the Token Binding IDs when generating and verifying bound tokens.
In the context of a TLS terminating reverse proxy (TTRP) deployment,
the provided and referred Token Binding IDs are made available to the
backend application as the "Sec-Provided-Token-Binding-ID" and "Sec-
Referred-Token-Binding-ID" HTTP headers respectively. The value of
both headers is an "EncodedTokenBindingID", for which the ABNF
[RFC5234] syntax is shown in Figure 1 below. "EncodedTokenBindingID"
is a single HTTP header field-value as defined in Section 3.2 of
[RFC7230], which MUST NOT have a list of values or occur multiple A Token Binding ID is represented as an "EncodedTokenBindingID", for
times in a request. An "EncodedTokenBindingID" is only for use in which the ABNF [RFC5234] syntax is shown in Figure 1 below.
HTTP requests and MUST NOT to be used in HTTP responses.
EncodedTokenBindingID = *( DIGIT / ALPHA / "-" / "_" ) EncodedTokenBindingID = *( DIGIT / ALPHA / "-" / "_" )
DIGIT = <Defined in Section B.1 of [RFC5234]> DIGIT = <Defined in Section B.1 of [RFC5234]>
ALPHA = <Defined in Section B.1 of [RFC5234]> ALPHA = <Defined in Section B.1 of [RFC5234]>
Figure 1: Encoded Token Binding ID Header ABNF Figure 1: Encoded Token Binding ID Header ABNF
The value of an "EncodedTokenBindingID" is a base64url encoding of The value of an "EncodedTokenBindingID" is a base64url encoding of
the TokenBindingID byte sequence (see section 3 of the TokenBindingID byte sequence (see section 3 of
[I-D.ietf-tokbind-protocol]) using the URL and filename safe alphabet [I-D.ietf-tokbind-protocol]) using the URL and filename safe alphabet
described in Section 5 of [RFC4648], with all trailing pad characters described in Section 5 of [RFC4648], with all trailing pad characters
'=' omitted and without the inclusion of any line breaks, whitespace, '=' omitted and without the inclusion of any line breaks, whitespace,
or other additional characters. or other additional characters.
2.2. Processing Rules 2.2. Token Binding ID HTTP Header Fields
The Token Binding Protocol [I-D.ietf-tokbind-protocol] recommends
that implementations make Token Binding IDs available to the
application as opaque byte sequences, enabling those applications to
use the Token Binding IDs when generating and verifying bound tokens.
In the context of a TLS terminating reverse proxy (TTRP) deployment,
the TTRP makes the Token Binding ID(s) available to the backend
application, when applicable, with the following header fields.
Sec-Provided-Token-Binding-ID
The Token Binding ID of the provided Token Binding represented as
an "EncodedTokenBindingID" as defined in Section 2.1.
Sec-Referred-Token-Binding-ID
The Token Binding ID of the referred Token Binding represented as
an "EncodedTokenBindingID" as defined in Section 2.1.
Both "Sec-Provided-Token-Binding-ID" and "Sec-Referred-Token-Binding-
ID" are single HTTP header field-valued as defined in Section 3.2 of
[RFC7230], which MUST NOT have a list of values or occur multiple
times in a request. An "EncodedTokenBindingID" is only for use in
HTTP requests and MUST NOT to be used in HTTP responses.
2.3. Processing Rules
This section defines the applicable processing rules for a TLS This section defines the applicable processing rules for a TLS
terminating reverse proxy (TTRP) and backend server(s) to provide terminating reverse proxy (TTRP) and backend server(s) to provide
server side support of Token Binding over HTTP server side support of Token Binding over HTTP
[I-D.ietf-tokbind-https] using the HTTP headers described in [I-D.ietf-tokbind-https] using the HTTP headers described in
Section 2.1. Use of the technique is to be a configuration or Section 2.2. Use of the technique is to be a configuration or
deployments option and the processing rules described herein are for deployments option and the processing rules described herein are for
servers operating with that option enabled. servers operating with that option enabled.
A TTRP negotiates the use of Token Binding with the client per A TTRP negotiates the use of Token Binding with the client per
[I-D.ietf-tokbind-negotiation] and validates the Token Binding [I-D.ietf-tokbind-negotiation] and validates the Token Binding
Message as defined in The Token Binding Protocol Message as defined in The Token Binding Protocol
[I-D.ietf-tokbind-protocol] and Token Binding over HTTP [I-D.ietf-tokbind-protocol] and Token Binding over HTTP
[I-D.ietf-tokbind-https] for each HTTP request on the underlying TLS [I-D.ietf-tokbind-https] for each HTTP request on the underlying TLS
connection. Requests with a valid Token Binding Message (and meeting connection. Requests with a valid Token Binding Message (and meeting
any other authorization or policy requirements of the TTRP) are any other authorization or policy requirements of the TTRP) are
dispatched to the backend server with the following modifications. dispatched to the backend server with the following modifications.
1. The "Sec-Token-Binding" header in the original incoming request 1. The "Sec-Token-Binding" header in the original incoming request
MUST be removed from the request that is dispatched to the MUST be removed from the request that is dispatched to the
backend server. backend server.
2. The Token Binding ID of the provided Token Binding of the Token 2. The Token Binding ID of the provided Token Binding of the Token
Binding Message MUST be placed in the "Sec-Provided-Token- Binding Message MUST be placed in the "Sec-Provided-Token-
Binding-ID" header field of the dispatched request using the Binding-ID" header field of the dispatched request using the
format defined in Section 2.1. format defined in Section 2.2.
3. If the Token Binding Message contains a referred Token Binding, 3. If the Token Binding Message contains a referred Token Binding,
the referred Token Binding ID MUST be placed in the "Sec- the referred Token Binding ID MUST be placed in the "Sec-
Referred-Token-Binding-ID" header field of the dispatched request Referred-Token-Binding-ID" header field of the dispatched request
using the format defined in Section 2.1. Otherwise, the "Sec- using the format defined in Section 2.2. Otherwise, the "Sec-
Referred-Token-Binding-ID" header field MUST NOT be present in Referred-Token-Binding-ID" header field MUST NOT be present in
the dispatched request. the dispatched request.
4. Any occurrence of the "Sec-Provided-Token-Binding-ID" or "Sec- 4. Any occurrence of the "Sec-Provided-Token-Binding-ID" or "Sec-
Referred-Token-Binding-ID" header in the original incoming Referred-Token-Binding-ID" header in the original incoming
request MUST be removed or overwritten before forwarding the request MUST be removed or overwritten before forwarding the
request. request.
Requests made over a TLS connection where the use of Token Binding Requests made over a TLS connection where the use of Token Binding
was not negotiated MUST be sanitized by removing any occurrences of was not negotiated MUST be sanitized by removing any occurrences of
the "Sec-Provided-Token-Binding-ID" and "Sec-Referred-Token-Binding- the "Sec-Provided-Token-Binding-ID" and "Sec-Referred-Token-Binding-
ID" header fields prior to dispatching the request to the backend ID" header fields prior to dispatching the request to the backend
server. server.
Forward proxies and other intermediaries MUST NOT add the "Sec- Forward proxies and other intermediaries MUST NOT add the "Sec-
Provided-Token-Binding-ID" or "Sec-Referred-Token-Binding-ID" header Provided-Token-Binding-ID" or "Sec-Referred-Token-Binding-ID" header
to requests. to requests.
2.3. Examples 2.4. Examples
Extra line breaks and whitespace have been added to the following Extra line breaks and whitespace have been added to the following
examples for display and formatting purposes only. examples for display and formatting purposes only.
2.3.1. Provided Token Binding ID 2.4.1. Provided Token Binding ID
The following "Sec-Token-Binding" header is from an HTTP request made The following "Sec-Token-Binding" header is from an HTTP request made
over a TLS connection between the client and the TTRP where the use over a TLS connection between the client and the TTRP where the use
of Token Binding has been negotiated (The base64url-encoded of Token Binding has been negotiated (The base64url-encoded
representation of the exported keying material, which can be used to representation of the exported keying material, which can be used to
validate the Token Binding Message, for that connection is validate the Token Binding Message, for that connection is
"AYVUayPTP9RmELNpGjFl6Ykm2CUx7pUMxe35yb11dgU"). The encoded Token "AYVUayPTP9RmELNpGjFl6Ykm2CUx7pUMxe35yb11dgU"). The encoded Token
Binding Message has the provided Token Binding the client uses with Binding Message has the provided Token Binding the client uses with
the server. the server.
skipping to change at page 6, line 10 skipping to change at page 6, line 33
After validating the Token Binding Message, the TTRP removes the After validating the Token Binding Message, the TTRP removes the
"Sec-Token-Binding" header and adds the following "Sec-Provided- "Sec-Token-Binding" header and adds the following "Sec-Provided-
Token-Binding-ID" header with the provided Token Binding ID to the Token-Binding-ID" header with the provided Token Binding ID to the
request that is dispatched to the backend server. request that is dispatched to the backend server.
Sec-Provided-Token-Binding-ID: AgBBQKzyIrmcY_YCtHVoSHBut69vrGfFdy1_ Sec-Provided-Token-Binding-ID: AgBBQKzyIrmcY_YCtHVoSHBut69vrGfFdy1_
YKTZfFJv6BjrZsKD9b9FRzSBxDs1twTqnAS71M1RBumuihhI9xqxXKk YKTZfFJv6BjrZsKD9b9FRzSBxDs1twTqnAS71M1RBumuihhI9xqxXKk
Figure 3: Header in HTTP Request to Backend Server Figure 3: Header in HTTP Request to Backend Server
2.3.2. Provided and Referred Token Binding IDs 2.4.2. Provided and Referred Token Binding IDs
The following "Sec-Token-Binding" header is from an HTTP request made The following "Sec-Token-Binding" header is from an HTTP request made
over a TLS connection between the client and the TTRP where the use over a TLS connection between the client and the TTRP where the use
of Token Binding has been negotiated (The base64url-encoded of Token Binding has been negotiated (The base64url-encoded
representation of the exported keying material, which can be used to representation of the exported keying material, which can be used to
validate the Token Binding Message, for that connection is validate the Token Binding Message, for that connection is
"wEWWCP1KPxfq-QL4NxYII_P4ti_9YYqrTpGs28BZEqE"). The encoded Token "wEWWCP1KPxfq-QL4NxYII_P4ti_9YYqrTpGs28BZEqE"). The encoded Token
Binding Message has the provided Token Binding the client uses with Binding Message has the provided Token Binding the client uses with
the server as well as the referred Token Binding that it uses with a the server as well as the referred Token Binding that it uses with a
different server. different server.
skipping to change at page 8, line 14 skipping to change at page 8, line 37
o Applicable protocol: HTTP o Applicable protocol: HTTP
o Status: standard o Status: standard
o Author/change Controller: IETF o Author/change Controller: IETF
o Specification Document(s): [[ this specification ]] o Specification Document(s): [[ this specification ]]
5. References 5. References
5.1. Normative References 5.1. Normative References
[I-D.ietf-tokbind-https] [I-D.ietf-tokbind-https]
Popov, A., Nystrom, M., Balfanz, D., Langley, A., and J. Popov, A., Nystrom, M., Balfanz, D., Langley, A., Harper,
Hodges, "Token Binding over HTTP", draft-ietf-tokbind- N., and J. Hodges, "Token Binding over HTTP", draft-ietf-
https-09 (work in progress), April 2017. tokbind-https-12 (work in progress), January 2018.
[I-D.ietf-tokbind-negotiation] [I-D.ietf-tokbind-negotiation]
Popov, A., Nystrom, M., Balfanz, D., and A. Langley, Popov, A., Nystrom, M., Balfanz, D., and A. Langley,
"Transport Layer Security (TLS) Extension for Token "Transport Layer Security (TLS) Extension for Token
Binding Protocol Negotiation", draft-ietf-tokbind- Binding Protocol Negotiation", draft-ietf-tokbind-
negotiation-08 (work in progress), April 2017. negotiation-10 (work in progress), October 2017.
[I-D.ietf-tokbind-protocol] [I-D.ietf-tokbind-protocol]
Popov, A., Nystrom, M., Balfanz, D., Langley, A., and J. Popov, A., Nystrom, M., Balfanz, D., Langley, A., and J.
Hodges, "The Token Binding Protocol Version 1.0", draft- Hodges, "The Token Binding Protocol Version 1.0", draft-
ietf-tokbind-protocol-14 (work in progress), April 2017. ietf-tokbind-protocol-16 (work in progress), October 2017.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data [RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data
Encodings", RFC 4648, DOI 10.17487/RFC4648, October 2006, Encodings", RFC 4648, DOI 10.17487/RFC4648, October 2006,
<http://www.rfc-editor.org/info/rfc4648>. <https://www.rfc-editor.org/info/rfc4648>.
[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, Specifications: ABNF", STD 68, RFC 5234,
DOI 10.17487/RFC5234, January 2008, DOI 10.17487/RFC5234, January 2008,
<http://www.rfc-editor.org/info/rfc5234>. <https://www.rfc-editor.org/info/rfc5234>.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, (TLS) Protocol Version 1.2", RFC 5246,
DOI 10.17487/RFC5246, August 2008, DOI 10.17487/RFC5246, August 2008,
<http://www.rfc-editor.org/info/rfc5246>. <https://www.rfc-editor.org/info/rfc5246>.
[RFC5705] Rescorla, E., "Keying Material Exporters for Transport [RFC5705] Rescorla, E., "Keying Material Exporters for Transport
Layer Security (TLS)", RFC 5705, DOI 10.17487/RFC5705, Layer Security (TLS)", RFC 5705, DOI 10.17487/RFC5705,
March 2010, <http://www.rfc-editor.org/info/rfc5705>. March 2010, <https://www.rfc-editor.org/info/rfc5705>.
[RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer [RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
Protocol (HTTP/1.1): Message Syntax and Routing", Protocol (HTTP/1.1): Message Syntax and Routing",
RFC 7230, DOI 10.17487/RFC7230, June 2014, RFC 7230, DOI 10.17487/RFC7230, June 2014,
<http://www.rfc-editor.org/info/rfc7230>. <https://www.rfc-editor.org/info/rfc7230>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
5.2. Informative References 5.2. Informative References
[fetch-spec] [fetch-spec]
WhatWG, "Fetch", Living Standard , WhatWG, "Fetch", Living Standard ,
<https://fetch.spec.whatwg.org/>. <https://fetch.spec.whatwg.org/>.
[RFC3864] Klyne, G., Nottingham, M., and J. Mogul, "Registration [RFC3864] Klyne, G., Nottingham, M., and J. Mogul, "Registration
Procedures for Message Header Fields", BCP 90, RFC 3864, Procedures for Message Header Fields", BCP 90, RFC 3864,
DOI 10.17487/RFC3864, September 2004, DOI 10.17487/RFC3864, September 2004,
<http://www.rfc-editor.org/info/rfc3864>. <https://www.rfc-editor.org/info/rfc3864>.
Appendix A. Acknowledgements Appendix A. Acknowledgements
The author would like to thank the following people for their various The author would like to thank the following people for their various
contributions to the specification: Vinod Anupam, Dirk Balfanz, John contributions to the specification: Vinod Anupam, Dirk Balfanz, John
Bradley, Nick Harper, Jeff Hodges, Subodh Iyengar, Leif Johansson, Bradley, William Denniss, Nick Harper, Jeff Hodges, Subodh Iyengar,
Yoav Nir, Andrei Popov, Eric Rescorla, Piotr Sikora, Martin Thomson, Leif Johansson, Yoav Nir, Andrei Popov, Eric Rescorla, Piotr Sikora,
Hans Zandbelt and others (please let me know, if you've contributed Martin Thomson, Hans Zandbelt and others (please let me know, if
and I've forgotten you). you've contributed and I've forgotten you).
Appendix B. Document History Appendix B. Document History
[[ to be removed by the RFC Editor before publication as an RFC ]] [[ to be removed by the RFC Editor before publication as an RFC ]]
draft-ietf-tokbind-ttrp-02
o Add to the Acknowledgements.
o Update references for Token Binding negotiation, protocol, and
https.
o Use the boilerplate from RFC 8174.
o Reformat the "HTTP Header Fields and Processing Rules" section to
make the header names more prominent and move the encoding
definitions earlier.
draft-ietf-tokbind-ttrp-01 draft-ietf-tokbind-ttrp-01
o Prefix the header names with "Sec-" so that they are denoted as o Prefix the header names with "Sec-" so that they are denoted as
forbidden header names by Fetch https://fetch.spec.whatwg.org/ forbidden header names by Fetch https://fetch.spec.whatwg.org/
o Removed potentially confusing sentence from Security o Removed potentially confusing sentence from Security
Considerations per Considerations per
https://mailarchive.ietf.org/arch/msg/unbearable/ https://mailarchive.ietf.org/arch/msg/unbearable/
O0IpppyyEqMrQjEkyEi8p8CeBGA O0IpppyyEqMrQjEkyEi8p8CeBGA
 End of changes. 31 change blocks. 
57 lines changed or deleted 90 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/