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

Mark Nottingham <mnot@mnot.net> Wed, 26 August 2020 06:11 UTC

Return-Path: <mnot@mnot.net>
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 658783A0DDF for <architecture-discuss@ietfa.amsl.com>; Tue, 25 Aug 2020 23:11:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=dy7cUXWT; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=stNpIhUo
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 BLXkG-ddMxaI for <architecture-discuss@ietfa.amsl.com>; Tue, 25 Aug 2020 23:11:41 -0700 (PDT)
Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 935A13A0DDA for <architecture-discuss@ietf.org>; Tue, 25 Aug 2020 23:11:41 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id A10CAEB4; Wed, 26 Aug 2020 02:11:40 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Wed, 26 Aug 2020 02:11:40 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=6 3Sx16ye2dasZ4UA2ND2jrB08HHGQSXaivdvvhDWYEk=; b=dy7cUXWTVZztWDhqb vWiC/j44i3WCPKxa4BOUdU004nXuG/Meik8Xbq7vlRILcToxGTl8sb25mj8gyj0S EjTJtf8iAj6A4Y4BC9cCa13EJNJKc9KplwyDZayBiUZYk0J1PxvU4lEiflHNzHAF TQxXtoFSo9yz4hitGdCtMUW3xcp2QWGmcCNIRYV00tpxivKuEaZdM9oEhQNFqa/P r4rVnVyoUSux81VyCwWLspA3gvywKjSVFbipBGZP7EQlzjWYjkhst/dmmV1eNZ9Y wRcEi4uRUxhwqxIoO9q/IAd4WutrSCST1f+v6/Nun0KDKOyqnaxcgHHTOvJQ1NiG J0Mug==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=63Sx16ye2dasZ4UA2ND2jrB08HHGQSXaivdvvhDWY Ek=; b=stNpIhUo0M+DHXiFhFutW5/86LeOFRdKO0t7sz18rcbYZFcf05fehYn2G jLOd4wB3Sim843CynlfoBQEyO0oeD3ffycnd8bG5qKR8AbHFatqPxeajLMALBw+/ j7DMjfvBmcJ1jQ4BQzTvA1ThofTbQmRHVQrQKnEHGeHsJSal843akcwcz4LiUqFU hKgkpETsHW8VHdR3Tl3LTsm0c+qU0KixOkjmu9ITIRUpjvx6S4gUCuoUMbhHzKoe T+VEntm6+uIJtxRon5BdIqpQrlCpnsqVO2YLbGAlhnUvnJfUyf8gkJh0Ff905Z/b WLxmpTumsyvmhs+MrRFo/SPlR2xzg==
X-ME-Sender: <xms:G_1FX2ySIBGUn7tPW8R-6rzG3uZR1pF-9gtgnAuLb6aPixVQ4r3uug>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedruddvuddguddtkecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtdejnecuhfhrohhmpeforghr khcupfhothhtihhnghhhrghmuceomhhnohhtsehmnhhothdrnhgvtheqnecuggftrfgrth htvghrnhepudfhtddugeeftdefkeevveeghfevveffteejfeekheetgeelhfdvhfffvdef hffgnecuffhomhgrihhnpehirggsrdhorhhgpdhivghtfhdrohhrghdpmhhnohhtrdhnvg htnecukfhppeduudelrddujedrudehkedrvdehudenucevlhhushhtvghrufhiiigvpedt necurfgrrhgrmhepmhgrihhlfhhrohhmpehmnhhothesmhhnohhtrdhnvght
X-ME-Proxy: <xmx:G_1FXyR88Xkg0wt6eH70ufjgpHqAuoMgUSPDWmEWoFXDBgxOgeXasQ> <xmx:G_1FX4WL6oHJOqRDr28bah-SQevOYDDR13S3kQWvc-NEv3QQcynkEw> <xmx:G_1FX8hRtkNT0tK_7MHcmSgMA7KIfR_-xFumozT_e56HGvyFWawkvw> <xmx:HP1FX7OOWopjFRvMZcuWCAzt4aYqqlFn35SDBakMVL43eVot0INfCg>
Received: from [192.168.7.30] (119-17-158-251.77119e.mel.static.aussiebb.net [119.17.158.251]) by mail.messagingengine.com (Postfix) with ESMTPA id 80900328005D; Wed, 26 Aug 2020 02:11:37 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <1D675EBC-4AC7-4E01-87CC-4DF4F0D9DD3C@tony.li>
Date: Wed, 26 Aug 2020 16:11:33 +1000
Cc: IAB Executive Administrative Manager <execd@iab.org>, edm@iab.org, architecture-discuss@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <6BC67FE7-5517-4733-96F1-A7991ABD9AF7@mnot.net>
References: <159839206489.26388.9889652884666821@ietfa.amsl.com> <1D675EBC-4AC7-4E01-87CC-4DF4F0D9DD3C@tony.li>
To: tony.li@tony.li
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/4OlswXD6dARNcwDC1929KiE7brI>
Subject: Re: [arch-d] [Edm] 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: Wed, 26 Aug 2020 06:11:43 -0000

Tony,

Do you have any constructive feedback about the program, or other work that we should focus on? Just calling it 'pointless' doesn't help.


> On 26 Aug 2020, at 7:53 am, tony.li@tony.li wrote:
> 
> 
> 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
> 
> -- 
> Edm mailing list
> Edm@iab.org
> https://www.iab.org/mailman/listinfo/edm

--
Mark Nottingham   https://www.mnot.net/