[Netrqmts] Fwd: New Version Notification for draft-daley-meeting-network-requirements-00.txt

Jay Daley <exec-director@ietf.org> Tue, 29 April 2025 03:34 UTC

Return-Path: <jay@staff.ietf.org>
X-Original-To: netrqmts@mail2.ietf.org
Delivered-To: netrqmts@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 6A2FA225D774 for <netrqmts@mail2.ietf.org>; Mon, 28 Apr 2025 20:34:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=staff-ietf-org.20230601.gappssmtp.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9CRiDHF4h5Lg for <netrqmts@mail2.ietf.org>; Mon, 28 Apr 2025 20:34:34 -0700 (PDT)
Received: from mail-pf1-x42b.google.com (mail-pf1-x42b.google.com [IPv6:2607:f8b0:4864:20::42b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id A20DC225D76F for <netrqmts@ietf.org>; Mon, 28 Apr 2025 20:34:34 -0700 (PDT)
Received: by mail-pf1-x42b.google.com with SMTP id d2e1a72fcca58-73c17c770a7so7424892b3a.2 for <netrqmts@ietf.org>; Mon, 28 Apr 2025 20:34:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=staff-ietf-org.20230601.gappssmtp.com; s=20230601; t=1745897673; x=1746502473; darn=ietf.org; h=date:to:references:message-id:subject:mime-version :content-transfer-encoding:from:from:to:cc:subject:date:message-id :reply-to; bh=8k155PNGIuqnyBpd5p8lpSonMwz3/Ze7N0IKILswqkc=; b=xJaRfiyfZfYnnW13+1SCinLT95p7SrOOHcdCIE79lhYZJ61CJDZS8wTGRmoPpE0Q60 m+niM/lZHQ1FMePEOGjKzXig9rSwHAaVB0QqR4HxqSQfJMwGctDwSak7g9Pmhr+8wSQZ fvGnz+HwAPKsGuZ/6+90sYEUCbp53uG1EvsukZd3SkAXwqYJRTMfXPAxUhFCMGgrZWWl LRmEGY1ZSy5An8sXDXsR0bUvNhsA90ucmL3XkgPTontl2JBeuffiEVQX7L9Vid6/2zR8 tB0jCpA9wWmPZlUbeOWJLNjyY0+4EsqG1NiCNU3uCsjziDB7HJKrM2ZGu6VY/UjTJakc gBEg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1745897673; x=1746502473; h=date:to:references:message-id:subject:mime-version :content-transfer-encoding:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=8k155PNGIuqnyBpd5p8lpSonMwz3/Ze7N0IKILswqkc=; b=Po1nLBbDRrZaonMOsZWUnAZxOJ/A0cGBaLSbikN9rAHZVvqmPiYXRy6Bd3iKWSZN6/ 4VqmSOf0Pf2Reynw6l8X9joa37bsHVQly/SdWhEzyDAYwskPeiuq/83clrQaZgjnC03P bRWPuc6gzsZoHSS2S9kyHUxr5vGoliBCNh8kjUowxRGc9K/T4EX75jR9y1H+RkBGMt94 MdroK3LA2skOVMd0yCBz45TU+gWPH/hOr+rJxCKrX7iC5ZFkRJevUMYze9Uk+RlptY3W XoRdSX7/HG+TgxZUdt4Jfde6vZXXjUyTOmBrEQ39AJJvqybV3XqBqKq6XbUJxg3xTdvA EChA==
X-Gm-Message-State: AOJu0YyA7L3Dl4ykZb+sPPT7wUvRzJpn6GK8pIr8sefZM+dMSz90yBu5 kID71v9Ri83qOkE5psWPIg+5mMPFTrUTJ2Ft68pYegAfyeEMkL/eIFhpCwScIflwViFPgyMpE/N BBQDHRA==
X-Gm-Gg: ASbGncuxeNKB6Yn/jAp3OvnQBzz46BhzT4Az7gpyRrdjoV5mlHkKptwJ0nRmbmMGu0z 2xMcj4hRsI+ZD8vmOz5xknulEdNrGSvoNoi32VUF6yQY6KX1dHjVkkVlagdfPJsUrv7N7RRgvtX +QNeQNAHpa72wFRUdFEzfDBNGg/jDxCmHw9BbDG0Fvbxl4uVFLvubY1kskOkXmNaIpoL3clIvv1 dgN/xep95HrHq1x1PdKAN4e4U8cY8i+cOENSiW+3pcF+2NH7aYwL1F8yTSi7drG5Da4b2CSVkkb xRJxNBf6RANOQh9/VZ0+8+Vx3POUi2fMaJnF4HXS1X33n9h4fFZzLQ0CwDtYpp9P9A7QZtjyT9K A7YKk6Jhj/alHTmHu/l+QDU2wdU0rECKtV7c8+tK+MyJO/w==
X-Google-Smtp-Source: AGHT+IFCP4gGZUO+k4QeFEvQ8BIALah4/CIT6zG4deNSV/sqEVYdfBNb9ATiayNq0quFUTrkCbrFKw==
X-Received: by 2002:a05:6a21:338d:b0:1f5:64fd:68ea with SMTP id adf61e73a8af0-2093c2cd288mr2443470637.4.1745897673284; Mon, 28 Apr 2025 20:34:33 -0700 (PDT)
Received: from smtpclient.apple (203-96-136-53.dsl-dynamic.connections.net.nz. [203.96.136.53]) by smtp.gmail.com with ESMTPSA id 41be03b00d2f7-b15fa80fa97sm7882290a12.51.2025.04.28.20.34.31 for <netrqmts@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 28 Apr 2025 20:34:32 -0700 (PDT)
From: Jay Daley <exec-director@ietf.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.500.181.1.5\))
Message-Id: <0DEC0B53-B7C4-443E-8A14-B3C000EE9E61@ietf.org>
References: <174589740918.363.7312605804609624778@dt-datatracker-9c7687889-5mqnr>
To: netrqmts@ietf.org
Date: Tue, 29 Apr 2025 15:34:18 +1200
X-Mailer: Apple Mail (2.3826.500.181.1.5)
Message-ID-Hash: GI7YVVNJ32LDZRAOGS3E6AVX4D7PHJZR
X-Message-ID-Hash: GI7YVVNJ32LDZRAOGS3E6AVX4D7PHJZR
X-MailFrom: jay@staff.ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Netrqmts] Fwd: New Version Notification for draft-daley-meeting-network-requirements-00.txt
List-Id: IETF Meeting Network Requirements <netrqmts.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netrqmts/0-NALhjE6uqPcVLYcBTMCsVdvJs>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netrqmts>
List-Help: <mailto:netrqmts-request@ietf.org?subject=help>
List-Owner: <mailto:netrqmts-owner@ietf.org>
List-Post: <mailto:netrqmts@ietf.org>
List-Subscribe: <mailto:netrqmts-join@ietf.org>
List-Unsubscribe: <mailto:netrqmts-leave@ietf.org>

Following on from various discussions about the IETF Network provided at IETF meetings, I have put together an I-D that aims to initiate a conversation on finding a way forward.  From the introduction:

> The network that IETF participants use at an IETF Meeting has been a
> high-profile feature of IETF Meetings for some time and is now a
> major part of the behind-the-scenes work and cost of running an IETF
> Meeting. This network replaces any venue network using equipment
> donated by suppliers, installed and managed by a mixed team of
> volunteers and contractors.
> 
> There are disagreements within the community about the requirements
> for this network, how it is delivered and whether or not the current
> cost and effort of providing the network is reasonable.
> 
> The IETF Administration LLC (IETF LLC) has overall responsibility for
> delivering IETF Meetings to meet community-set requirements including
> managing the meeting costs and service provision. However, the IETF
> LLC is unclear on what the path is to resolve these disagreements.
> This is important because they get to the heart of the requirements
> for the IETF Network and the resulting provision of that network.
> The main area of uncertainty is whether this is a community matter
> that requires a community-led process to determine an outcome such as
> an RFC, or this is for the IETF LLC to lead on and make decisions
> through its normal consultative processes.
> 
> This document aims to initiate a conversation to clarify the way
> forward. To do this, it provides a full primer on the facts needed
> to understand the current situation and the areas of disagreement.
> This includes It sets out the current high-level requirements for the
> IETF Network, an overview of how the IETF Network is delivered, how
> this relates back to the requirements and where the areas of
> disagreement are.

Details of the I-D below.

Jay


> Begin forwarded message:
> 
> From: internet-drafts@ietf.org
> Subject: New Version Notification for draft-daley-meeting-network-requirements-00.txt
> Date: 29 April 2025 at 15:30:09 GMT+12
> To: "Jay Daley" <jay@staff.ietf.org>
> 
> A new version of Internet-Draft
> draft-daley-meeting-network-requirements-00.txt has been successfully
> submitted by Jay Daley and posted to the
> IETF repository.
> 
> Name:     draft-daley-meeting-network-requirements
> Revision: 00
> Title:    IETF Network Requirements
> Date:     2025-04-28
> Group:    Individual Submission
> Pages:    17
> URL:      https://www.ietf.org/archive/id/draft-daley-meeting-network-requirements-00.txt
> Status:   https://datatracker.ietf.org/doc/draft-daley-meeting-network-requirements/
> HTML:     https://www.ietf.org/archive/id/draft-daley-meeting-network-requirements-00.html
> HTMLized: https://datatracker.ietf.org/doc/html/draft-daley-meeting-network-requirements
> 
> 
> Abstract:
> 
>   This document aims to initiate a conversation to clarify the way
>   forward to address disagreements within the community about the
>   requirements for the IETF meeting network, how it is delivered and
>   whether or not the current cost and effort of providing the network
>   is reasonable.
> 
> 
> 
> The IETF Secretariat
> 
> 

-- 
Jay Daley
IETF Executive Director
exec-director@ietf.org