Re: IAB report to the community for IETF 110

Tommy Pauly <tpauly@apple.com> Fri, 05 March 2021 21:13 UTC

Return-Path: <tpauly@apple.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 A06F53A0E0D; Fri, 5 Mar 2021 13:13:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.366
X-Spam-Level:
X-Spam-Status: No, score=-2.366 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.248, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=apple.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 e4WZnBySPdJf; Fri, 5 Mar 2021 13:13:39 -0800 (PST)
Received: from rn-mailsvcp-ppex-lapp45.apple.com (rn-mailsvcp-ppex-lapp45.rno.apple.com [17.179.253.49]) (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 C52633A0E0B; Fri, 5 Mar 2021 13:13:39 -0800 (PST)
Received: from pps.filterd (rn-mailsvcp-ppex-lapp45.rno.apple.com [127.0.0.1]) by rn-mailsvcp-ppex-lapp45.rno.apple.com (8.16.0.43/8.16.0.43) with SMTP id 125LCWOC024711; Fri, 5 Mar 2021 13:13:38 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=from : message-id : content-type : mime-version : subject : date : in-reply-to : cc : to : references; s=20180706; bh=pASwHkBnl4ZjOsD/QjNRP/J+80vhCcci8SJ6+Pu3ppw=; b=fm6TQPs0tKh9fyofm6+2w3n8roRGG2/e2IYzLmhJNeBN1zCRv0TL+9KD8jjyVdKE7tL1 PCZZR+jiUdrTA/xQL5aEb1VJ771dagaTX80xfnICqeW8c5t+bfP72V2aGdICUNcpCkH0 51anUWo0Ulw2V6+ME2lW2lr4wAxa86ERpUnurnDhBt3MpVh44eRQadlWf9IJ236CN3Pc zsUrSFQcftasy+jO1Qjn+5E04jTE99+ZfB2qQHgPvGPpuh0ys4L/zaIgcYHjalDD+uX/ /UO//ErlnQfD+FNrhanh0D8LmzRq75Jk/z36jQF5VrN0gRbghMbFihMDf2SSLXtu4TzE TQ==
Received: from rn-mailsvcp-mta-lapp03.rno.apple.com (rn-mailsvcp-mta-lapp03.rno.apple.com [10.225.203.151]) by rn-mailsvcp-ppex-lapp45.rno.apple.com with ESMTP id 373410yw04-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 05 Mar 2021 13:13:38 -0800
Received: from rn-mailsvcp-mmp-lapp01.rno.apple.com (rn-mailsvcp-mmp-lapp01.rno.apple.com [17.179.253.14]) by rn-mailsvcp-mta-lapp03.rno.apple.com (Oracle Communications Messaging Server 8.1.0.7.20201203 64bit (built Dec 3 2020)) with ESMTPS id <0QPI00XTTLMQLHG0@rn-mailsvcp-mta-lapp03.rno.apple.com>; Fri, 05 Mar 2021 13:13:38 -0800 (PST)
Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp01.rno.apple.com by rn-mailsvcp-mmp-lapp01.rno.apple.com (Oracle Communications Messaging Server 8.1.0.7.20201203 64bit (built Dec 3 2020)) id <0QPI00000LG48H00@rn-mailsvcp-mmp-lapp01.rno.apple.com>; Fri, 05 Mar 2021 13:13:38 -0800 (PST)
X-Va-A:
X-Va-T-CD: 77c40f669fd41aacbbe5121aa5d6725f
X-Va-E-CD: 77e3cceec49ac227fda0ba85e7573fd5
X-Va-R-CD: d4803369ede59ae7bc7b55f1af778924
X-Va-CD: 0
X-Va-ID: 52d4606d-88ac-4bb2-8897-37275240024e
X-V-A:
X-V-T-CD: 77c40f669fd41aacbbe5121aa5d6725f
X-V-E-CD: 77e3cceec49ac227fda0ba85e7573fd5
X-V-R-CD: d4803369ede59ae7bc7b55f1af778924
X-V-CD: 0
X-V-ID: fd57fdc0-f930-492b-bb76-6b653187e03c
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.761 definitions=2021-03-05_14:2021-03-03, 2021-03-05 signatures=0
Received: from smtpclient.apple (unknown [17.11.100.250]) by rn-mailsvcp-mmp-lapp01.rno.apple.com (Oracle Communications Messaging Server 8.1.0.7.20201203 64bit (built Dec 3 2020)) with ESMTPSA id <0QPI00842LMNJQ00@rn-mailsvcp-mmp-lapp01.rno.apple.com>; Fri, 05 Mar 2021 13:13:36 -0800 (PST)
From: Tommy Pauly <tpauly@apple.com>
Message-id: <47C15B77-469A-45EB-81A5-03B9A82CF6D7@apple.com>
Content-type: multipart/alternative; boundary="Apple-Mail=_005EC832-C986-4306-9285-EFDE3CF9737E"
MIME-version: 1.0 (Mac OS X Mail 15.0 \(3668.0.2\))
Subject: Re: IAB report to the community for IETF 110
Date: Fri, 05 Mar 2021 13:13:35 -0800
In-reply-to: <b881ba57-7beb-e035-f7eb-7cf55ddd3060@gmail.com>
Cc: IAB Chair <iab-chair@iab.org>, IETF Discussion Mailing List <ietf@ietf.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <C586EE71-4BB3-454C-B102-528F61E0AEA7@iab.org> <b881ba57-7beb-e035-f7eb-7cf55ddd3060@gmail.com>
X-Mailer: Apple Mail (2.3668.0.2)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.761 definitions=2021-03-05_14:2021-03-03, 2021-03-05 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ufef2AAZkTfLjn7Bn1qeCpIrPK8>
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 21:13:42 -0000

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 <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> 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
>> 
>