IETF Logo Mail Archive

Re: Fully functional email address

Rob Sayre <sayrer@gmail.com> Mon, 16 June 2025 22:33 UTC

Return-Path: <sayrer@gmail.com>
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 5915B35AF192 for <ietf@mail2.ietf.org>; Mon, 16 Jun 2025 15:33:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -0.698
X-Spam-Level:
X-Spam-Status: No, score=-0.698 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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=gmail.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 8R0bbr71Ns7E for <ietf@mail2.ietf.org>; Mon, 16 Jun 2025 15:33:36 -0700 (PDT)
Received: from mail-pg1-x534.google.com (mail-pg1-x534.google.com [IPv6:2607:f8b0:4864:20::534]) (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 1526B35AF18B for <ietf@ietf.org>; Mon, 16 Jun 2025 15:33:36 -0700 (PDT)
Received: by mail-pg1-x534.google.com with SMTP id 41be03b00d2f7-b2c2c762a89so4033071a12.0 for <ietf@ietf.org>; Mon, 16 Jun 2025 15:33:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1750113215; x=1750718015; darn=ietf.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=r+LvrwUsvo+/FREgDQ6SE2r3aGfye2YikTDQGVx2bZ4=; b=m2fbxjz9cC46wHyesuyQFarjm3fj38s4+CDWcSAAkPf/G0LChIX/uln0F0f2uwqTaO VKWE9ty0bV1cpHX+16rp/LA12KzqSrL+T/YrcTLh7oZK/GAXtWftX07fZOxa0D087ITy j4WDRvbZlrwK9WHkqW/7/Hm/CBtL2fJKx6b8IagXVvc0oO9+/H3ejMo0niFxEvBgFOPX WyMh9D2lwvb1iZb3MsgsXFiuL6nYfO6P0KgkpC9kcSN5WYAzaHRQOnQumgES5L521wTi /uMjm3o3vcdslgXwf+BK+qRoZankglCb8GmmvtRFoT1B51FgGYKMK/8pfZ34dci+mY3J iUbg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1750113215; x=1750718015; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=r+LvrwUsvo+/FREgDQ6SE2r3aGfye2YikTDQGVx2bZ4=; b=DQgkR0TabHWJViyiUGQIw/uu/IW24HXeeNjJvP7VXwqALRG5yhMaNbJ2qinDBHa2eR RfWjvZJvpTwLHQuXlavAcTqTY9HIc9XlaE9NGQ4CMls4BNSyH6Ke3qGA10m+ZQx8E260 z9tJgpTGdtlW8GU5V4zjDpsQAaxoo2TO8eJWTDWLnW3hJfh6I84oMIuuaLjtKxF/Yan3 WTR1fcZKQkDOmoxITwomODGuonvWt4FZiqzbC4qtU2rAFGXdf/37Ozg+Eb7Hr6CU5oPq TFaHMGJI6PjnyNe6obFVvPsfNp5hkYplD2kYNdim1GTfTg7F1TxaBkvRICr4LVg+glFy TQSw==
X-Gm-Message-State: AOJu0YzGc5UG58vvdlD96TQrmowtomWKKFego9cNf5fVg20NNV9rNrDy QsPRNw6R7QZT5NruHv5ZCERFR08O6U2MGu44g8Ftx+EOYR9acbWHx58RuzBi19H0E+Hw2zVFdka RvSREasfDtbrSeIOZCn0uOvaxPeRG6z++KAkU
X-Gm-Gg: ASbGncuXya2fh6/1STCkyO3awquX3X/vO5RXuOZa6P/Do5BX3UElsC6emmoB2vftMhN 8zHHO9EKIY69Jxq24QQKBEiu4qpJPfmhOMo9hTQPY7rl78IVIx3e9SpswJHy0RSRMxU92vre0mW iuWoQFNIgRc4ciPaZ3iG8X7uxpGkUXt5mzZx2MfBIpu64V
X-Google-Smtp-Source: AGHT+IFhDHPWogecS6ZLVFvvIKgBQkgbmBxAxcqFJC42v9Y4t46GMYH0V6VNkoLdMLjdrkNqZxy/FS7JAI2So6d2ZVo=
X-Received: by 2002:a05:6a00:1911:b0:740:b394:3ebd with SMTP id d2e1a72fcca58-7489ce0d3afmr14285829b3a.7.1750113214787; Mon, 16 Jun 2025 15:33:34 -0700 (PDT)
MIME-Version: 1.0
From: Rob Sayre <sayrer@gmail.com>
Date: Mon, 16 Jun 2025 15:33:23 -0700
X-Gm-Features: AX0GCFuJ7Xf4LkQhKOS4qilo0ksM-WAdUymbGphU9emYKpwLXcwNcBswEeR5vA8
Message-ID: <CAChr6SyjvEBU=O0uiyfzYKNoBCW26KmSp2GriPtxMJEBSfxLbw@mail.gmail.com>
Subject: Re: Fully functional email address
To: IETF discussion list <ietf@ietf.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: multipart/alternative; boundary="0000000000007bf4400637b7fc7d"
Message-ID-Hash: VBRFD6CKWC2BQHMUCVCO3ROBE56W46LK
X-Message-ID-Hash: VBRFD6CKWC2BQHMUCVCO3ROBE56W46LK
X-MailFrom: sayrer@gmail.com
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
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/v8Ddsri1CN5w6lU4Q5P1Zjzy3LA>
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>

Hi,

Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
> In the current case, where such a person is appealing WG/AD actions,
> then I think we should go even further to accommodate them, because
> that is the right thing to do.

We should. But the main problem in this case is not the email address, but
that the complaint was submitted as a self-hosted PDF. It's not clear that
the PDF document is subject to the Note Well. The response invited the
person to make a submission in email where that would be more clear.

We do tolerate those automatically inserted corporate email footers that
contradict the Note Well, because you can't just make up your own rules as
you send an email. In this case, the email could start with "This is a
verbatim copy of <URL>...".

thanks,
Rob

v2.34.0 | Report a Bug | By Email | System Status