Impact of TLS 1.3 to Operational Network Security Practices
draft-camwinget-tls-proxy-impact-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Nancy Cam-Winget , Eric Wang , Roman Danyliw , Roelof DuToit | ||
| Last updated | 2019-11-04 | ||
| Replaced by | draft-camwinget-tls-ns-impact | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-camwinget-tls-ns-impact | |
| 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
Network-based security solutions are used by enterprises, the public sector, internet-service providers, and cloud-service providers to both complement and enhance host-based security solutions. As the most widely deployed protocol to secure communication, these network- based security solutions must necessarily interact with TLS. This document describes this interaction for current operational security practices and notes the impact of TLS 1.3 on them.
Authors
Nancy Cam-Winget
Eric Wang
Roman Danyliw
Roelof DuToit
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)