From nobody Thu Nov 12 09:47:30 2020
Return-Path: <ietf@kuehlewind.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 6F3EB3A145A;
 Thu, 12 Nov 2020 09:47:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001,
 URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Ar8kfpAWxScG; Thu, 12 Nov 2020 09:47:26 -0800 (PST)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de
 [IPv6:2a01:488:42:1000:50ed:8223::])
 (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 A6C2B3A1456;
 Thu, 12 Nov 2020 09:47:26 -0800 (PST)
Received: from p200300dee707b600141061c179aad33d.dip0.t-ipconnect.de
 ([2003:de:e707:b600:1410:61c1:79aa:d33d]); authenticated
 by wp513.webpack.hosteurope.de running ExIM with esmtpsa
 (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 id 1kdGgs-0002tA-M8; Thu, 12 Nov 2020 18:47:22 +0100
From: Mirja Kuehlewind <ietf@kuehlewind.net>
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Thu, 12 Nov 2020 18:47:21 +0100
Message-Id: <3036D6C9-A1F4-4035-B039-0C9E75DE55C4@kuehlewind.net>
To: architecture-discuss@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.4)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1605203246;3e619cba;
X-HE-SMSGID: 1kdGgs-0002tA-M8
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/mkD3eWYS0ECn44RrABS-gwvrbOY>
Subject: [arch-d] Call for Feedback on the new proposed structure for
 Technical Programs and Administrative Support Groups
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: Thu, 12 Nov 2020 17:47:28 -0000

Hi all,

The IAB has been working on refactoring its programs. You can find the =
proposed description of the new structure and procedures on Github [1]. =
The aim of this effort is to increase transparency, visibility, and =
openness of the architectural work done by the IAB.=20

In analysing the current IAB programs, the IAB identified two kinds of =
programs which are quite different in their needs and goals. Therefore, =
the new structure proposes to separate today=E2=80=99s IAB programs into =
Technical Programs and Administrative Support Groups.=20

Technical Programs are more short-lived activities (even though this =
might be longer than one IAB cycle) and focus on specific technical or =
architectural issues that require both input from experts as well as =
community discussion. Current Technical Programs are model-t and EDM.=20

Administrative Support Groups are long-term activities that help the IAB =
to fulfil their oversight or administrative responsibilities. Based on =
the nature of their task these groups usually consist of a small, =
dedicated set of experts that may have a need to handle matters =
confidentially. Administrative Support Groups are the current technical =
plenary program, the IANA program, and the liaison program. Please note =
that the IAB is also in the progress of reviewing these activities.=20

RSOC could also be considered as an Administrative Support Group; =
however, given the on-going process in the future RFC editor model =
program, the IAB will not implement any changes or actions on RSOC until =
this process has concluded.

Further, the future RFC editor model program is not considered in this =
new structure. The IAB is not intending to implement any changes or =
intervene in any way with the work of the program.

We believe that this new structure will better support the IAB=E2=80=99s =
needs and hopefully clarify procedures and expectation. Further, we hope =
that this will also help to increase the exchange with the community!

Please provide feedback on this mailing list, on GitHub by raising an =
issue, or directly to the IAB <iab@iab.org>.

Mirja K=C3=BChlewind
IAB chair

[1] =
https://github.com/intarchboard/IAB-programs/blob/master/IAB-programs.md


