Re: IAB report to the community for IETF 110

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 05 March 2021 22:06 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 583023A0FE5 for <ietf@ietfa.amsl.com>; Fri, 5 Mar 2021 14:06:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, NICE_REPLY_A=-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 BBM58ct5y4Kt for <ietf@ietfa.amsl.com>; Fri, 5 Mar 2021 14:06:23 -0800 (PST)
Received: from mail-pj1-x1032.google.com (mail-pj1-x1032.google.com [IPv6:2607:f8b0:4864:20::1032]) (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 AF1413A0FDA for <ietf@ietf.org>; Fri, 5 Mar 2021 14:06:23 -0800 (PST)
Received: by mail-pj1-x1032.google.com with SMTP id l18so2969424pji.3 for <ietf@ietf.org>; Fri, 05 Mar 2021 14:06:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=jFrjeeWs6Mvc0yqh9hhQTIwZv4DrIoOPgE0O7DgieWg=; b=Nung+xYDquyVfIOgRcryYu90LXZe1kN4YZjmyjY4gTfrs6Ll3702yL/oorD+XH0KgU 2Zn1o4oRhHSH+2h3ZXgfUxD4SwJlGNx/vBT/8A/9XGci2dKFxVKcrQcPEmpXoCywfA0f djDxhtvGTB8+/bFIjOuPBnlVrNuOm61jnDPF87dTN8EdWQkuiLmnu/FHo1DjOdpqZpLA 0WDxlG3UieqaXTpB+EsLBtmL2FF4hlxKFzjAfEZuGIwkIZGd5BrEqUuja8KuKXbE+G74 6BNOcTgNPTo43j1+XBLM1v0nVz/XPzwtNkNTjZw5cV1nobO0dSlPfZ8+msPPEz5FOYyE DfTg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=jFrjeeWs6Mvc0yqh9hhQTIwZv4DrIoOPgE0O7DgieWg=; b=uaH5WlJTPLpMFMfSgciSXxqXiQHOnuxYX87GHJGhxX83RVS8os9BOT2ICYhsriWFFt myEvAyH4H+s6QkGEYW0TBnv4jHrtrz8hQf6+NoeEybR5HNwFFai+1D7mah5kbkA1PAq1 IQ/4307WHi+7rqM39qkWkGJGfav6+ttYMnhp7qs2pDjeIE0r4WjFulxcCp7c54NV7zeY QUpPNegqahHEXfJfODOmkd9lvEqvB5fao0NryAbrNhjs6SQh2gr2q4mvRuHAkevMhwTg JfW4V2MnMfg6SJnXPy7EihzaZkax/YGAa6LYlyqLWQUV4X4bgzVRjw1FzMvmW+E6Gok4 M2mA==
X-Gm-Message-State: AOAM530QTvwDqeZ8DjCLYkOEnNyq32tYcrL69t5w6FQhvN8/F8use5o0 jXyyclVRgKRHRDcM+aOvPVzH2Y0JPdbWrw==
X-Google-Smtp-Source: ABdhPJwW9AAZWPj6e4p+8B7x4kLbsCm5vPBvg6mxWyDh0+hm5xEMviKm0yrvIorIn9dzkjjvXtut+Q==
X-Received: by 2002:a17:90a:a088:: with SMTP id r8mr12318929pjp.73.1614981981755; Fri, 05 Mar 2021 14:06:21 -0800 (PST)
Received: from [192.168.178.20] ([151.210.131.28]) by smtp.gmail.com with ESMTPSA id e1sm3004056pjt.10.2021.03.05.14.06.19 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 05 Mar 2021 14:06:21 -0800 (PST)
Subject: Re: IAB report to the community for IETF 110
To: Tommy Pauly <tpauly@apple.com>
Cc: IAB Chair <iab-chair@iab.org>, IETF Discussion Mailing List <ietf@ietf.org>
References: <C586EE71-4BB3-454C-B102-528F61E0AEA7@iab.org> <b881ba57-7beb-e035-f7eb-7cf55ddd3060@gmail.com> <47C15B77-469A-45EB-81A5-03B9A82CF6D7@apple.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <caf7c129-817f-7754-a2d9-60bc2ce79bb7@gmail.com>
Date: Sat, 06 Mar 2021 11:06:16 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <47C15B77-469A-45EB-81A5-03B9A82CF6D7@apple.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UYy2U_i2QM1z8cFSBjhciWnafpQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Mar 2021 22:06:25 -0000

Tommy,

There are no new members until after next week's plenary. This seems procedurally sloppy to me. (It's not a disaster of course.)

Regards
   Brian Carpenter

On 06-Mar-21 10:13, Tommy Pauly wrote:
> The new and continuing members voted on the IAB chair, as normal! Due to the virtual meeting schedule, the inaugural meeting with the new members joining as full members (that would normally occur on the Sunday before IETF week) was held on the Wednesday before instead. This is the same process that was followed last year as well.
> 
> Please see the agenda for that meeting here: https://www.iab.org/wiki/index.php/2021-03-03_Agenda.
> 
> Best,
> Tommy
> 
>> On Mar 5, 2021, at 12:01 PM, Brian E Carpenter <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrote:
>>
>> Mirja,
>>
>>> IAB Chair selection
>>> ——
>>> The IAB has reselected me, Mirja Kühlewind, as IAB Chair. Thanks a lot! I’m really looking forward to serve another year in this role and to keep working with a new IAB on further improving transparency and visibility of the IAB hoping that we as a group can provide valuable input to the community!
>>
>> Congratulations, but I do have a question. Since the new members are not seated yet, does that mean that the old IAB has selected the Chair of the new one?
>>
>> In the past, to my knowledge, it has normally been the new IAB that selects its Chair, at the first IAB meeting after the changeover (or later, on one or two occasions).
>>
>> The IAB charter doesn't specify when the IAB selects its chair, which may be an oversight (by me, since I was the document's editor).
>>
>> Regards
>>   Brian
>>
>> On 06-Mar-21 02:45, IAB Chair wrote:
>>> Dear colleagues,
>>>
>>> As usually, the IAB has uploaded its report for the IETF-110 meeting to the proceedings in the datatracker. To access the full report, please see here:
>>>
>>> https://www.ietf.org/proceedings/110/slides/slides-110-ietf-sessa-iab-report-to-the-community-for-ietf-110-00
>>>
>>>
>>> In this email I would also like to use the opportunity to highlight some news:
>>>
>>> IAB Chair selection
>>> ——
>>> The IAB has reselected me, Mirja Kühlewind, as IAB Chair. Thanks a lot! I’m really looking forward to serve another year in this role and to keep working with a new IAB on further improving transparency and visibility of the IAB hoping that we as a group can provide valuable input to the community!
>>>
>>>
>>> Workshop reports
>>> ——
>>> The IAB has published the draft workshop report for the COVID-19 Network Impacts IAB workshop that was held online last November:
>>>
>>> https://datatracker.ietf.org/doc/draft-iab-covid19-workshop/
>>>
>>> We already received quite some feedback and some good reviews. Huge thanks for that! We believe this document will soon after the IETF-110 meeting be ready for publication as IAB RFC. However, more feedback and reviews are of course very welcome!
>>>
>>> Further, the report for the IAB workshop on Design Expectations vs. Deployment Reality in Protocol Development has been published as RFC 8980:
>>>
>>> https://datatracker.ietf.org/doc/rfc8980/
>>>
>>>
>>> IAB Liaison Coordination
>>> ——
>>> The IAB has established a new Liaison Coordinator position. This position provides a clear contact point for all liaison managers as well as for the community regarding any liaison-related requests towards the IAB. Further, this new role is a first step to improve coordination and communication of our liaison management and handling of liaison statements. The IAB is currently working actively on further improvements in that direction.
>>>
>>> To reach the IAB liaison coordinator(s) a new mailing alias has been established:
>>>
>>> liaison-coordinator@iab.org
>>>
>>>
>>> In any case, you can of course still reach the IAB with any questions, also regarding liaisons, directly by sending a mail to iab@iab.org.
>>>
>>> Or, feel free to also just send me an email directly, if you have any comments or concerns you want to discuss!
>>>
>>> Best regards,
>>> Mirja Kühlewind
>>> IAB Chair
>>>
>>> On behalf of the IAB
>>>
>>>
>>>
>>> _______________________________________________
>>> IETF-Announce mailing list
>>> IETF-Announce@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf-announce
>>>
>>
>