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

tony.li@tony.li Wed, 26 August 2020 14:37 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 41BE93A1533 for <architecture-discuss@ietfa.amsl.com>; Wed, 26 Aug 2020 07:37:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.498
X-Spam-Level:
X-Spam-Status: No, score=-1.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 fezsY99o8Mxr for <architecture-discuss@ietfa.amsl.com>; Wed, 26 Aug 2020 07:37:13 -0700 (PDT)
Received: from mail-pg1-f177.google.com (mail-pg1-f177.google.com [209.85.215.177]) (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 933BC3A0D4D for <architecture-discuss@ietf.org>; Wed, 26 Aug 2020 07:37:13 -0700 (PDT)
Received: by mail-pg1-f177.google.com with SMTP id i10so1134168pgk.1 for <architecture-discuss@ietf.org>; Wed, 26 Aug 2020 07:37:13 -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=8m8QpXN/8Zg1H1piYtMy1KWOWjR9z0Qr+rhxWdpOBVU=; b=madRab/X9fJl0l2b7FAh1B3S0XuIaVUhd04xTZLhlyMMhxcEHRmJLHqMJCzEQyWaPu G2CcrETKzljUH/jkUMRFeLWpLpLeKEvynviCkHHQLgtA0ZfDPXEk2UP1bBeeCh+eOrU0 xT8V4ZgNvQcXJpg2M8a5sa65F9TIDwPmt44g65JUG88aZxWuMvS19ygIHB/BFRCeMrTE VFeA1TUi4HeCJ5ArriHt0Nml0uZ9wfUso7HHtgbjJl2XsHBuL0Lue60TwptOKgIOoMtS p04OLDV/dMQWoqMWtLfnbFg8E0y1rjrk1qa3Gpty+T3XNk1K//kIohT+HyxFAPU9kfSp 2R3w==
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=8m8QpXN/8Zg1H1piYtMy1KWOWjR9z0Qr+rhxWdpOBVU=; b=kcDuVkgqgu1rD2H1O2Pw5sI9fOnHzZNiHOFJy0xOMAkFtdoW3ATp9CuA7ff8zbDtQ1 GeyfwS2M6nqfF9vh8hMetTMgkXisZpQkaSgNR6UckEz54qaw7PQ9e5Jd90E+xZlblGZR saki5bMAwZMlrKXPgYGb4wlubVqvMShioKVmU6uDDY1VyY5tlYJiH56MfJ9R2kD0UAZv ELl4lTcyvgl0B6/bsfWtD5zIM+KAu7C+SHJCLB3wQlgyLpcE3nG+ujgH5MscYt/WUhN7 +H7EWsHfcPWkBL0mHM+BPM4T1269J3v6RE3nl9gN88G0mp5qEkIU+X3z3wSE06U1dldN nvFQ==
X-Gm-Message-State: AOAM533LSSA+zTtU9kkBjk52+mkjeiO5gJyN7rWSFaVrWeEUyRUV3LjX QAgJBs4mFQMN8/GJW7iJ7M3DdPhexKc=
X-Google-Smtp-Source: ABdhPJyA2pekcnN1dkKl7LdlnBt7D1rrtxJ1+bXghqqsLfDPlLvfBeXnS3GQuc1e6vG6wAGiooT9Qg==
X-Received: by 2002:a63:1457:: with SMTP id 23mr11028526pgu.80.1598452572892; Wed, 26 Aug 2020 07:36:12 -0700 (PDT)
Received: from [10.95.80.107] ([162.210.129.5]) by smtp.gmail.com with ESMTPSA id v78sm3508920pfc.121.2020.08.26.07.36.11 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Aug 2020 07:36:12 -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: <6BC67FE7-5517-4733-96F1-A7991ABD9AF7@mnot.net>
Date: Wed, 26 Aug 2020 07:36:07 -0700
Cc: IAB Executive Administrative Manager <execd@iab.org>, edm@iab.org, architecture-discuss@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <6B5BBDD0-32F5-4E96-ADB8-813E4EA2A2A9@tony.li>
References: <159839206489.26388.9889652884666821@ietfa.amsl.com> <1D675EBC-4AC7-4E01-87CC-4DF4F0D9DD3C@tony.li> <6BC67FE7-5517-4733-96F1-A7991ABD9AF7@mnot.net>
To: Mark Nottingham <mnot@mnot.net>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/PyOw6PvS4aMYlcGOZ_RUCNTwokc>
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 14:37:15 -0000

Mark,

The starting point should be a clear problem statement.  With examples.

Tony


> On Aug 25, 2020, at 11:11 PM, Mark Nottingham <mnot@mnot.net> wrote:
> 
> 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/
>