Virtual Private Network (VPN) traffic leakages in dual-stack hosts/ networks
draft-ietf-opsec-vpn-leakages-00
| The information below is for an old version of the document | |||
|---|---|---|---|
| Document | Type | Expired Internet-Draft (opsec WG) | |
| Last updated | 2013-06-15 (latest revision 2012-12-12) | ||
| Replaces | draft-gont-opsec-vpn-leakages | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | WG Document Jul 2013 | |
| Document shepherd | None | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-opsec-vpn-leakages-00.txt
Abstract
The subtle way in which the IPv6 and IPv4 protocols co-exist in typical networks, together with the lack of proper IPv6 support in popular Virtual Private Network (VPN) products, may inadvertently result in VPN traffic leaks. That is, traffic meant to be transferred over a VPN connection may leak out of such connection and be transferred in the clear on the local network. This document discusses some scenarios in which such VPN leakages may occur, either as a side effect of enabling IPv6 on a local network, or as a result of a deliberate attack from a local attacker. Additionally, it discusses possible mitigations for the aforementioned issue.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)