Routing-Related Design Choices for IPv6 Networks
draft-ietf-v6ops-design-choices-12

Document Type Expired Internet-Draft (v6ops WG)
Last updated 2017-05-17 (latest revision 2016-11-13)
Replaces draft-matthews-v6ops-design-guidelines
Stream IETF
Intended RFC status Informational
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state WG Document (wg milestone: Jul 2017 - Describe routing cho... )
Document shepherd Fred Baker
Shepherd write-up Show (last changed 2015-04-06)
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
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 can be found at
https://www.ietf.org/archive/id/draft-ietf-v6ops-design-choices-12.txt

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 (philip_matthews@magma.ca)
Victor Kuarsingh (victor@jvknet.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)