Re: [arch-d] Call for Comment: <draft-iab-protocol-transitions> (Out With the Old and In With the New: Planning for Protocol Transitions)

"Paul Hoffman" <paul.hoffman@vpnc.org> Sat, 14 January 2017 23:48 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD9BD129E7A; Sat, 14 Jan 2017 15:48:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.5
X-Spam-Level:
X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_05=-0.5] 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 u47utVk0O3fM; Sat, 14 Jan 2017 15:48:33 -0800 (PST)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2511129E76; Sat, 14 Jan 2017 15:48:33 -0800 (PST)
Received: from [10.32.60.28] (50-1-51-163.dsl.dynamic.fusionbroadband.com [50.1.51.163]) (authenticated bits=0) by mail.proper.com (8.15.2/8.14.9) with ESMTPSA id v0ENlcZh060209 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 14 Jan 2017 16:47:38 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 50-1-51-163.dsl.dynamic.fusionbroadband.com [50.1.51.163] claimed to be [10.32.60.28]
From: Paul Hoffman <paul.hoffman@vpnc.org>
To: architecture-discuss@ietf.org, iab@iab.org
Date: Sat, 14 Jan 2017 15:48:31 -0800
Message-ID: <0D528A55-C9C1-413A-8067-31157CDB99DB@vpnc.org>
In-Reply-To: <148357904166.13056.1797751203596240116.idtracker@ietfa.amsl.com>
References: <148357904166.13056.1797751203596240116.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
X-Mailer: MailMate (1.9.6r5319)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/eoLwG03ALNZ6IQ8Lv2nSDWoj13k>
Subject: Re: [arch-d] Call for Comment: <draft-iab-protocol-transitions> (Out With the Old and In With the New: Planning for Protocol Transitions)
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Jan 2017 23:48:35 -0000

On 4 Jan 2017, at 17:17, IAB Executive Administrative Manager wrote:

> This is an announcement of an IETF-wide Call for Comment on
> draft-iab-protocol-transitions-05.

I have read this version of the draft and think it will be a useful RFC. 
Kudos for having the document also cover transitions outside the IETF 
standards process; this document can be useful to developers who have 
created proprietary standards as well as organizations transitioning 
from one type of communications system to another. Having case studies 
that run the gamut from "this worked well" to "this was painful" is also 
valuable.

--Paul Hoffman