Issues with Dual Stack IPv6 on by Default
draft-ietf-v6ops-v6onbydefault-03
| Document | Type | Expired Internet-Draft (v6ops WG) | |
|---|---|---|---|
| Authors | Sebastien Roy , Alain Durand , James Paugh | ||
| Last updated | 2015-10-14 (latest revision 2004-07-20) | ||
| Stream | IETF | ||
| Intended RFC status | Informational | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | David Kessens | ||
| Send notices to | kurtis@kurtis.pp.se | ||
https://www.ietf.org/archive/id/draft-ietf-v6ops-v6onbydefault-03.txt
Abstract
This document discusses problems that can occur when dual stack nodes that have IPv6 enabled by default are deployed in IPv4 or mixed IPv4 and IPv6 environments. The problems include application connection delays, poor connectivity, and network insecurity. The purpose of this memo is to raise awareness of these problems so that they can be fixed or worked around, not to try to specify whether IPv6 should be enabled by default or not.
Authors
Sebastien Roy
(Sebastien.Roy@Eng.Sun.COM)
Alain Durand
(Alain.Durand@sun.com)
James Paugh
(james.paugh@eng.sun.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)