Re: Fully functional email address

S Moonesamy <sm+ietf@elandsys.com> Tue, 17 June 2025 02:42 UTC

Return-Path: <sm@elandsys.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 BF04D35C0AFD for <ietf@mail2.ietf.org>; Mon, 16 Jun 2025 19:42:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: 0.199
X-Spam-Level:
X-Spam-Status: No, score=0.199 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 yWgtJnQSs3nx for <ietf@mail2.ietf.org>; Mon, 16 Jun 2025 19:42:48 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by mail2.ietf.org (Postfix) with ESMTP id BEEFE35C0AFA for <ietf@ietf.org>; Mon, 16 Jun 2025 19:42:47 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.117.105.116]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 55H2gO3s009243 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 16 Jun 2025 19:42:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elandsys.com; s=mail; t=1750128156; x=1750214556; i=@elandsys.com; bh=qyd8TjtzpzniyOHDo1TCIXYhE5I/yblf2nOMa2lch+c=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=2QiVsT10Pr7JG1v9REpUHNM1WadtQs0rK+QW6ErfeC1sMYcw/+h5fdWtesf1CulWf 1s4y2ORN2YQ8H0mlJhYxJ7z+32loAIpIQfhK1/3jTmER7cY9FPleQ1i7fZpfd6hoXy ItsXzntC8+p9Od+E77U4DJc7y4KBI5S3WuSX432k=
Message-Id: <6.2.5.6.2.20250616181644.19ba6ab0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 16 Jun 2025 19:28:03 -0700
To: Rob Sayre <sayrer@gmail.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Fully functional email address
In-Reply-To: <CAChr6SyjvEBU=O0uiyfzYKNoBCW26KmSp2GriPtxMJEBSfxLbw@mail.g mail.com>
References: <CAChr6SyjvEBU=O0uiyfzYKNoBCW26KmSp2GriPtxMJEBSfxLbw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Message-ID-Hash: 3WYB6YGX25ZSNI3SBRVRBCG5JK4OKMZG
X-Message-ID-Hash: 3WYB6YGX25ZSNI3SBRVRBCG5JK4OKMZG
X-MailFrom: sm@elandsys.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/G63xZRWAfqxdFPly9CvF8e1k8Cc>
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 Rob,
At 03:33 PM 16-06-2025, Rob Sayre wrote:
>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.

Whether a self-hosted PDF is a valid complaint depends on how RFC 
5378, Section 1(a) is interpreted.  There is an answer about "fair 
use" in the IETF Trust's frequently asked questions.  It may be a bit 
complicated for some participants; the IETF Trust said that it varies 
from country to country.

>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>...".

Those corporate footers are discussed in the "Note Well" (RFC 5378, 
Section 5.2).

Regards,
S. Moonesamy