RFC 8170 on Planning for Protocol Adoption and Subsequent Transitions
rfc-editor@rfc-editor.org Wed, 17 May 2017 19:43 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42C7412940B for <ietf-announce@ietfa.amsl.com>; Wed, 17 May 2017 12:43:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iYzcF7hk-tjj for <ietf-announce@ietfa.amsl.com>; Wed, 17 May 2017 12:43:11 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D3EA212711E for <ietf-announce@ietf.org>; Wed, 17 May 2017 12:41:47 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id CD916B80CC6; Wed, 17 May 2017 12:41:42 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8170 on Planning for Protocol Adoption and Subsequent Transitions
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Message-Id: <20170517194142.CD916B80CC6@rfc-editor.org>
Date: Wed, 17 May 2017 12:41:42 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/H6ouLe_ieT7iqDIouoxdstdDirM>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 May 2017 19:43:13 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8170
Title: Planning for Protocol Adoption and
Subsequent Transitions
Author: D. Thaler, Ed.
Status: Informational
Stream: IAB
Date: May 2017
Mailbox: dthaler@microsoft.com
Pages: 22
Characters: 55160
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-iab-protocol-transitions-08.txt
URL: https://www.rfc-editor.org/info/rfc8170
DOI: 10.17487/RFC8170
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.
This document is a product of the Internet Architecture Board.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC