Email usage (Was: Fully functional email address)
Jay Daley <exec-director@ietf.org> Tue, 17 June 2025 14:46 UTC
Return-Path: <jay@staff.ietf.org>
X-Original-To: ietf@mail2.ietf.org
Delivered-To: ietf@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id AC2EB35FAE9C for <ietf@mail2.ietf.org>; Tue, 17 Jun 2025 07:46:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable 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 5Ru3Y2C52pAQ for <ietf@mail2.ietf.org>; Tue, 17 Jun 2025 07:46:05 -0700 (PDT)
Received: from mail-il1-x12c.google.com (mail-il1-x12c.google.com [IPv6:2607:f8b0:4864:20::12c]) (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 772D935FAE86 for <ietf@ietf.org>; Tue, 17 Jun 2025 07:46:05 -0700 (PDT)
Received: by mail-il1-x12c.google.com with SMTP id e9e14a558f8ab-3de2869dd74so1124735ab.0 for <ietf@ietf.org>; Tue, 17 Jun 2025 07:46:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=staff-ietf-org.20230601.gappssmtp.com; s=20230601; t=1750171565; x=1750776365; darn=ietf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=BimG5HygXWcHmu0Yh/QT1xdyI59uHfg8LmrFfNnwXyE=; b=u4BtfvaL40voCJSsBikp5IHlMNZvCvPo0Zg3SpR7Df8AW5b9czFOqheGutHqIrWPk5 ky2bMP1yJ/WspRqzylDVMktuqN0AsDF11Dl8DYZIE5SwWmzyLX4rCIGvSZLg6zNpeFU6 98NUTZBwPlwvq9DDpobUhr6ge33+9CAp72NXvlIN8y1mUQr0y6q0T3qzspwN8SgH3Iva jCxtLLK1ULelXLiUCUHeUh/qe4Q4rdN7wugtMT1u1EGw19oX+I+u41FR73Ybb1gNE+Zk QWrD0EKSLiA+SlhNSF1IDQQtcRMhSQu/P1r+SFr2TimybVjzy5sG2g45llidqloM0Y/7 2LGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1750171565; x=1750776365; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=BimG5HygXWcHmu0Yh/QT1xdyI59uHfg8LmrFfNnwXyE=; b=xTcJw0LVyjFJEgfUiVTl/mxTVmHq7em65Li5wwjXgxkWEvx8JV+Ar/1G4gMVHcDF6B xnIyUdH/gKJw0yEB1ZL8mPe6f9GVqYcqzHfg+K/BA9HV64d5CjSyyEIqjoueWBpSQWlc EUTPar7UzOR9g4+PfWjNUZ8mNVHrjYIKrUtkDaKIXYDQsEv2nj6aDB9SnGb0Hty2WzNJ +DKgWUapte3aEK/CXFzFpzu1315ObSEo/l/seh5MW4XFvOYsCKOZRjBtvXTiAPZcCOHs YTDw1BYJUjeCo9TU81sOCe6Ii4hzZ/705TgdSseoFsWdHH84rsRYewJbffnWfB/ir5u/ ucyA==
X-Gm-Message-State: AOJu0Yz/0iGr6z6BYdJ8QWdCEM6hy3WOycuorL/hAGRZYQlw9I4oIgaW 1sIOWZ3LVFWjDqLWn7xYGtcNYGqORs0niTFzZAIOHSwt6YsdX9AA8kSRL7vROfpZUg9YEoMIHbs 3AemNzLobGkrM4ww=
X-Gm-Gg: ASbGnctFh4/RbhylcW0Rn7lVSsj4DMs2kBn3QiHAFpX7MINC1gyprisjK0RCYZiqeVH jiTfNPtkaRXhDm32RHq6RVDJnLLgPLJ7mKYepkNU8GSM/kbC/6/ySz1fJTZjVUMcoba0sISLStb 5CIesnDQBQ+TfUnzVZ5Hf8mh6OjPBnIj5EXTvQO7WYuug/H5ZVpLhgEHe46khtFoTtXv4M5sc4k vjghNABE3KX6w6IghYmvJYAzMUxJBpUwVnExbBZP3Y0MOZlM1bfgJAwgHjchKGEgsSYbgNvMe6N SOoQz+NCCZlmisv4fqOILAQbBmX+/lKn+reP5v9+tPNQSZ0MKcDuNgy6qRbaVmVW2SfW6N9DvJT zodjW5y70Fp5V
X-Google-Smtp-Source: AGHT+IEI/wtEYLUixJ0dRd4XNQbJDeMSTQbA9vQPbEbjxooc+sc/zRLaY212XNfhgZi7ag60FTXtaA==
X-Received: by 2002:a92:ca4a:0:b0:3dd:d365:78bf with SMTP id e9e14a558f8ab-3de07da2f99mr150570865ab.22.1750171564836; Tue, 17 Jun 2025 07:46:04 -0700 (PDT)
Received: from smtpclient.apple ([207.35.121.166]) by smtp.gmail.com with ESMTPSA id 8926c6da1cb9f-50149c6a358sm2252401173.79.2025.06.17.07.46.03 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 17 Jun 2025 07:46:04 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.600.51.1.1\))
Subject: Email usage (Was: Fully functional email address)
From: Jay Daley <exec-director@ietf.org>
In-Reply-To: <MN2PR17MB40315D5E73393FBF18AF3868CD70A@MN2PR17MB4031.namprd17.prod.outlook.com>
Date: Tue, 17 Jun 2025 10:45:53 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <84E6C0C8-23FA-4DCD-8EA3-77090324152C@ietf.org>
References: <18892.1750014795@obiwan.sandelman.ca> <50FFA5F1-6895-4C6C-A4C7-1DA2226CA07B@huitema.net> <9311a7d6-e935-fe48-d897-0011599aa5b0@iecc.com> <MN2PR17MB40315D5E73393FBF18AF3868CD70A@MN2PR17MB4031.namprd17.prod.outlook.com>
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3826.600.51.1.1)
Message-ID-Hash: BQE5PZQSSJRCEDHK5LZGLWKGAXYMVD6M
X-Message-ID-Hash: BQE5PZQSSJRCEDHK5LZGLWKGAXYMVD6M
X-MailFrom: jay@staff.ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: IETF general list <ietf@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3tNNSIOc0BOO64Sm7xQLYmTwoco>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-owner@ietf.org>
List-Post: <mailto:ietf@ietf.org>
List-Subscribe: <mailto:ietf-join@ietf.org>
List-Unsubscribe: <mailto:ietf-leave@ietf.org>
> On 16 Jun 2025, at 12:36, Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org> wrote: > > Regular surveys of the IETF community have shown that while other forms of communication are also desired, “kids these days” don’t have any particular distaste for email. The issue is more about the amount of it, rather than just using it. IIRC Jay talked about it in a plenary and at the WGchairs forum, but I don’t have any good links other than the 2024 community survey. The IETF Community Survey 2024 does indeed talk about this, in a number of places: Q26a. "Do any of the following hinder or deter you from participating in the IETF?" includes "The reliance on email and mailing lists" as one of the statements. Overall this is not a hindrance but those from Africa and those 18-24 years old do regard it as such. To a lesser degree, so do new participants and people from the other regions that have a smaller number of participants. The commentary in the survey is: > 42. The reliance on email and mailing lists is not considered much of a hindrance except for participants under 24 and participants from Africa. This is likely due to those two demographics having a much higher use of phones than laptops and the sub-optimal experience of using email on phones. In the IETF context, this may be worsened by the various email formatting styles of IETF participants (e.g. lines manually wrapped at 78 characters per line) that are difficult to read on mobile devices. Q22. "How do you prefer to be informed of IETF activities?" includes "Email announcements" as an option. This comes out as the preferred option by a long way and with a relatively tight spread by age. Even for younger people, the other options are still a way behind. Q24. "How do you prefer to participate in the discussions and decisions of the IETF?" includes "IETF Mailing lists" as an option. This again comes out as the preferred option by a long way. However, for younger participants and new participants, issue trackers and remote meeting participation are just as popular. Jay -- Jay Daley IETF Executive Director exec-director@ietf.org
- Re: Fully functional email address John C Klensin
- Re: Fully functional email address John C Klensin
- Re: Fully functional email address George Michaelson
- Fully functional email address S Moonesamy
- Re: Fully functional email address Paul Wouters
- Re: Fully functional email address S Moonesamy
- Re: Fully functional email address John Levine
- Re: Fully functional email address Michael Richardson
- Re: Fully functional email address Christian Huitema
- Re: Fully functional email address George Michaelson
- Re: Fully functional email address John C Klensin
- Re: Fully functional email address S Moonesamy
- Re: Fully functional email address John R. Levine
- Re: Fully functional email address Salz, Rich
- Re: Fully functional email address Rob Sayre
- Email usage (Was: Fully functional email address) Jay Daley
- Re: Fully functional email address Stephen Farrell
- Re: Fully functional email address Jay Daley
- Re: Fully functional email address S Moonesamy
- Re: Fully functional email address Martin J. Dürst
- Re: Fully functional email address Christian Huitema
- Re: Fully functional email address S Moonesamy
- Re: Fully functional email address Stephen Farrell
- Re: Fully functional email address John Levine
- Re: Fully functional email address Rich Kulawiec
- Re: Fully functional email address Phillip Hallam-Baker
- Re: Fully functional email address Paul Wouters
- Re: Fully functional email address John C Klensin
- Re: Fully functional email address S Moonesamy