A workaround for termination of IPv4 network services
draft-hiromi-sunset4-termination-ipv4-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Hiroaki Hazeyama , Atsushi Onoe , Osamu Nakamura | ||
| Last updated | 2013-09-12 (Latest revision 2013-03-11) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | WG state | (None) | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| 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
After sun-setting of IPv4, many devices will be connected to IPv6 single stack network. In this document we describe a workaround for IPv6 enabled network configuration. At this moment, the condition of IPv6 adoption on the consumer devices such as PC, tablet, mobile terminal and entertainment device are various. For example, some devices are fully support IPv6 client but some are not. It is very hard to provide IPv6 network service with these various conditioned devices. To solve this problem, we tried to verify some configurations to connect these devices into IPv6 enabled consumer network for termination of IPv4 network services.
Authors
Hiroaki Hazeyama
Atsushi Onoe
Osamu Nakamura
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)