Re: [Edm] [arch-d] New IAB Program: Evolvability, Deployability, & Maintainability (EDM) Tue, 25 August 2020 21:53 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DA60C3A0C27; Tue, 25 Aug 2020 14:53:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.4
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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ZT_8LfSSiZe7; Tue, 25 Aug 2020 14:53:46 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::52a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6CC2A3A0C33; Tue, 25 Aug 2020 14:53:46 -0700 (PDT)
Received: by with SMTP id d19so7749589pgl.10; Tue, 25 Aug 2020 14:53:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; 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;; 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=lCy5dH19ryZovpKiCJj+Xoyl1GIJBPZzGJLm5W4+N3JXoF44HSKxglYO+Ti4AkehHm w8C2mDLqveso0crvueywbpK//XGHMN9RFUu1mSuN55xa9NqfX3e4Gx+mI6a+WxbagL2h em3q0B9G8W7Qs/mT0+yP6QZNI6HQtkt4jnAq4VSA1JPLguvI0dGx8cs4VEKdTBF0DyXg 9d1aMpfXA0PTibZ8bPS3r3ZBF3mqfAaSbMtcEaxDqce9O2uflM3X6ALIcT0aHCnZpYaE m2Q9k90gNjEzf8c/fOa0OmnPuAcY+PQrnAV2OqmN8Rh9zSd3aJ8n0tjHHl3cMufvLLuD bqzg==
X-Gm-Message-State: AOAM530zjQog0UYIfKySPVkb64yu77ZRT74sIOXP+hpLXuQ0B//0kPrN kX5AZukLmM4YllMVljKe7+ID2yoiHeM=
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 [] ([]) by with ESMTPSA id j13sm201724pfn.166.2020. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 25 Aug 2020 14:53:44 -0700 (PDT)
Sender: Tony Li <>
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.\))
In-Reply-To: <>
Date: Tue, 25 Aug 2020 14:53:41 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <>
To: IAB Executive Administrative Manager <>
X-Mailer: Apple Mail (2.3608.
Archived-At: <>
Subject: Re: [Edm] [arch-d] New IAB Program: Evolvability, Deployability, & Maintainability (EDM)
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Evolvability, Deployability, & Maintainability \(Proposed\) Program" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-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.


> On Aug 25, 2020, at 2:47 PM, IAB Executive Administrative Manager <> 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 <>
> Mailing list:
> Address:
> To subscribe:
> Archive:
> Program Page:
> 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