Some Design Choices for IPv6 Networks
draft-ietf-v6ops-design-choices-09
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Philip Matthews , Victor Kuarsingh | ||
| Last updated | 2016-04-21 (Latest revision 2015-10-19) | ||
| Replaces | draft-matthews-v6ops-design-guidelines | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | Fred Baker | ||
| Shepherd write-up | Show Last changed 2015-04-06 | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | draft-ietf-v6ops-design-choices.all@tools.ietf.org |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document presents advice on certain routing-related design choices that arise when designing IPv6 networks (both dual-stack and IPv6-only). The intended audience is someone designing an IPv6 network who is knowledgeable about best current practices around IPv4 network design, and wishes to learn the corresponding practices for IPv6.
Authors
Philip Matthews
Victor Kuarsingh
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)