IP Traffic Flow Security
draft-hopps-ipsecme-iptfs-01
| Document | Type |
Replaced Internet-Draft
(ipsecme WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Christian Hopps | ||
| Last updated | 2019-12-07 (Latest revision 2019-06-05) | ||
| Replaced by | RFC 9347 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Associated WG milestone |
|
||
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-ipsecme-iptfs | |
| 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
This document describes a mechanism to enhance IPsec traffic flow security by adding traffic flow confidentiality to encrypted IP encapsulated traffic. Traffic flow confidentiality is provided by obscuring the size and frequency of IP traffic using a fixed-sized, constant-send-rate IPsec tunnel. The solution allows for congestion control as well.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)