[arch-d] The IAB Liaison Oversight program

Mirja Kuehlewind <ietf@kuehlewind.net> Tue, 23 February 2021 16:54 UTC

Return-Path: <ietf@kuehlewind.net>
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 359C73A0A2B; Tue, 23 Feb 2021 08:54:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id fuUp89SAtroS; Tue, 23 Feb 2021 08:54:37 -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 3D9123A0942; Tue, 23 Feb 2021 08:54:29 -0800 (PST)
Received: from p200300dee71fe600099adfd57fb215f4.dip0.t-ipconnect.de ([2003:de:e71f:e600:99a:dfd5:7fb2:15f4]); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1lEax8-0008Lc-5O; Tue, 23 Feb 2021 17:54:26 +0100
From: Mirja Kuehlewind <ietf@kuehlewind.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.\))
Message-Id: <20D66908-CE42-46B8-8D0E-832A4399B81A@kuehlewind.net>
Date: Tue, 23 Feb 2021 17:54:22 +0100
Cc: IAB IAB <iab@iab.org>
To: architecture-discuss@iab.org
X-Mailer: Apple Mail (2.3608.
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1614099269;7affd11f;
X-HE-SMSGID: 1lEax8-0008Lc-5O
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/Vh_JnUo3LFgkckQsz6srm4tRBNY>
Subject: [arch-d] The IAB Liaison Oversight program
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: Tue, 23 Feb 2021 16:54:39 -0000

Hi all,

As per our charter, '[t]he IAB acts as representative of the interests of the IETF and the Internet Society in technical liaison relationships with other organizations concerned with standards and other technical and organizational issues relevant to the world-wide Internet'[1]. That representation is carried out by liaison managers, who are selected from the community by the IAB. Liaison managers are overseen by individual members of the IAB who act as shepherds (see also [2]).

Firstly, I would like to note that this message is not intended to propose any changes to the liaison manager/shepherd system at this time, as the IAB believes that this representation works well.

In parallel to the liaison manager/shepherd system, the IAB is operating the Liaison Oversight program (see [3]). This program has been dormant for several years, and does not have a clear role to play in liaison management as of today. The program supported the IAB in developing the framework for liaison relationships and setting the requirements for the related IT systems but these activities were completed some time ago. 

As part of the IAB effort to restructure its programs, the IAB is in the process of reviewing all open programs. Given the currently unclear function and role of the IAB Oversight program, the IAB has decided to conclude the program. Again, this will not impact the liaison management as performed today.

The IAB sees liaison management as an important part of its role and has taken on responsibilities like periodically reviewing liaison relationships itself, rather than delegating that responsibility to a program. Further, the IAB serves as a contact point to the community and frequently reaches out to members of the community in order to request support for the IAB and the IETF community in its liaison activities on an as-needed basis, depending on the liaison relationship and technology in question. This process has been working well and the IAB is working on further improving it to make it more clear and transparent to the community as well as improving continuity of knowledge and knowledge transfer between the IAB and a broad range of community experts.

If during the on-going review of the liaison management process the IAB may find it necessary to have one or more programs for liaison management, e.g. to support maintenance of very active liaison relationships or to improve a specific parts of the liaison management process, the new IAB program structure has been set up to make to easy and uncomplicated to open and close programs/support groups as needed. Inline with that, the IAB believes it is the better option to create new groups with clear charters and purposeful membership, rather than potentially recycling a dormant program.

We thank the program members for their service.


On behalf on the IAB

[1] RFC2850 s 2(f)
[2] https://www.ietf.org/about/liaisons/
[3] https://www.iab.org/activities/programs/iab-liaison-coordination-program/