IETF Logo Mail Archive

Re: [arch-d] Call for Comment: <draft-iab-use-it-or-lose-it-02> (Long-term Viability of Protocol Extension Mechanisms)

Russ Housley <housley@vigilsec.com> Sun, 12 September 2021 19:23 UTC

Return-Path: <housley@vigilsec.com>
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 72FCE3A1887 for <architecture-discuss@ietfa.amsl.com>; Sun, 12 Sep 2021 12:23:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 EKAV6BywqUYd for <architecture-discuss@ietfa.amsl.com>; Sun, 12 Sep 2021 12:23:39 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D677E3A1886 for <architecture-discuss@ietf.org>; Sun, 12 Sep 2021 12:23:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 86D37300BFD for <architecture-discuss@ietf.org>; Sun, 12 Sep 2021 15:23:39 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id gbpLFnx9BxEE for <architecture-discuss@ietf.org>; Sun, 12 Sep 2021 15:23:38 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 2D2B3300B78; Sun, 12 Sep 2021 15:23:38 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
Date: Sun, 12 Sep 2021 15:23:36 -0400
References: <162991703946.25379.3009360954932586670@ietfa.amsl.com>
To: architecture-discuss@ietf.org, IAB <iab@iab.org>
In-Reply-To: <162991703946.25379.3009360954932586670@ietfa.amsl.com>
Message-Id: <147A3BCB-EBBB-4BC7-B812-7C7670377CAC@vigilsec.com>
X-Mailer: Apple Mail (2.3445.104.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/XHKWXr66BuIf8HD-0Qu_4KkXu50>
Subject: Re: [arch-d] Call for Comment: <draft-iab-use-it-or-lose-it-02> (Long-term Viability of Protocol Extension Mechanisms)
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 12 Sep 2021 19:23:46 -0000

I read the document, and I encourage the IAB to publish it.

Russ

> On Aug 25, 2021, at 2:43 PM, IAB Executive Administrative Manager <execd@iab.org> wrote:
> 
> This is an announcement of an IETF-wide Call for Comment on 
> draft-iab-use-it-or-lose-it-02.
> 
> The document is being considered for publication as an Informational RFC 
> within the IAB stream, and is available for inspection at:
> <https://datatracker.ietf.org/doc/draft-iab-use-it-or-lose-it/>
> 
> The Call for Comment will last until 2021-09-22. Please send comments to
> architecture-discuss@ietf.org and iab@iab.org.
> 
> Abstract:
> 
>   The ability to change protocols depends on exercising the extension
>   and version negotiation mechanisms that support change.  This
>   document explores how regular use of new protocol features can ensure
>   that it remains possible to deploy changes to a protocol.  Examples
>   are given where lack of use caused changes to be more difficult or
>   costly.

v2.23.0 | Report a Bug | By Email