Future IETF Meeting Network Requirements
bofreq-livingood-future-ietf-meeting-network-requirements-01

Document Type Proposed BOF request
Title Future IETF Meeting Network Requirements
Last updated 2025-01-15
State Proposed
Editors Sean Turner , Jason Livingood
Responsible leadership Roman Danyliw
Send notices to (None)
bofreq-livingood-future-ietf-meeting-network-requirements-01

Name: Future IETF Meeting Network Requirements

Description

The IETF has completed the second IASA2 retrospective. That report contained an action item on this, and this BoF is intended to take the next step on that.

Operating the network to support an IETF meeting is a significant undertaking and is
at the core of people's meeting experience. Today, we rely on some contractors to
lead the deployment and operation of the network, supported by volunteers from the
IETF community. There are a range of costs that are associated with the meeting
network, some of which may be related to supporting things that the community does
not want or need. Alternatively, there may be things the network does not provide
that the community would like to add.

It seems like this is a good opportunity to convene a BoF session to discuss the
community's future expectations for the meeting network. These expectations can
then be used to create technical requirements that the IETF meeting network team can
consider for future meetings.

Required Details

  • Status: Not WG Forming
  • Responsible AD: Roman Danyliw
  • BOF proponents: Jason Livingood <jason_livingood@comcast.com>, Sean Turner <sean@sn3rd.com>
  • Number of people expected to attend: 50
  • Length of session (1 or 2 hours): 2 hours
  • Conflicts (whole Areas and/or WGs)
  • Chair Conflicts: IETF Chair
  • Technology Overlap: None
  • Key Participant Conflict: TBD

Information for IAB/IESG

Not applicable - this is an administrative BoF

Agenda