IPv6 Campus Transition Scenario Description and Analysis
draft-ietf-v6ops-campus-transition-01
| Document | Type |
Expired Internet-Draft
(v6ops WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Tim Chown | ||
| Last updated | 2024-08-05 (Latest revision 2007-03-28) | ||
| Replaces | draft-chown-v6ops-campus-transition | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Dead WG Document | |
| 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
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 (and probably for some time) alongside IPv4. This analysis identifies the available components for IPv6 transition, while validating the applicability of the IPv6 Enterprise Network Scenarios informational text. It focuses on the network and associated service elements of the transition, rather than the application elements.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)