TLS Proxy Best Practice
draft-wang-opsec-tls-proxy-bp-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Eric Wang , Andrew Ossipov , Roelof DuToit | ||
Last updated | 2020-12-06 (Latest revision 2020-06-04) | ||
Replaces | draft-wang-tls-proxy-best-practice | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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
Andrew Ossipov
Roelof DuToit
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)