Advisory Guidelines for 6to4 Deployment
draft-carpenter-v6ops-6to4-teredo-advisory-03
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Brian E. Carpenter | ||
| Last updated | 2011-04-05 (Latest revision 2011-03-11) | ||
| Replaced by | draft-ietf-v6ops-6to4-advisory | ||
| 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-6to4-advisory | |
| 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 provides advice to network operators about deployment of the 6to4 technique for automatic tunneling of IPv6 over IPv4. It is principally addressed to Internet Service Providers, including those that do not yet support IPv6, and to Content Providers. The intention of the advice is to minimise both user dissatisfaction and help desk calls.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)