Re: [arch-d] The IAB Liaison Oversight program - feedback on closing
"Andrew G. Malis" <agmalis@gmail.com> Tue, 23 February 2021 22:31 UTC
Return-Path: <agmalis@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 525713A0DFE; Tue, 23 Feb 2021 14:31:06 -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 z-3NA1T9pLVu; Tue, 23 Feb 2021 14:31:04 -0800 (PST)
Received: from mail-qt1-x82c.google.com (mail-qt1-x82c.google.com [IPv6:2607:f8b0:4864:20::82c]) (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 E90643A0DD4; Tue, 23 Feb 2021 14:31:03 -0800 (PST)
Received: by mail-qt1-x82c.google.com with SMTP id o34so46247qtd.11; Tue, 23 Feb 2021 14:31:03 -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=AJCLlQGR3C61fgCeGybwdNYBGWOQZUy7X1OAhQ25TVg=; b=UOVPaWuurFfQZ3WqJRoF2dvIqQUffr+ZzUqWQWNUjIqWkqdXnR7HoZFKFcR0Nb6r3X g7Rk7qriei8PUBrL4IC39TWtOxUVpTAxDQZjXy5q3yWF7iCXvywT6GoAkwWtAuk58WDC ur1OjVPcVkwlm13XuqZAE8WYpR0bOWgKNfNBhmiV4UK8YaOsSKDTDWPAmMKwdBGuZ3SD 4W82V1QXnFbkFUja0iFgDDIYCOpjng+Qs7cDAf2XZnGaycLQwdSZeqUO9dBMUMfAWa7I 5mga2LACo/shishDm4vI2MJHvI6BRmJeAA9rt4QRpOV5J8XvhyPKbLqgzg4+BqoOiSFP RpLg==
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=AJCLlQGR3C61fgCeGybwdNYBGWOQZUy7X1OAhQ25TVg=; b=ERJgOW2mDSZMW8JZniyhXvqHVy8goY3IURPaxM0bCXuOSjETCVRj9zfWrsn7wH4tCg l66sUBq7zWiQqy16rFQMvShX6LM8LWQyJZme561TOqUwYE+wSyEfoxE6wdNhsVRRmtTU tW7Wz+nko6tQoRzwibujcM87QjCxqXnn984/wghw8zzkKkdzPnaXFZCox/JN1uN2Xh4Z TxhC5SGKsNo4uHA+200YHeug7EAZeu9j/YBnhrnyawYBVpqtX/rRKIlHngMNp1zmivoT 9TFiG7s6YHMylVlY8J+Te8/ulPmuJGRCp23bGN343k8lG3cmzPq8c9DSDYXjpueOOqFR VyEg==
X-Gm-Message-State: AOAM531uyq62grHFrsdobwO01xj7vPCD147NbfAYILFFQf0Y19oGw5rE wz5UBUpcSoMIqFKDGnuiifGNexA34mFBh4wrTvE=
X-Google-Smtp-Source: ABdhPJx0V59tXKi4qjWf02U7q+T8/nM/hlFkXW0eie1VhYiznx+vTu/TLvBl4CVVI9bdtk7jGmQZrP41bWEc8gsVFxk=
X-Received: by 2002:ac8:5985:: with SMTP id e5mr27462931qte.160.1614119462795; Tue, 23 Feb 2021 14:31:02 -0800 (PST)
MIME-Version: 1.0
References: <MWHPR02MB24649D2053322ED233429A05D6809@MWHPR02MB2464.namprd02.prod.outlook.com>
In-Reply-To: <MWHPR02MB24649D2053322ED233429A05D6809@MWHPR02MB2464.namprd02.prod.outlook.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Tue, 23 Feb 2021 17:30:46 -0500
Message-ID: <CAA=duU1Fi17hwyU5EAnxRpTNM9-eTkvdHVV7DGszkKgZ_scv3A@mail.gmail.com>
To: "BRUNGARD, DEBORAH A" <db3546@att.com>
Cc: Mirja Kuehlewind <ietf@kuehlewind.net>, "architecture-discuss@iab.org" <architecture-discuss@iab.org>, IAB IAB <iab@iab.org>
Content-Type: multipart/alternative; boundary="000000000000347b6305bc08797c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/A-R3qAsIJWOa7n6h7SP92oZa_68>
Subject: Re: [arch-d] 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: Tue, 23 Feb 2021 22:31:06 -0000
Deborah, As a former IAB member back when we took liaisons more seriously, a bit +100! Cheers, Andy On Tue, Feb 23, 2021 at 5:05 PM BRUNGARD, DEBORAH A <db3546@att.com> wrote: > Hi, > > [no-hats] > > While the IAB can open/close programs per their discretion without > community input, I want the community to know that, as incoming IAB member, > I had raised concerns on closing this program. IETF's liaison relationships > to other SDOs has always been an important issue to me, as a working group > chair of groups working with ITU, Routing AD, and MPLS liaison. > > Basically, I didn't understand why the approach on this program was to > close it without first considering rechartering. The rationale for closing > this program, i.e., no need for "recycling a dormant program", is identical > to the IANA program ("sleepy program"), though for that program the > conclusion was to update the charter and ask the community for feedback. > > And so my bigger concern - the IAB says it is "unclear" on the need for a > liaison oversight program. For those of us involved in other SDOs, IETF's > current "whac-a-mole[*]" process of involving experts on "as-needed basis" > is very concerning. This program was formed to "provide strategic > direction" so as to relieve our liaison managers of being in conflict with > RFC4691: > > https://www.iab.org/documents/correspondence-reports-documents/2011-2/iab-response-to-some-iesg-thoughts-on-liaisons/ > > One of the four questions on the 2021 IAB Questionnaire was "how can the > value of the IETF to internal and broader technical community be improved". > To me, that question from the community, was affirming the importance to be > [more] proactive in our liaison strategy to SDOs/forums/open source > efforts. Not to close the responsible program with no new proposal. > > Sigh, as new IAB member, I'll tackle drafting a "clear charter" with > "purposeful membership" program on liaison oversight, and hopefully be able > to convince my IAB colleagues. Hopefully SOON [**] in the IAB decision > timeline. > > 2nd (longer) Sigh, > Deborah > (countdown - 2 weeks!) > [*] https://en.wikipedia.org/wiki/Whac-A-Mole > [**] https://www.ietf.org/archive/id/draft-farrel-soon-06.txt > > -----Original Message----- > From: Architecture-discuss <architecture-discuss-bounces@ietf.org> On > Behalf Of Mirja Kuehlewind > Sent: Tuesday, February 23, 2021 11:54 AM > To: architecture-discuss@iab.org > Cc: IAB IAB <iab@iab.org> > Subject: [arch-d] The IAB Liaison Oversight program > > 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. > > Regards, > > Mirja > On behalf on the IAB > > > [1] RFC2850 s 2(f) > [2] > https://urldefense.com/v3/__https://www.ietf.org/about/liaisons/__;!!BhdT!zvZhVZdKjTglhGiKkGwKaQOHI2hnkIzAee1ZtSK_SjFw_VMFpb4eIq9xnFihmAQ$ > [3] > https://urldefense.com/v3/__https://www.iab.org/activities/programs/iab-liaison-coordination-program/__;!!BhdT!zvZhVZdKjTglhGiKkGwKaQOHI2hnkIzAee1ZtSK_SjFw_VMFpb4eIq9xK0bE_LM$ > > > _______________________________________________ > Architecture-discuss mailing list > Architecture-discuss@ietf.org > > https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/architecture-discuss__;!!BhdT!zvZhVZdKjTglhGiKkGwKaQOHI2hnkIzAee1ZtSK_SjFw_VMFpb4eIq9x7IQ6lHI$ > > _______________________________________________ > 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