draft-ietf-httpbis-client-cert-field-02.txt   draft-ietf-httpbis-client-cert-field-latest.txt 
HTTP Working Group B. Campbell HTTP Working Group B. Campbell
Internet-Draft Ping Identity Internet-Draft Ping Identity
Intended status: Informational M. Bishop, Ed. Intended status: Informational M. Bishop, Ed.
Expires: November 26, 2022 Akamai Expires: January 3, 2023 Akamai
May 25, 2022 July 2, 2022
Client-Cert HTTP Header Field Client-Cert HTTP Header Field
draft-ietf-httpbis-client-cert-field-02 draft-ietf-httpbis-client-cert-field-latest
Abstract Abstract
This document defines HTTP extension header fields that allow a TLS This document defines HTTP extension header fields that allow a TLS
terminating reverse proxy to convey the client certificate terminating reverse proxy to convey the client certificate
information of a mutually-authenticated TLS connection to the origin information of a mutually-authenticated TLS connection to the origin
server in a common and predictable manner. server in a common and predictable manner.
About This Document About This Document
skipping to change at page 2, line 4 skipping to change at page 2, line 4
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 November 26, 2022. This Internet-Draft will expire on January 3, 2023.
Copyright Notice Copyright Notice
Copyright (c) 2022 IETF Trust and the persons identified as the Copyright (c) 2022 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
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
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Notation and Conventions . . . . . . . . . . 4
1.2. Terminology and Applicability . . . . . . . . . . . . . . 4
2. HTTP Header Fields and Processing Rules . . . . . . . . . . . 5
2.1. Encoding . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2. Client-Cert HTTP Header Field . . . . . . . . . . . . . . 5
2.3. Client-Cert-Chain HTTP Header Field . . . . . . . . . . . 6
2.4. Processing Rules . . . . . . . . . . . . . . . . . . . . 6
3. Deployment Considerations . . . . . . . . . . . . . . . . . . 8
3.1. Header Field Compression . . . . . . . . . . . . . . . . 8
3.2. Header Block Size . . . . . . . . . . . . . . . . . . . . 8
3.3. TLS Session Resumption . . . . . . . . . . . . . . . . . 8
4. Security Considerations . . . . . . . . . . . . . . . . . . . 9
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
5.1. HTTP Field Name Registrations . . . . . . . . . . . . . . 10
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
6.1. Normative References . . . . . . . . . . . . . . . . . . 10
6.2. Informative References . . . . . . . . . . . . . . . . . 11
Appendix A. Example . . . . . . . . . . . . . . . . . . . . . . 12
Appendix B. Considerations Considered . . . . . . . . . . . . . 14
B.1. Field Injection . . . . . . . . . . . . . . . . . . . . . 14
B.2. The Forwarded HTTP Extension . . . . . . . . . . . . . . 15
B.3. The Whole Certificate and Certificate Chain . . . . . . . 15
Appendix C. Acknowledgements . . . . . . . . . . . . . . . . . . 16
Appendix D. Document History . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18
1. Introduction 1. Introduction
A fairly common deployment pattern for HTTPS applications is to have A fairly common deployment pattern for HTTPS applications is to have
the origin HTTP application servers sit behind a reverse proxy that the origin HTTP application servers sit behind a reverse proxy that
terminates TLS connections from clients. The proxy is accessible to terminates TLS connections from clients. The proxy is accessible to
the internet and dispatches client requests to the appropriate origin the internet and dispatches client requests to the appropriate origin
server within a private or protected network. The origin servers are server within a private or protected network. The origin servers are
not directly accessible by clients and are only reachable through the not directly accessible by clients and are only reachable through the
reverse proxy. The backend details of this type of deployment are reverse proxy. The backend details of this type of deployment are
typically opaque to clients who make requests to the proxy server and typically opaque to clients who make requests to the proxy server and
skipping to change at page 11, line 17 skipping to change at page 10, line 21
<https://www.rfc-editor.org/info/rfc8941>. <https://www.rfc-editor.org/info/rfc8941>.
6.2. Informative References 6.2. Informative References
[I-D.ietf-httpbis-semantics] [I-D.ietf-httpbis-semantics]
Fielding, R. T., Nottingham, M., and J. Reschke, "HTTP Fielding, R. T., Nottingham, M., and J. Reschke, "HTTP
Semantics", draft-ietf-httpbis-semantics-19 (work in Semantics", draft-ietf-httpbis-semantics-19 (work in
progress), September 2021. progress), September 2021.
[I-D.ietf-quic-http] [I-D.ietf-quic-http]
Bishop, M., "Hypertext Transfer Protocol Version 3 Bishop, M., "HTTP/3", draft-ietf-quic-http-34 (work in
(HTTP/3)", draft-ietf-quic-http-34 (work in progress), progress), February 2021.
February 2021.
[I-D.ietf-quic-qpack] [I-D.ietf-quic-qpack]
Krasic, C. '., Bishop, M., and A. Frindell, "QPACK: Header Krasic, C. '., Bishop, M., and A. Frindell, "QPACK: Field
Compression for HTTP/3", draft-ietf-quic-qpack-21 (work in Compression for HTTP/3", draft-ietf-quic-qpack-21 (work in
progress), February 2021. progress), February 2021.
[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,
<https://www.rfc-editor.org/info/rfc5246>. <https://www.rfc-editor.org/info/rfc5246>.
[RFC6585] Nottingham, M. and R. Fielding, "Additional HTTP Status [RFC6585] Nottingham, M. and R. Fielding, "Additional HTTP Status
Codes", RFC 6585, DOI 10.17487/RFC6585, April 2012, Codes", RFC 6585, DOI 10.17487/RFC6585, April 2012,
 End of changes. 6 change blocks. 
37 lines changed or deleted 7 lines changed or added

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