TLS Proxy Best Practice
draft-wang-tls-proxy-best-practice-01
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2020-03-04 | ||
| Replaced by | draft-wang-opsec-tls-proxy-bp | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-wang-opsec-tls-proxy-bp | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-wang-tls-proxy-best-practice-01.txt
Abstract
TLS proxies are widely deployed by organizations to enable security features and apply enterprise policies. This document defines a TLS proxy and discusses a wide range of security requirements to guide TLS proxy implementations.
Authors
Eric Wang
(ejwang@cisco.com)
Andrew Ossipov
(aossipov@cisco.com)
Roelof DuToit
(roelof.dutoit@broadcom.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)