Virtual Private Network (VPN) traffic leakages in dual-stack hosts/ networks
draft-gont-opsec-vpn-leakages-00

Document Type Replaced Internet-Draft (individual)
Last updated 2013-01-14 (latest revision 2012-10-15)
Replaced by draft-ietf-opsec-vpn-leakages
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-opsec-vpn-leakages
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-gont-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

Fernando Gont (fgont@si6networks.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)