Re: [arch-d] New IAB Program: Evolvability, Deployability, & Maintainability (EDM)

tony.li@tony.li Tue, 25 August 2020 21:53 UTC

Return-Path: <tony1athome@gmail.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 8EDDA3A0C34 for <architecture-discuss@ietfa.amsl.com>; Tue, 25 Aug 2020 14:53:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.4
X-Spam-Level:
X-Spam-Status: No, score=0.4 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 2OqsvDjmtZvC for <architecture-discuss@ietfa.amsl.com>; Tue, 25 Aug 2020 14:53:46 -0700 (PDT)
Received: from mail-pg1-x52f.google.com (mail-pg1-x52f.google.com [IPv6:2607:f8b0:4864:20::52f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12F4A3A0C27 for <architecture-discuss@ietf.org>; Tue, 25 Aug 2020 14:53:46 -0700 (PDT)
Received: by mail-pg1-x52f.google.com with SMTP id v15so7754797pgh.6 for <architecture-discuss@ietf.org>; Tue, 25 Aug 2020 14:53:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=+4ivqI2lqd/3YU4etj7lrvtxytVtpsWr1WMmFxvuVDc=; b=VSgb5lySf0fYqERenbe9I+S7pvaVdLgqJnBjfZtQmNJiEsxQKZaNhvrl2b3LD3SvkA K4igN1hXEc+XhxMhQdLfnC78yQZmxQQKuQm2ZE73a+nXKdfGLbkdvIEWymmwQpTH030U +CuXo/EPsMG9zcGcp3yj7UG7J8m2q38gYvMwk8Gy9YXXNHlhn7QwmtPilrsZa4Q/lWZ/ 7HNSbSdNTngmh+PmtJnyNAXDR7xM9pvJfBbqTVFgfPg3WndQLemlRTv3JeUSdIZC6Wdq z5eBiy5Nre/UHAvjY3z53UYEhpeY+XfxSDZXHtkfnl3dFESO/0HG1iiLfLr9tq8PP7y5 ddwg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:mime-version:subject:from:in-reply-to :date:cc:content-transfer-encoding:message-id:references:to; bh=+4ivqI2lqd/3YU4etj7lrvtxytVtpsWr1WMmFxvuVDc=; b=dE85AU/oXDerynVWzAibGwPj/UQguL14fgAN9J0QnHp96lBO473vaWh5aEW6sRn62f SLhE9Lc4emK3UZW/RH7ytjAHlcJV2EBeCQkz/ir9k/ETrH37dHJGHlXa8GOuNAW1i7Qj nc/vioYJZ3xrHc2eaHuzZ1xE3ewH5bBHjTtZdD2b37fT1dfkmmMNWl/ro3eHPtZIXD4C qLTCopHVLYbSEmWT7juHkjZPgJP9O6Xyr/Ur/JZxfRVkP7yKtHlx0BMTXLMHr+0l1fkA L1W2dWTjLPF5M/44u/9G6i03BcokyA9BydLuy0xXhsOJzdyg9hYvgfaZ156auYHP87V2 fkOg==
X-Gm-Message-State: AOAM530m6ncF6DYf+2FY+RE6lLw7Bg1F4Clw6E2MiNNni+eB8eiJjRk2 eMx0S45fNWQwzQbSGxpBqFQ1iPJosQA=
X-Google-Smtp-Source: ABdhPJw7xgzaIjFS3vEXoglMczL0CXQXURdMf+ELFIYnG623SlqjZD+JRuKfVcNm8Aik6L6Ak0PmFQ==
X-Received: by 2002:a63:f70e:: with SMTP id x14mr6250903pgh.407.1598392425498; Tue, 25 Aug 2020 14:53:45 -0700 (PDT)
Received: from [10.95.82.114] ([162.210.129.5]) by smtp.gmail.com with ESMTPSA id j13sm201724pfn.166.2020.08.25.14.53.43 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 25 Aug 2020 14:53:44 -0700 (PDT)
Sender: Tony Li <tony1athome@gmail.com>
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
From: tony.li@tony.li
In-Reply-To: <159839206489.26388.9889652884666821@ietfa.amsl.com>
Date: Tue, 25 Aug 2020 14:53:41 -0700
Cc: architecture-discuss@ietf.org, edm@iab.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <1D675EBC-4AC7-4E01-87CC-4DF4F0D9DD3C@tony.li>
References: <159839206489.26388.9889652884666821@ietfa.amsl.com>
To: IAB Executive Administrative Manager <execd@iab.org>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/R49VebPf6pf5k122YzkbtcBunPE>
Subject: Re: [arch-d] New IAB Program: Evolvability, Deployability, & Maintainability (EDM)
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: Tue, 25 Aug 2020 21:53:48 -0000

Seems like point 1 should be ignoring pointless IAB programs.

There’s work to be done. This isn’t it.

Tony


> On Aug 25, 2020, at 2:47 PM, IAB Executive Administrative Manager <execd@iab.org> wrote:
> 
> A new IAB Program has been formed on Evolvability, Deployability, & 
> Maintainability (EDM). For additional information, please contact the 
> IAB or the Program Lead.
> 
> Evolvability, Deployability, & Maintainability (EDM) Program
> -----------------------------------------------------------------------
> 
> IAB Lead:
> Tommy Pauly <tpauly@apple.com>
> 
> Mailing list:
> Address: edm@iab.org
> To subscribe: https://www.iab.org/mailman/listinfo/edm
> Archive: https://mailarchive.ietf.org/arch/browse/edm/
> 
> 
> Program Page: https://www.iab.org/activities/programs/evolvability-deployability-maintainability-edm-program/
> 
> Program Description:
> 
> This program will focus on how to practically encourage best practices 
> within the IETF to ensure that the IETF’s standards process considers 
> protocol evolution, deployability, and long-term maintainability. This 
> group will work on documents that catalog and analyze successful 
> strategies for protocol evolution, deployment, and maintenance, such as 
> updating and extending RFC 6709. Moreover, it will focus on ways to help 
> promote and increase awareness of these strategies within the IETF via 
> program meetings, workshops, and helping organize efforts within working 
> groups and various IETF teams. The program will include members of the 
> IESG and the tools team to help implement these strategies.
> 
> The topics this group will consider include:
> 
> * Evolvability: Encourage protocols to design for extensibility and 
>  greasing, and promote the use of extension points to prevent 
>  ossification. Make it easy for people, especially those who aren’t 
>  steeped in IETF process, to know which extension points are the right 
>  ones to use for a given protocol (and which ones should be considered 
>  more stable/ossified), and make sure there aren’t high allocation 
>  barriers to use those extension points.
> 
> * Deployability: Focus on how we make “running code” something that is 
>  better integrated into the working group process. Look at methods to 
>  catalog implementations, tools for tracking interoperability testing 
>  on different protocol versions, or repositories of which versions of 
>  protocols are implemented and used on the Internet. Discuss how 
>  deployments can advertise experiments they are running.
> 
> * Maintainability: Many working groups have expressed a desire to have 
>  ways for the community of protocol designers and implementers to keep 
>  track of the current state of affairs in deployment patterns, known 
>  errata/bugs, or best practices. Help promote consistent ways to host 
>  non-RFC working group output, like FAQs, wikis, and discussion venues. 
>  Consider how this community involvement can continue and involve the 
>  right experts, even after a working group closes.
> 
> The program will:
> 
> * Engage with the IETF community and implementers outside of the IETF to 
>  identity successes and problem areas, and collect ideas for 
>  improvements.
> * Work with the IESG and directorates to determine how best practices 
>  for evolvability can best be applied during IESG review and IETF last 
>  call.
> * Work with the IESG and tools team on ways to connect implementers and 
>  communities that develop and maintain protocols, both while a working 
>  group is active, and after a working group has concluded its charter.
> 
> _______________________________________________
> Architecture-discuss mailing list
> Architecture-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/architecture-discuss