draft-ietf-tokbind-ttrp-03.txt   draft-ietf-tokbind-ttrp-04.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 February 25, 2018 Intended status: Standards Track June 6, 2018
Expires: August 29, 2018 Expires: December 8, 2018
HTTPS Token Binding with TLS Terminating Reverse Proxies HTTPS Token Binding with TLS Terminating Reverse Proxies
draft-ietf-tokbind-ttrp-03 draft-ietf-tokbind-ttrp-04
Abstract Abstract
This document defines HTTP header fields that enable a TLS This document defines HTTP header fields that enable a TLS
terminating reverse proxy to convey information to a backend server terminating reverse proxy to convey information to a backend server
about the validated Token Binding Message received from a client, about the validated Token Binding Message received from a client,
which enables that backend server to bind, or verify the binding of, which 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.
This facilitates the reverse proxy and backend server functioning
together as though they are a single logical server side deployment
of HTTPS Token Binding.
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 https://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 August 29, 2018. This Internet-Draft will expire on December 8, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 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
(https://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
skipping to change at page 2, line 10 skipping to change at page 2, line 13
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. Encoding . . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Encoding . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1.1. Token Binding ID . . . . . . . . . . . . . . . . . . 4 2.1.1. Token Binding ID . . . . . . . . . . . . . . . . . . 4
2.1.2. Token Binding Type . . . . . . . . . . . . . . . . . 4 2.1.2. Token Binding Type . . . . . . . . . . . . . . . . . 4
2.2. Token Binding ID HTTP Header Fields . . . . . . . . . . . 4 2.2. Token Binding ID HTTP Header Fields . . . . . . . . . . . 4
2.3. Processing Rules . . . . . . . . . . . . . . . . . . . . 5 2.3. Processing Rules . . . . . . . . . . . . . . . . . . . . 5
2.4. Examples . . . . . . . . . . . . . . . . . . . . . . . . 6 2.4. Examples . . . . . . . . . . . . . . . . . . . . . . . . 6
2.4.1. Provided Token Binding ID . . . . . . . . . . . . . . 6 2.4.1. Provided Token Binding ID . . . . . . . . . . . . . . 6
2.4.2. Provided and Referred Token Binding IDs . . . . . . . 7 2.4.2. Provided and Referred Token Binding IDs . . . . . . . 7
3. Security Considerations . . . . . . . . . . . . . . . . . . . 8 2.4.3. Provided and Other Token Binding IDs . . . . . . . . 8
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 3. Security Considerations . . . . . . . . . . . . . . . . . . . 9
4.1. HTTP Message Header Field Names Registration . . . . . . 9 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 4.1. HTTP Message Header Field Names Registration . . . . . . 10
5.1. Normative References . . . . . . . . . . . . . . . . . . 9 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.2. Informative References . . . . . . . . . . . . . . . . . 10 5.1. Normative References . . . . . . . . . . . . . . . . . . 10
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 10 5.2. Informative References . . . . . . . . . . . . . . . . . 11
Appendix B. Document History . . . . . . . . . . . . . . . . . . 11 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 11
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 12 Appendix B. Document History . . . . . . . . . . . . . . . . . . 12
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 13
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 4, line 25 skipping to change at page 4, line 29
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 ABNF Figure 1: Encoded Token Binding ID ABNF
2.1.2. Token Binding Type 2.1.2. Token Binding Type
A Token Binding type can be represented as an A Token Binding type value (a single byte) can be represented as an
"EncodedTokenBindingType", which is the base16 encoding (Section 8 of "EncodedTokenBindingType", which is a case-insensitive hex (Section 8
[RFC4648]) of the single TokenBindingType byte. ABNF [RFC5234] of [RFC4648]) encoding. The ABNF definition is shown in Figure 2
syntax for "EncodedTokenBindingType" is shown in Figure 2 below. below.
EncodedTokenBindingType = 1*2( DIGIT / EncodedTokenBindingType = 1*2HEXDIG
"A" / "B" / "C" / "D" / "E" / "F" /
"a" / "b" / "c" / "d" / "e" / "f" ) HEXDIG = <Defined in Section B.1 of [RFC5234]>
Figure 2: Encoded Token Binding Type ABNF Figure 2: Encoded Token Binding Type ABNF
2.2. Token Binding ID HTTP Header Fields 2.2. Token Binding ID HTTP Header Fields
The Token Binding Protocol [I-D.ietf-tokbind-protocol] recommends The Token Binding Protocol [I-D.ietf-tokbind-protocol] recommends
that implementations make Token Binding IDs available to the that implementations make Token Binding IDs available to the
application as opaque byte sequences, enabling those applications to application as opaque byte sequences, enabling those applications to
use the Token Binding IDs when generating and verifying bound tokens. use the Token Binding IDs when generating and verifying bound tokens.
In the context of a TLS terminating reverse proxy (TTRP) deployment, In the context of a TLS terminating reverse proxy (TTRP) deployment,
skipping to change at page 6, line 42 skipping to change at page 6, line 49
examples for display and formatting purposes only. examples for display and formatting purposes only.
2.4.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 that the client uses
the server. with the server.
Sec-Token-Binding: AIkAAgBBQKzyIrmcY_YCtHVoSHBut69vrGfFdy1_YKTZfFJv Sec-Token-Binding: AIkAAgBBQKzyIrmcY_YCtHVoSHBut69vrGfFdy1_YKTZfFJv
6BjrZsKD9b9FRzSBxDs1twTqnAS71M1RBumuihhI9xqxXKkAQEtxe4jeUJU0WezxlQ 6BjrZsKD9b9FRzSBxDs1twTqnAS71M1RBumuihhI9xqxXKkAQEtxe4jeUJU0WezxlQ
XWVSBFeHxFMdXRBIH_LKOSAuSMOJ0XEw1Q8DE248qkOiRKzw3KdSNYukYEPmO21bQi XWVSBFeHxFMdXRBIH_LKOSAuSMOJ0XEw1Q8DE248qkOiRKzw3KdSNYukYEPmO21bQi
3YYAAA 3YYAAA
Figure 3: Header in HTTP Request to TTRP Figure 3: Header in HTTP Request to TTRP
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-
skipping to change at page 7, line 23 skipping to change at page 7, line 30
Figure 4: Header in HTTP Request to Backend Server Figure 4: Header in HTTP Request to Backend Server
2.4.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 that the client uses
the server as well as the referred Token Binding that it uses with a with the server as well as the referred Token Binding that it uses
different server. with a different server.
Sec-Token-Binding: ARIAAgBBQCfsI1D1sTq5mvT_2H_dihNIvuHJCHGjHPJchPav Sec-Token-Binding: ARIAAgBBQCfsI1D1sTq5mvT_2H_dihNIvuHJCHGjHPJchPav
NbGrOo26-2JgT_IsbvZd4daDFbirYBIwJ-TK1rh8FzrC-psAQMyYIqXj7djGPev1dk NbGrOo26-2JgT_IsbvZd4daDFbirYBIwJ-TK1rh8FzrC-psAQMyYIqXj7djGPev1dk
jV9XxLYGCyqOrBVEtBHrMUCeo22ymLg3OiFcl_fmOPxJbjxI6lKcF0lyfy-dSQmPIe jV9XxLYGCyqOrBVEtBHrMUCeo22ymLg3OiFcl_fmOPxJbjxI6lKcF0lyfy-dSQmPIe
zQ0AAAECAEFArPIiuZxj9gK0dWhIcG63r2-sZ8V3LX9gpNl8Um_oGOtmwoP1v0VHNI zQ0AAAECAEFArPIiuZxj9gK0dWhIcG63r2-sZ8V3LX9gpNl8Um_oGOtmwoP1v0VHNI
HEOzW3BOqcBLvUzVEG6a6KGEj3GrFcqQBAHQm0pzgUTXKLRamuKE1pmmP9I3UBVpoe HEOzW3BOqcBLvUzVEG6a6KGEj3GrFcqQBAHQm0pzgUTXKLRamuKE1pmmP9I3UBVpoe
1DBCe9H2l1VPpsImakUa6crAqZ-0CGBmji7bYzQogpKcyxTTFk5zdwAA 1DBCe9H2l1VPpsImakUa6crAqZ-0CGBmji7bYzQogpKcyxTTFk5zdwAA
Figure 5: Header in HTTP Request to TTRP Figure 5: Header in HTTP Request to TTRP
skipping to change at page 8, line 5 skipping to change at page 8, line 12
the provided and referred Token Binding IDs respectively, to the the provided and referred Token Binding IDs respectively, to the
request that is dispatched to the backend server. request that is dispatched to the backend server.
Sec-Provided-Token-Binding-ID: AgBBQCfsI1D1sTq5mvT_2H_dihNIvuHJCHGj Sec-Provided-Token-Binding-ID: AgBBQCfsI1D1sTq5mvT_2H_dihNIvuHJCHGj
HPJchPavNbGrOo26-2JgT_IsbvZd4daDFbirYBIwJ-TK1rh8FzrC-ps HPJchPavNbGrOo26-2JgT_IsbvZd4daDFbirYBIwJ-TK1rh8FzrC-ps
Sec-Referred-Token-Binding-ID: AgBBQKzyIrmcY_YCtHVoSHBut69vrGfFdy1_ Sec-Referred-Token-Binding-ID: AgBBQKzyIrmcY_YCtHVoSHBut69vrGfFdy1_
YKTZfFJv6BjrZsKD9b9FRzSBxDs1twTqnAS71M1RBumuihhI9xqxXKk YKTZfFJv6BjrZsKD9b9FRzSBxDs1twTqnAS71M1RBumuihhI9xqxXKk
Figure 6: Headers in HTTP Request to Backend Server Figure 6: Headers in HTTP Request to Backend Server
2.4.3. Provided and Other Token Binding IDs
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
of Token Binding has been negotiated (The base64url-encoded
representation of the exported keying material, which can be used to
validate the Token Binding Message, for that connection is
"Zr_1DESCcDoaltcZCK613UrEWHRf2B3w9i3bwcxpacc"). The encoded Token
Binding Message has the provided Token Binding and two other Token
Bindings.
Sec-Token-Binding: AZsAAgBBQA35hcCjI5GEHLLAZ0i2l2ZvQe-bSPAP7jovkZJM
4wYHgmmXNd1aRpnQmXK9ghUmrdtS6p_e2uSlMXIVKOIwgysAQJ-TKyVGF37XUXMy79
ybwJyPpfCG9Iq6fdIxLX_yJn-L__Z3p_WIL3g17K0OH3XZmJS3qZNNEVu_8HmPN-d9
hGMAAE0CAEFAR68GbdIQyrHqkorJF0sekYJvf8iV03obGxbaWbqAEJetsYxprB6c3M
x5KDHBGZjsFbeFW5Xec_EaxX0Hw3RmJwBA-Fu22kokRbB7G0D0g6_sdCHTbczSCmnm
6rqP1x7kRIIj_kJNCCWcwMMFzbsBTXcm5fJrRdBTcsqiiqYD6aJ1SgAACwIAQUCDqt
6m63By8b1lvhN-n9OsQThoLomzKpMicSZGwR166jplhbkjrFsHzdNqzLFFEhCT9s0p
XrcbpOHsZnpRSkmhAEBfOwxjK3Y9EOeMrqjo0IUhmurW2EgtSRBjDwc0r-rDT231Zv
_f1oePB8Pkd1kgAtgKX5EDiemfo1YER3_I2cv3AAA
Figure 7: Header in HTTP Request to TTRP
After validating the Token Binding Message, the TTRP removes the
"Sec-Token-Binding" header and adds the following "Sec-Provided-
Token-Binding-ID" and "Sec-Other-Token-Binding-ID" headers to the
request that is dispatched to the backend server.
Sec-Provided-Token-Binding-ID: AgBBQA35hcCjI5GEHLLAZ0i2l2ZvQe-bSPAP
7jovkZJM4wYHgmmXNd1aRpnQmXK9ghUmrdtS6p_e2uSlMXIVKOIwgys
Sec-Other-Token-Binding-ID: 4d.AgBBQEevBm3SEMqx6pKKyRdLHpGCb3_IldN6
GxsW2lm6gBCXrbGMaawenNzMeSgxwRmY7BW3hVuV3nPxGsV9B8N0Zic,b.AgBBQIO
q3qbrcHLxvWW-E36f06xBOGguibMqkyJxJkbBHXrqOmWFuSOsWwfN02rMsUUSEJP2
zSletxuk4exmelFKSaE
Figure 8: Headers in HTTP Request to Backend Server
3. Security Considerations 3. Security Considerations
The headers described herein enable a reverse proxy and backend The headers described herein enable a reverse proxy and backend
server to function together as though they are single logical server server to function together as though they are a single logical
side deployment of HTTPS Token Binding. Use of the headers outside server side deployment of HTTPS Token Binding. Use of the headers
that intended use case, however, may undermine the protections outside that intended use case, however, may undermine the
afforded by Token Binding. Therefore steps MUST be taken to prevent protections afforded by Token Binding. Therefore steps MUST be taken
unintended use, both in sending the headers and in relying on their to prevent unintended use, both in sending the headers and in relying
value. on their value.
Producing and consuming the headers SHOULD be a configurable option, Producing and consuming the headers SHOULD be a configurable option,
respectively, in a reverse proxy and backend server (or individual respectively, in a reverse proxy and backend server (or individual
application in that server). The default configuration for both application in that server). The default configuration for both
should be to not use the headers thus requiring an "opt-in" to the should be to not use the headers thus requiring an "opt-in" to the
functionality. functionality.
Backend servers MUST only accept the headers from trusted reverse Backend servers MUST only accept the headers from trusted reverse
proxies. And reverse proxies MUST sanitize the incoming request proxies. And reverse proxies MUST sanitize the incoming request
before forwarding it on by removing or overwriting any existing before forwarding it on by removing or overwriting any existing
skipping to change at page 10, line 48 skipping to change at page 11, line 48
[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,
<https://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, William Denniss, Nick Harper, Jeff Hodges, Subodh Iyengar, Bradley, William Denniss, Nick Harper, Jeff Hodges, Subodh Iyengar,
Leif Johansson, Michael B. Jones, Yoav Nir, Andrei Popov, Eric Leif Johansson, Michael B. Jones, Yoav Nir, James Manger, Andrei
Rescorla, Piotr Sikora, Martin Thomson, Hans Zandbelt and others Popov, Eric Rescorla, Piotr Sikora, Martin Thomson, and Hans Zandbelt
(please let me know, if 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-04
o Add an example with Sec-Other-Token-Binding-ID.
o Use the HEXDIG core ABNF rule for EncodedTokenBindingType and
mention case-insensitive in the text.
o Minor editorial fixes.
o Add to the Acknowledgements and remove the 'and others' bit.
draft-ietf-tokbind-ttrp-03 draft-ietf-tokbind-ttrp-03
o Add a header to allow for additional token binding types other o Add a header to allow for additional token binding types other
than provided and referred to be conveyed. than provided and referred to be conveyed.
o Reword the Abstract somewhat for (hopefully) improved readability. o Reword the Abstract somewhat for (hopefully) improved readability.
o Minor editorial and formatting updates. o Minor editorial and formatting updates.
draft-ietf-tokbind-ttrp-02 draft-ietf-tokbind-ttrp-02
skipping to change at page 11, line 43 skipping to change at page 13, line 5
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
o Editorial fixes. o Editorial fixes.
draft-ietf-tokbind-ttrp-00
o Initial WG draft from draft-campbell-tokbind-ttrp. o Initial WG draft from draft-campbell-tokbind-ttrp.
draft-campbell-tokbind-ttrp-01 draft-campbell-tokbind-ttrp-01
o Minor editorial fixes. o Minor editorial fixes.
o Add to the Acknowledgements. o Add to the Acknowledgements.
draft-campbell-tokbind-ttrp-00
o Initial draft based on 'consensus to work on the problem' from the o Initial draft based on 'consensus to work on the problem' from the
Seoul meeting [1][2] and reflecting the consensus approach from Seoul meeting [1][2] and reflecting the consensus approach from
discussions at the Chicago meeting [3]. discussions at the Chicago meeting [3].
[1] https://www.ietf.org/proceedings/97/minutes/minutes-97- [1] https://www.ietf.org/proceedings/97/minutes/minutes-97-
tokbind-01.txt (minutes from Seoul) tokbind-01.txt (minutes from Seoul)
[2] https://www.ietf.org/proceedings/97/slides/slides-97-tokbind- [2] https://www.ietf.org/proceedings/97/slides/slides-97-tokbind-
reverse-proxies-00.pdf (slides from Seoul) reverse-proxies-00.pdf (slides from Seoul)
[3] https://mailarchive.ietf.org/arch/msg/ [3] https://mailarchive.ietf.org/arch/msg/
unbearable/_ZHI8y2Vs5WMP8VMRr7zroo_sNU (summary of discussion) unbearable/_ZHI8y2Vs5WMP8VMRr7zroo_sNU (summary of discussion)
 End of changes. 16 change blocks. 
37 lines changed or deleted 88 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/