Designing for Transition
draft-thaler-transition-principles-00
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Dave Thaler | ||
Last updated | 2015-10-05 | ||
Replaced by | draft-iab-protocol-transitions | ||
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-iab-protocol-transitions | |
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
Over the many years since the introduction of the Internet Protocol, we have seen a number of transitions, throughout the protocol stack, from one protocol or technology to another. Many protocols and technologies were not designed to enable smooth transition to alternatives or to easily deploy extensions, and thus some transitions, such as the introduction of IPv6, have been difficult. This document attempts to summarize some basic principles to enable future transitions, and also summarizes what makes for a good transition plan.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)