* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Birds of a Feather Meetings (IETF Pre-WG Efforts)

This page provides one common place that lists "possible IETF pre-WG efforts", known as Birds of a Feather ("BoF") meetings. Anybody who proposes a BoF is strongly encouraged to register the BoF effort here at such time as appropriate; e.g., during steps 1 and 2 in RFC 5434. Also see https://www.ietf.org/wg/bof-procedures.html.

The IAB will also attempt to provide BoF Shepherds as described in their document on the subject only on request from the IESG. If you feel that your BoF would benefit from an IAB BoF Shepherd, please discuss this with your Area Director.

To allow the Secretariat to schedule a BoF slot if it is approved, each entry MUST include the following items:

  • Long name and abbreviation
  • Description, including whether the BoF is intended to form a WG or not
  • The responsible Area Director (AD)
  • BoF Chairs (or the ADs as placeholders)
  • Number of people expected to attend
  • Length of session (1, 1.5, 2, or 2.5 hours)
  • Conflicts to avoid (whole Areas and/or WGs)
  • Links to the mailing list, draft charter if any, relevant Internet-Drafts, etc.

Template for BOF Entry

Timeframe IETF 100 (Singapore)

Current schedule of "Important Dates" requires that all BOF proposal requests be submitted to Area Directors (ADs) by 2359 UTC Friday, 2017-09-29. The IAB and IESG will hold a joint teleconference to discuss the proposals. ADs will be expected to approve or disapprove the BOF request on that teleconference, ensuring that the Secretariat has all of the information to put the first draft of the agenda together on or before 2017-10-13.

Applications and Real-Time


IETF Administrative Support Activity 2.0 (IASA20)


The purpose of this BOF is to continue discussions from IETF 98 and 99 and the iasa20@ietf.org mailing list regarding refactoring the IETF Administrative Support Activity (IASA). The IASA 2.0 design team has been incorporating feedback from IETF 99 and further refining and expanding their document. Assuming that work gets shared with the community well in advance of IETF 100, the goal of this session will be to determine the sense of the community about the direction for IASA 2.0.

The responsible Area Director (AD): Alissa Cooper
BoF Chairs: Jon Peterson
Number of people expected to attend: 100
Length of session (1, 1.5, 2, or 2.5 hours): 2 hours
Conflicts to avoid (whole Areas and/or WGs): mtgvenue, all of sec area, stir, modern, tram, sipbrandy
Mailing List: ​https://www.ietf.org/mailman/listinfo/iasa20
Draft charter: n.a.
Relevant drafts:


Operations and Management



Firmware Update (FUD)


Vulnerabilities with Internet of Things (IoT) devices have raised the need for a secure firmware update mechanism that is also suitable for constrained devices. Security experts, researchers and regulators recommend that all IoT devices are equipped with such a mechanism. This work group, once formed, will develop an interoperable approach for securely updating IoT devices.

Status: WG Forming
Responsible AD: Kathleen Moriarty
BoF chairs: Russ Housley / David Waltermire
Number of people expected to attend: 100
Length of session (1, 1.5, 2, or 2.5 hours): 1.5 hours
Conflicts to avoid (whole Areas and/or WGs): curdle ipwave stir ipsecme tls lamps mile sacm saag
Links to the mailing list, draft charter if any, relevant Internet-Drafts:

Agenda (draft)

  • Agenda bash, scribe, minute taker [5min]
  • Review of proposed charter text [10 mins]
  • Charter discussion [45 mins]
  • Discussion of work items and milestones [30 mins]


IAB Sessions

Previous meeting BOFs

Timeframe IETF 99 (Prague)

Timeframe IETF 98 (Chicago)

Timeframe IETF 97 (Seoul)

Timeframe IETF 96 (Berlin)

Timeframe IETF 95 (Buenos Aires)

Timeframe IETF 94 (Yokohama)

Timeframe IETF 93 (Prague)

Timeframe IETF 92 (Dallas)

Timeframe IETF 91 (Honolulu)

Timeframe IETF 90 (Toronto)

Timeframe IETF 89 (London)

Timeframe IETF 88 (Vancouver)

Timeframe IETF 87 (Berlin)

Timeframe IETF 86 (Orlando)

Timeframe IETF 85 (Atlanta)

Timeframe IETF 84 (Vancouver)

Timeframe IETF 83 (Paris)

Timeframe IETF 82 (Taipei)

Timeframe IETF 81 (Quebec City)

Timeframe IETF 80 (Prague)

Timeframe IETF 79 (Beijing)

Timeframe IETF 78 (Maastricht)

Timeframe IETF 77 (Anaheim)

Timeframe IETF 76 (Hiroshima)

Timeframe IETF 75 (Stockholm)

Timeframe IETF 74 (San Francisco)

Timeframe IETF 73 (Minneapolis)

Timeframe IETF 72 (Dublin)

Timeframe IETF 71 (Philadelphia)

Timeframe IETF 70 (Vancouver)

Timeframe IETF 69 (Chicago)

Timeframe IETF 68 (Prague)

Timeframe IETF 67 (San Diego)

Timeframe IETF 66 (Montreal)

Timeframe IETF 65 (Dallas)