Re: IAB report to the community for IETF 110

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 05 March 2021 20:02 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 A68753A0D92 for <ietf@ietfa.amsl.com>; Fri, 5 Mar 2021 12:02:48 -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 mXWe4JcbnJ1f for <ietf@ietfa.amsl.com>; Fri, 5 Mar 2021 12:02:46 -0800 (PST)
Received: from mail-pf1-x436.google.com (mail-pf1-x436.google.com [IPv6:2607:f8b0:4864:20::436]) (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 B11253A104F for <ietf@ietf.org>; Fri, 5 Mar 2021 12:02:01 -0800 (PST)
Received: by mail-pf1-x436.google.com with SMTP id 16so1396322pfn.5 for <ietf@ietf.org>; Fri, 05 Mar 2021 12:02:01 -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=JXAMXGJNvfkrg/6DXHqAcPj38OlHCuqNbyTiW++97ro=; b=bLzS6jDPHsyAACccbcyhXLl8gFLXFTccJ/Z4tcNVM4X+ZywsU2nm3Goq+FguJGbibj r9AaO21zP7+7BSKlq6nqen8FMwvI6OynuG1edZj6qxkLepN56sD/ICLfElYIP2pPJS9J M8bozqQBfgIpXxyEKC2aspg2zBGTZ8lMhLQ/e1BtNvYHITOWrWgGvjxdCx+xJQTFrtKt i4cbj+g09SDEQpNgmvDwVOftmVQmLSffl4Xkwc8txjmf9/dQzFxIj44ax/ZcDFzEevAQ tR1hz9DUYaF3dCkrZM1XCFccGUtchtOw/KkVk4KJ/4yPuvSEeeWYmakfClLuyf2M/xZi sKeQ==
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=JXAMXGJNvfkrg/6DXHqAcPj38OlHCuqNbyTiW++97ro=; b=SuvlRAKI0TEjC9Hk1uMKK67uhRkmxy2N0KSnuhRMTDlX/EVpXYyFROAEyFpgGDmWvD 0WttxjfLF+lwU00EvYD9v1S9MpVvqqtLwzojMMbj+2CpAIPqkGC1QfeJz1tRSbSFPOv2 6jwGGhDqW6L/Gm24gZn+IaC7F+QpduK6wWUizwPAiqHp1qn+2HKuuuuo/IGlfodb2tgo u8XDN1/ffCRUjwshtB+HkDvLh2CkgNnvnTlaSi7hcmJtzmd4e22Ngo4GHuuGlhkp0fYo eZ1dKu0mjBNVPmJVbSRpGPXMVgFXmdibnR9s4tlqbNtKic5r4C5rLipxSfq0VVX0PuPX /4Eg==
X-Gm-Message-State: AOAM530zYD/ujmp5lxE1i9R8WKKbGbKNHBCeS1eShaYN7uoZXflNVxix c1Y8I/0dD3Nj/mYtSmHpBnr3QYEnQm7byA==
X-Google-Smtp-Source: ABdhPJyDOe5waFcyJ7q1t6WKN4I7vWTcq/8DHD5MRUosDVjfK2NWXo7Nmgt7UOf2H4kN/z8zmfJC+w==
X-Received: by 2002:a65:4947:: with SMTP id q7mr10002614pgs.83.1614974519985; Fri, 05 Mar 2021 12:01:59 -0800 (PST)
Received: from [192.168.178.20] ([151.210.131.28]) by smtp.gmail.com with ESMTPSA id g15sm3251082pfb.30.2021.03.05.12.01.58 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 05 Mar 2021 12:01:59 -0800 (PST)
Subject: Re: IAB report to the community for IETF 110
To: IAB Chair <iab-chair@iab.org>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
References: <C586EE71-4BB3-454C-B102-528F61E0AEA7@iab.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <b881ba57-7beb-e035-f7eb-7cf55ddd3060@gmail.com>
Date: Sat, 06 Mar 2021 09:01:55 +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: <C586EE71-4BB3-454C-B102-528F61E0AEA7@iab.org>
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/HLprlNDnWXHQuzb5D6m9C4iXo_I>
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 20:02:54 -0000

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
>