IAOC report in advance of IETF 101

IAOC Chair <iaoc-chair@ietf.org> Tue, 13 March 2018 22:28 UTC

Return-Path: <iaoc-chair@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 262DC124D68; Tue, 13 Mar 2018 15:28:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IAOC Chair <iaoc-chair@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Cc: iaoc@ietf.org
Subject: IAOC report in advance of IETF 101
X-Test-IDTracker: no
X-IETF-IDTracker: 6.75.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: ietf@ietf.org
Message-ID: <152098013115.9858.12117056020611815306.idtracker@ietfa.amsl.com>
Date: Tue, 13 Mar 2018 15:28:51 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/fUwrJ448oI4qsMlbReRVhv87PEQ>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Mar 2018 22:28:51 -0000

This report is provided in advance of IETF101 for the purpose of giving IETF participants more detail of the current work of the IAOC. Please feel free to bring any questions about its contents to the IETF Plenary in London, or share them directly with the IAOC (iaoc@ietf.org).

The IETF’s 2018 budget has been finalized, and will shortly be available, along with a narrative outline of its important features, https://iaoc.ietf.org/budget-and-finance.html. Key things to note are that the IETF’s 2018 expenses are budgeted to be the same as for 2017, and registration and sponsorship revenue for 2018 are projected to be in line with 2017 actual revenue. Meeting fees have not been raised in several years, even as meeting expenses have increased. While there is no current plan to raise meeting fees in 2018, the budget advice for 2019 and beyond does project a requirement for meeting registration fee increases. The IAOC Finance Committee has been working on documenting the IETF’s financial model (codifying expectations of revenue and expenditures), which should help set expectations for different revenue streams, going forward. At the same time, sponsorship remains an important part of the IETF’s budget picture, as does the Internet Society’s continued financial support. On the subject of sponsorship, the IAOC looks forward to the successful contracting of professional fundraising expertise — an update is expected imminently.

Following up on the IAD transition, the IAOC conducted a 90-day review discussion with Portia Wenze-Danley. The IAOC plans to continue these regular check-ins throughout the transition process.

Since IETF 100, two regular work items have completed smoothly. The RFP for the development of RFC Format Tools yielded a contract awarded to Soaring Hawk https://mailarchive.ietf.org/arch/msg/ietf-announce/ceKbnZw7spJ0dOWTiJhSA7HhH3w. The RFP for IETF Legal Services also concluded successfully, with the engagement of Brad Biddle of Brad Biddle of Biddle Law PC, and David Wilson of Thompson Hine LLP, to serve as IETF's new legal counsel https://mailarchive.ietf.org/arch/msg/ietf-announce/7IwUwdBX4FadbgftTSB4D0tLOhU.

One regular work item that had some challenges was the finalization of the venue for IETF 103. Happily, in the end, things have been worked out with the contract (as you know, IETF 103 will be in Bangkok https://mailarchive.ietf.org/arch/msg/ietf-announce/KBiJnaHvcq_1m3D9jr8DW9NNkvw). The most important thing to take away from this experience is that contract negotiations can have some difficult moments, and on some future occasion it may be important for the IAOC to execute a fallback plan. We are happy with the outcome, and pleased that we didn’t have to exercise a fallback plan this time, but you can rest assured that there was reading and consideration of the soon-to-be-published MTGVENUE document.

Looking ahead, during the week of IETF 101 and/or at its retreat, the IAOC will be constituting its committees, as it does every year. There is an open call for volunteers from the community, for those who have the desire and ability to help. (See https://mailarchive.ietf.org/arch/msg/ietf-announce/kQy7Ob-GeQ-w0uB_WTO1PXfkpyc). Also, the IAOC will have its annual retreat in late April. Concrete suggestions for improving transparency would be welcomed, for discussion at that retreat.

At IETF 101, the IAOC welcomes two new members: Glenn Deen and Andrew Sullivan will replace departing IAOC appointees Tobias Gondrom and myself (Leslie Daigle) whose terms are concluding.

IAOC Chair, for the IAOC.