Skip to main content

Requirements for IPv6 Routers

Document Type Expired Internet-Draft (v6ops WG)
Expired & archived
Authors Zaid Ali Kahn , John Jason Brzozowski , Russ White
Last updated 2018-11-27 (Latest revision 2018-05-26)
Replaces draft-ali-ipv6rtr-reqs, draft-v6ops-ipv6rtr-reqs
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Additional resources Mailing list discussion
Stream WG state 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:


The Internet is not one network, but rather a collection of networks. The interconnected nature of these networks, and the nature of the interconnected systems that make up these networks, is often more fragile than it appears. Perhaps "robust but fragile" is an overstatement, but the actions of each vendor, implementor, and operator in such an interconnected environment can have a major impact on the stability of the overall Internet (as a system). The widespread adoption of IPv6 could, particularly, disrupt network operations, in a way that impacts the entire system. This time of transition is an opportune time to take stock of lessons learned through the operation of large-scale networks on IPv4, and consider how to apply these lessons to IPv6. This document provides an overview of the design and architectural decisions that attend IPv6 deployment, and a set of IPv6 requirements for routers, switches, and middleboxes deployed in IPv6 networks. The hope of the editors and contributors is to provide the necessary background to guide equipment manufacturers, protocol implementors, and network operators in effective IPv6 deployment.


Zaid Ali Kahn
John Jason Brzozowski
Russ White

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