Planning for Protocol Adoption and Subsequent Transitions
RFC 8170
Revision differences
Document history
Date | By | Action |
---|---|---|
2017-05-17
|
(System) | Received changes through RFC Editor sync (created alias RFC 8170, changed abstract to 'Over the many years since the introduction of the Internet Protocol, … Received changes through RFC Editor sync (created alias RFC 8170, changed abstract to 'Over the many years since the introduction of the Internet Protocol, we have seen a number of transitions throughout the protocol stack, such as deploying a new protocol, or updating or replacing an existing protocol. Many protocols and technologies were not designed to enable smooth transition to alternatives or to easily deploy extensions; 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 it also summarizes what makes for a good transition plan.', changed standardization level to Informational, changed state to RFC, added RFC published event at 2017-05-17, changed IAB state to Published RFC) |
2017-05-17
|
(System) | RFC published |