IPv6 Campus Transition Scenario Description and Analysis
draft-chown-v6ops-campus-transition-03
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Tim Chown | ||
| Last updated | 2006-10-16 (Latest revision 2006-06-29) | ||
| Replaced by | draft-ietf-v6ops-campus-transition | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-v6ops-campus-transition | |
| 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
In this document we consider and analyse the specific scenario of IPv6 transition and deployment in a large department of a university campus network. The department is large enough to operate its own instances of all the conventional university services including (for example) web, DNS, email, filestore, interactive logins, and remote and wireless access. The scenario is a dual-stack one, i.e. transition to IPv6 means deploying IPv6 in the first instance alongside IPv4. This analysis identifies the available (and still missing) components for IPv6 transition, while validating the applicability of the IPv6 Enterprise Network Scenarios informational text.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)