Experiences from IPv6-Only Networks with Transition Technologies in the WIDE Camp Autumn 2012
draft-hazeyama-widecamp-ipv6-only-experience-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Hiroaki Hazeyama , Ruri Hiromi , Tomohiro Ishihara , Osamu Nakamura | ||
| Last updated | 2013-04-06 (Latest revision 2012-10-03) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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 reports and discusses issues on IPv6 only networks and IPv4/IPv6 transition technologies through our experiences on the 3rd experiment on the WIDE camp. The 3rd experiment was held from September 3rd to September 6th, 2012. As well as past two experiments, we conducted face to face interview to participants for grasping IPv6 capability on users' devices, OSes, and applications. In addition to this, we explored solutions to mitigate timeout / fallback problems of IPv4/IPv6 dual stack clients on an IPv6 only network that is composed of DHCP6 and DNS64/NAT64.
Authors
Hiroaki Hazeyama
Ruri Hiromi
Tomohiro Ishihara
Osamu Nakamura
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)