IETF Logo Mail Archive

Re: Fully functional email address

Jay Daley <exec-director@ietf.org> Tue, 17 June 2025 14:11 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 D205035F3CAB for <ietf@mail2.ietf.org>; Tue, 17 Jun 2025 07:11:57 -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 26zo6B20ypa2 for <ietf@mail2.ietf.org>; Tue, 17 Jun 2025 07:11:57 -0700 (PDT)
Received: from mail-il1-x131.google.com (mail-il1-x131.google.com [IPv6:2607:f8b0:4864:20::131]) (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 5CDA535F3CA6 for <ietf@ietf.org>; Tue, 17 Jun 2025 07:11:57 -0700 (PDT)
Received: by mail-il1-x131.google.com with SMTP id e9e14a558f8ab-3de1875bf9dso21380625ab.2 for <ietf@ietf.org>; Tue, 17 Jun 2025 07:11:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=staff-ietf-org.20230601.gappssmtp.com; s=20230601; t=1750169517; x=1750774317; 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=gMw8bis4PsOORjfDyXRxXlBtycJJHu2loM+T4FpyBWw=; b=ve24Qypx9HhEqx+LMO/pzZNCRkWENDDuMuK1CL3UMTPUcgn4S4ajrjWAqlX85+Emv5 DFmvHVbxlvwXgKb5MF2GSzDAT8UA2i1T82s1qmRNmWXBqGOXHCUdoX784x7iFf7ufrD6 7r19SKhshHIKH14lw6x+Tq6eN28LoC+Xm3E0umrc+ozlT7CfyswjMGXVxpGdxhoSIQH2 2H9ggWG4IluuLK7AWaTQi/0rY2aZ/lBKZBDjifq4tne21ZmqVv7PVZULQufbT08Dxut6 rp0Lt6ZdYe16n66tthttT+GUIvV63KayjSrnzxhFatDnvX+gSbvaFKnKIK9QY2bo/IpC qnAQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1750169517; x=1750774317; 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=gMw8bis4PsOORjfDyXRxXlBtycJJHu2loM+T4FpyBWw=; b=mWfLXIcXDEO711Qe6tuJ4cnB/99ftrkhySv3M0eBDDtfti/46ctTYAbs2MW8Eg+b9K arJJNlLUxjQC/ahBhTMDGXBKM3dehRTB5p4CNJEbiT0oyqeFKnhvX+T0DIrLHT+EcbmQ LXog91R3+LMA3+oTHQZiEJqN0AouQPuqAF//ZYy00fx1l3uy+eCeILC66rPVZO6+vbWW J7KNwVcZKEaxgUTYuNKf1UsSZJnMrJyFYvMwXtQ/aYPHsk3g+VdYEpSA4jQv9v2uKWUC O7UIeNerCBUnxosLttxr+71on8SuISPKEgGTmo144OC3vytn4h4rHF4+O7+cSQfk6Q3k HQRQ==
X-Gm-Message-State: AOJu0YyvFkOXI/b9mUDDq7ovcfiUS08YHmrEuMBh4eHsF7EJ4YQ6fTkC MY8UAC83gQYdam3f1HPn+dWQ72cReud1u0W9iIQdql/2tBVnssDQOEDutExXETAKdkLA2A==
X-Gm-Gg: ASbGnctjXgpUIrQLELpHaCxqYGQeAv6HxxfGWZ0hiOwUlgugLtCdhHOSWsYSaSOFYDR ShWTj/O0DPYrjTjyp4KM0rL/bXU6fuPsG0r9teDQvaGSZoOO/sK2xqq0zF887U5r9Y59r0c2xo+ Y3dn/sTj51ASlow1jsoWr4Nr4wuTjtVNgHjhtqP3Wbvf3I763RA8b8lJJWA4TeC60k/hX5gci7+ DqrJnAl8USoogmbgMeEf7/8tlv2TflDaRtTWaN9k/FXx9IovLVqr5XxdCvX4kWEhcadaY8vFBXd hQEEyr5dmY637QJryMYmeEuQRBr60lglTGyWn8hyhi6EUWQCxmad3EsiDzhBaFgNw0St54y6wDW ImWr2Omc=
X-Google-Smtp-Source: AGHT+IFzfcWjX3ABqe7S3zOqdfSo8EibBwHy6gEtzpM0LKHV1E4oFz+/YUfUCtB5PNkQSIdZAcpeOA==
X-Received: by 2002:a05:6e02:1486:b0:3d9:668c:a702 with SMTP id e9e14a558f8ab-3de07c55d0amr139131355ab.9.1750169515557; Tue, 17 Jun 2025 07:11:55 -0700 (PDT)
Received: from smtpclient.apple ([207.35.121.166]) by smtp.gmail.com with ESMTPSA id 8926c6da1cb9f-50149c68bb1sm2250185173.87.2025.06.17.07.11.54 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 17 Jun 2025 07:11:54 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.600.51.1.1\))
Subject: Re: Fully functional email address
From: Jay Daley <exec-director@ietf.org>
In-Reply-To: <6.2.5.6.2.20250616181644.19ba6ab0@elandnews.com>
Date: Tue, 17 Jun 2025 10:11:43 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C69C4FD4-1681-4C74-9CD6-36013758095E@ietf.org>
References: <CAChr6SyjvEBU=O0uiyfzYKNoBCW26KmSp2GriPtxMJEBSfxLbw@mail.gmail.com> <6.2.5.6.2.20250616181644.19ba6ab0@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>, Rob Sayre <sayrer@gmail.com>
X-Mailer: Apple Mail (2.3826.600.51.1.1)
Message-ID-Hash: UNX4RURZR7KVLYLWIUVTUTV225OXPVZR
X-Message-ID-Hash: UNX4RURZR7KVLYLWIUVTUTV225OXPVZR
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@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/zJA8SrLKGz6LcmbdYvfIzApYpUo>
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 22:28, S Moonesamy <sm+ietf@elandsys.com> wrote:
> 
> 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.

There have been a number of self-hosted PDFs submitted as appeals so it is not clear which one is being referred to.  For one of these, where its use as a contribution was challenged, there is no lack of clarity or question of interpretation, as per my official response:

  https://mailarchive.ietf.org/arch/msg/spasm/5C1_WjpQNeHKQf7ia15mxL2mVuk/

Jay

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

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