Impact of TLS 1.3 to Operational Network Security Practices
draft-ietf-opsec-ns-impact-04
Document | Type |
Expired Internet-Draft
(opsec WG)
Expired & archived
|
|
---|---|---|---|
Authors | Nancy Cam-Winget , Eric Wang , Roman Danyliw , Roelof DuToit | ||
Last updated | 2021-07-30 (Latest revision 2021-01-26) | ||
Replaces | draft-camwinget-opsec-ns-impact | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | In WG Last Call | |
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
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 TLS is a widely deployed protocol to secure communication, these network- based security solutions must necessarily interact with it. 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.)