Guide to Mapping IPv4 to IPv6 Subnets
draft-schild-v6ops-guide-v4mapping-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Christian Schild | ||
| Last updated | 2004-01-29 | ||
| 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 is intended to be a guide for network administrators of enterprise sized sites that employ the Internet Protocol Version 4 (IPv4) and who would like to introduce the Internet Protocol Version 6 (IPv6) dual-stack. It applies to scenarios where IPv4 subnets must be mapped to IPv6 subnets for management purposes while keeping the option to create IPv6 subnets in parallel and independently in the future with almost no restrictions; it is not meant to be applied to scenarios where a native IPv6 address plan can be created easily and without the need to map IPv4 subnets.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)