Designing for Transition
draft-thaler-transition-principles-00

Document Type Replaced Internet-Draft (individual)
Last updated 2015-10-05
Replaced by draft-iab-protocol-transitions
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-iab-protocol-transitions
Telechat date
Responsible AD (None)
Send notices to (None)

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-thaler-transition-principles-00.txt

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

Dave Thaler (dthaler@microsoft.com)

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