Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Planning for Protocol Adoption and Subsequent Transitions (RFC8170)

IP.com Disclosure Number: IPCOM000250027D
Original Publication Date: 2017-May-01
Included in the Prior Art Database: 2017-May-18
Document File: 44 page(s) / 55K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

D. Thaler: AUTHOR [+2]

Abstract

A "transition" is the process or period of changing from one state or condition to another. There are several types of such transitions, including both technical transitions (e.g., changing protocols or deploying an extension) and organizational transitions (e.g., changing what organization manages a web site). This document focuses solely on technical transitions, although some principles might apply to other types as well.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 5% of the total text.

Internet Architecture Board (IAB)                         D. Thaler, Ed. Request for Comments: 8170                                      May 2017 Category: Informational ISSN: 2070-1721

        Planning for Protocol Adoption and Subsequent Transitions

Abstract

   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.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This document is a product of the Internet Architecture Board (IAB)    and represents information that the IAB has deemed valuable to    provide for permanent record.  It represents the consensus of the    Internet Architecture Board (IAB).  Documents approved for    publication by the IAB are not a candidate for any level of Internet    Standard; see Section 2 of RFC 7841.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc8170.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.

 Thaler                        Informational                     [Page 1]
 RFC 8170                 Planning for Transition                May 2017

 Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2

   2.  Extensibility . . . . . . . . . . . . . . . . . . . . . . . .   4

   3.  Transition vs. Coexistence  . . . . . . . . . . . . . . . . .   5

   4.  Translation/Adaptation Location . . . . . . . . . . . . . . .   6

   5.  Transition Plans  . . . . . . . . . . . . . . . . . . . . . .   7

     5.1.  Understanding of Existing Deployment  . . . . . . . . . .   7

     5.2.  Explanation of Incentives . . . . . . . . . . . . . . . .   7

     5.3.  Description of Phases and...