Translator specification approach
draft-miyata-v6ops-trans-approach-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Hiroshi Miyata | ||
| Last updated | 2008-05-14 | ||
| 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
IPv4 address is estimated to run out shortly. So as [I-D.durand-v6ops-natv4v6v4] stated, we have to consider IPv6 only node for smooth transition. On the other hand, IETF have deprecated the NAT-PT with some reasons. And now we need to seek alternative solutions. Before talking specific technology, we need to consider overall strategy for translation technology.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)