[arch-d] Proposed IAB program: Evolvability, Deployability, & Maintainability.

Tommy Pauly <tpauly@apple.com> Mon, 06 July 2020 19:02 UTC

Return-Path: <tpauly@apple.com>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 31A733A0A09 for <architecture-discuss@ietfa.amsl.com>; Mon, 6 Jul 2020 12:02:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Aa-j9YT0HPyf for <architecture-discuss@ietfa.amsl.com>; Mon, 6 Jul 2020 12:02:07 -0700 (PDT)
Received: from ma1-aaemail-dr-lapp02.apple.com (ma1-aaemail-dr-lapp02.apple.com []) (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 53FCF3A09CC for <architecture-discuss@iab.org>; Mon, 6 Jul 2020 12:02:06 -0700 (PDT)
Received: from pps.filterd (ma1-aaemail-dr-lapp02.apple.com []) by ma1-aaemail-dr-lapp02.apple.com ( with SMTP id 066IjFlk006354 for <architecture-discuss@iab.org>; Mon, 6 Jul 2020 12:02:05 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=from : content-type : mime-version : subject : message-id : date : to; s=20180706; bh=yhSYFqY8DOk8nXv0g8H4BcUPTHhZ3onzXSSs1KOr568=; b=k5sZHQq6iNLU1Wo2tejvjPrB8XXtHonDtnIGNj/OJFWSf5kPy0P8llDqro7A0C4dqKjR cyW7nSxD5vf3WA44lOFnvr3ziLUMW8kVY2X3oE9g0ZNcy/DS2/gLq1ZSsGe2OULTzNd2 wJgtR8Z81hYsAhZOIm2v10D22dPR9nF/f6EjjfevYaV0SFaE5IqMHOMn9cHTro4AHE+0 SYhhjBmoGQO8myh66iKgzRIVZPhyOfTtHBji/pKoVAGnUZrISWTVd2bKrRz55NCaFZSA 5M0tVnXG8Io+SU4sgavOvoK+sm1IO1z7xHt2n2R06einZnMxfVt6HuJdYM3tm3DDtUBu 9Q==
Received: from rn-mailsvcp-mta-lapp03.rno.apple.com (rn-mailsvcp-mta-lapp03.rno.apple.com []) by ma1-aaemail-dr-lapp02.apple.com with ESMTP id 322pescv45-3 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <architecture-discuss@iab.org>; Mon, 06 Jul 2020 12:02:05 -0700
Received: from rn-mailsvcp-mmp-lapp04.rno.apple.com (rn-mailsvcp-mmp-lapp04.rno.apple.com []) by rn-mailsvcp-mta-lapp03.rno.apple.com (Oracle Communications Messaging Server 64bit (built Mar 12 2020)) with ESMTPS id <0QD200TX2A7A6IL0@rn-mailsvcp-mta-lapp03.rno.apple.com> for architecture-discuss@iab.org; Mon, 06 Jul 2020 12:01:59 -0700 (PDT)
Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp04.rno.apple.com by rn-mailsvcp-mmp-lapp04.rno.apple.com (Oracle Communications Messaging Server 64bit (built Mar 12 2020)) id <0QD200E00A7AJX00@rn-mailsvcp-mmp-lapp04.rno.apple.com> for architecture-discuss@iab.org; Mon, 06 Jul 2020 12:01:59 -0700 (PDT)
X-Va-T-CD: f34240ee9f18a8bc9b487d2fa1de37f1
X-Va-E-CD: 80fc74c126ddaebfaa5b4bd5a801094e
X-Va-R-CD: bd1804ac603c8166b4722f6ca7eb6779
X-Va-CD: 0
X-Va-ID: 75bd2119-0272-4da3-ac28-34a2b4c03d4a
X-V-T-CD: f34240ee9f18a8bc9b487d2fa1de37f1
X-V-E-CD: 80fc74c126ddaebfaa5b4bd5a801094e
X-V-R-CD: bd1804ac603c8166b4722f6ca7eb6779
X-V-CD: 0
X-V-ID: d71d17a5-ce46-41d8-9c45-52d9bfe632b6
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-07-06_16:2020-07-06, 2020-07-06 signatures=0
Received: from [] (unknown []) by rn-mailsvcp-mmp-lapp04.rno.apple.com (Oracle Communications Messaging Server 64bit (built Mar 12 2020)) with ESMTPSA id <0QD200OJ0A7A8R00@rn-mailsvcp-mmp-lapp04.rno.apple.com> for architecture-discuss@iab.org; Mon, 06 Jul 2020 12:01:59 -0700 (PDT)
From: Tommy Pauly <tpauly@apple.com>
Content-type: multipart/alternative; boundary="Apple-Mail=_167563D1-F0B3-45C9-92C5-94FA7FE460F6"
MIME-version: 1.0 (Mac OS X Mail 13.4 \(3608.\))
Message-id: <087DBE75-7103-4D82-8878-59F1E53592C8@apple.com>
Date: Mon, 06 Jul 2020 12:01:58 -0700
To: "architecture-discuss@iab.org" <architecture-discuss@iab.org>
X-Mailer: Apple Mail (2.3608.
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-07-06_16:2020-07-06, 2020-07-06 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/vua9gZnC6dSnDjtQUh-6hdAd4Zw>
Subject: [arch-d] Proposed IAB program: Evolvability, Deployability, & Maintainability.
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: Mon, 06 Jul 2020 19:02:16 -0000

The IAB is considering starting a new program that would look at the Evolvability, Deployability, and Maintainability of Internet protocols. The description of the program is included at the bottom of this email.

We’d like to get feedback on the proposed program topic and description. We’ll be considering this over the next few weeks, and your thoughts and input are welcome!



Evolvability, Deployability, & Maintainability (EDM) Program

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.