Re: [arch-d] [IAB] The IAB Liaison Oversight program - feedback on closing
Bernard Aboba <bernard.aboba@gmail.com> Wed, 24 February 2021 05:21 UTC
Return-Path: <bernard.aboba@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 CC7CB3A0E18; Tue, 23 Feb 2021 21:21:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=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=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 RFsCsHZhB5Ge; Tue, 23 Feb 2021 21:20:57 -0800 (PST)
Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) (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 22CE23A0E15; Tue, 23 Feb 2021 21:20:56 -0800 (PST)
Received: by mail-lf1-x12a.google.com with SMTP id d3so1111183lfg.10; Tue, 23 Feb 2021 21:20:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=GPbHB8eGX0c4rH5SJrq101jfM2DZCQROwD2PC0dGEQk=; b=TIq79zeYJkpn1kl5/QKE2gBUHv2tA0hXuyWWrboz+xtzSEwP+HzERXP3SGYiJYZpzk N8MOS2Zchqhd6mOuvx0CCkH8fcJ3Jft20xaJf82T1LKNNxAm9OjZ1I5+ijPiagoKbWbZ teFLyXbPkLzBqdhgNVh5iBnI5DYJRQYQ0bQwxYvGPvANpu9wvrDKUWfqeF9nK/hr6frk kJ7mUPpugYUmCtGkvdYuVDFyytAPlKN1VkqKCbdTTm3MqZplQeg9qm79kaWPvtSlP17V GwGjMCC6GVSdAr/c4uDM9nfpx/w5w9xhf77rCPNvh0YjbQ4b0KHFYZP2DGyRhCdLpn2I yzbw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=GPbHB8eGX0c4rH5SJrq101jfM2DZCQROwD2PC0dGEQk=; b=AjINtL8Wb5L0GcrHfgrJB+rTwDTATiVDTnQTlF+2eUwpEaqAn7Qb1ay9B4Vo/6JK1K xvoM5kGvw1QanVUEj5XwQ/PpkwC+vlwqgikRloS/OFnK4A10nLz4iO7QY4VQwzTii86u Fg7mO2YBA+DTXjetuyUUwiHQaccWswYYfli69w/yRahFFqzsDn/K3WbN9lQvkj6MvFfu VwnAjh4GMr3ll7l0dPAsXLclpzKkibW6TXMxUFGqI8a9oRSPz8sI9qo/cAYHlk5MRzjb LapCcxVagafUCO5y/lwiXKeE0R2Bdbq3IzcGGwH8TQVt1eJXPlj4XjVJzRQhv6yfUMn+ ooZg==
X-Gm-Message-State: AOAM5301Cvbg9I5tk1qDmnDtGEalxZz2KDVQHonmBf8N6/p1AqMOQROR OgjE68CWXXLhjuvqqO0b2KSePPEIfvXil2icyl+eKI7pw2s=
X-Google-Smtp-Source: ABdhPJwaOrdGbCYGpQF3Y/iiMf29JMxCmQzASB4GghxQCMx0htw1cXhQ5eabJV+Jxze0Z0j5cPtp1B6f5cYfshDm6+A=
X-Received: by 2002:ac2:5ec1:: with SMTP id d1mr9703091lfq.48.1614144054592; Tue, 23 Feb 2021 21:20:54 -0800 (PST)
MIME-Version: 1.0
References: <MWHPR02MB24649D2053322ED233429A05D6809@MWHPR02MB2464.namprd02.prod.outlook.com> <313945B7-F998-410F-B067-004D95704C73@mnot.net> <ybl8s7ebcdn.fsf@w7.hardakers.net>
In-Reply-To: <ybl8s7ebcdn.fsf@w7.hardakers.net>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Tue, 23 Feb 2021 21:20:44 -0800
Message-ID: <CAOW+2dukxQRu9HA2v0mTR_k6ijtxAp7bv4e8cJVjrr-XOgpL+g@mail.gmail.com>
To: Wes Hardaker <wjhns1@hardakers.net>
Cc: "architecture-discuss@iab.org" <architecture-discuss@iab.org>, IAB IAB <iab@iab.org>
Content-Type: multipart/alternative; boundary="000000000000fd88a405bc0e328a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/1-bF5qF40Bwn7OttIWErRTevwCs>
Subject: Re: [arch-d] [IAB] The IAB Liaison Oversight program - feedback on closing
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, 24 Feb 2021 05:21:01 -0000
I must say, I find this discussion quite confusing. The management of liaisons is a fundamental task of the IAB. *How* the IAB organizes itself to carry out the task is up to the IAB. But the IAB does need to examine the functioning of liaison relationships on a regular basis, as well as monitoring the performance of liaison managers, so as to appoint or replace them as needed (or choose not to reappoint a replacement if there is no need). For that periodic review to get done, someone on the IAB has to step up and take a leadership role, and probably at least one other IAB member should take part, just to provide some backup/burden sharing. The individual(s) then report to the IAB on a regular basis. You can call those individual(s) the "IAB leads" or a "Program", it doesn't much matter. But you can't just say "the IAB will do it" - if you don't have specific individuals identified, and a regular rhythm for the work, then it's not likely to happen by accident. And this regular work *does* need to be done - or else you end up with liaison managers who have long since lost interest, or worse - managers who take advantage of the lack of IAB oversight to overstep their roles. In that sense, liaison management is is quite a different IAB responsibility than say, the RFC Editor Program, where it was envisaged that the IAB would *not* get involved in the details. So when it is said "the program did not meet", I am wondering whether this really means that the IAB hasn't been soliciting liaison reports on a regular basis, or paying attention to the performance of liaison managers. If so, that's not a statement about "the program" - it's a statement about the IAB - and something that should be brought to the attention of the nomcom. On Tue, Feb 23, 2021 at 3:21 PM Wes Hardaker <wjhns1@hardakers.net> wrote: > > Here I sit. Perched on the fence. > > I'm convinced that the existing program was either not needed or at > least not functional as is (not meeting is a clear indication of that). > Thus, I think a recharter likely wouldn't have been helpful because it > would have left an existing non-functional structure in place with a > minor incremental change (or at least, that's what I think the most > likely outcome would be). > > It would be best, IMHO, to decide what *is* needed and then come up with > a structure that works to support that. I doubt it will look like what > it used to look like. > > Here's some example bullets of what might be needed for such a program: > > * Evaluation of the program as a whole > * Evaluation of liaisonships with each other organization > * Evaluation of changes for organizations with which we have or need > relationships with > * Evaluation for how to best distribute incoming information from > liaisonships to the rest of the IETF technical community. > * [your ideas here] > > Here's what should be out of scope (IMHO): > > * Evaluation of individual liasons -- that's in the IAB's charter > * Handling of the liaison reports/interactions themselves -- (again, IAB) > > Here's the things that might be needed to achieve the goals: > > * A person or group of people responsible to ensure the program (or > whatever) is operational and active (chairs) > * Assured representation from the IETF (including, but limited to, the > IAB, the IESG, the wider IETF community, ....) > * Assured representation from the external organizations that may wish > to have a voice (the SDOs with which we interact may want to > participate -- we may even facility dialog at a higher level) > > What are the risks? > > * this could quickly grow much bigger than need be (the above is already > potentially too large) > * this could quickly grow too political > * this could quickly become bureaucratic > * And, like its predecessor, it could become forgotten and unused > > ... > > I think the liaisonships with other SDOs are critical to our success as > an SDO in the Internet ecosystem. A lot has happened in the last 10 > years that has proven that. The existing liaisonships do work, and we > do hear from and communicate with and through them. The question left: > is there more that should be done to improve the work, or better yet, > help the liaisons themselves be more effective? If so, what? > > -- > Wes Hardaker > USC/ISI > > _______________________________________________ > Architecture-discuss mailing list > Architecture-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/architecture-discuss >
- Re: [arch-d] The IAB Liaison Oversight program - … BRUNGARD, DEBORAH A
- Re: [arch-d] The IAB Liaison Oversight program - … Andrew G. Malis
- Re: [arch-d] [IAB] The IAB Liaison Oversight prog… Mark Nottingham
- Re: [arch-d] [IAB] The IAB Liaison Oversight prog… Wes Hardaker
- Re: [arch-d] The IAB Liaison Oversight program - … Toerless Eckert
- Re: [arch-d] The IAB Liaison Oversight program - … Mirja Kuehlewind
- Re: [arch-d] [IAB] The IAB Liaison Oversight prog… Melinda Shore
- Re: [arch-d] [IAB] The IAB Liaison Oversight prog… Bernard Aboba
- Re: [arch-d] [IAB] The IAB Liaison Oversight prog… Mark Nottingham
- Re: [arch-d] [IAB] The IAB Liaison Oversight prog… Bernard Aboba
- Re: [arch-d] The IAB Liaison Oversight program - … Eliot Lear
- Re: [arch-d] The IAB Liaison Oversight program - … Guntur Wiseno Putra
- Re: [arch-d] The IAB Liaison Oversight program - … BRUNGARD, DEBORAH A
- Re: [arch-d] The IAB Liaison Oversight program - … Guntur Wiseno Putra