IETF Logo Mail Archive

Comments on draft-richardson-in-memorium-00

S Moonesamy <sm+ietf@elandsys.com> Sun, 22 June 2025 18:25 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 A05DA3805945 for <ietf@mail2.ietf.org>; Sun, 22 Jun 2025 11:25:08 -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 qIoBGEcr5exK for <ietf@mail2.ietf.org>; Sun, 22 Jun 2025 11:25:07 -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 095AB3805936 for <ietf@ietf.org>; Sun, 22 Jun 2025 11:25:06 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.117.115.183]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 55MIOXE0014398 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 22 Jun 2025 11:25:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elandsys.com; s=mail; t=1750616705; x=1750703105; i=@elandsys.com; bh=mG3oVz6/Fob+gNaqg/QnVnzgEz50UIr6iRp/HMfpNlY=; h=Date:To:From:Subject; b=ZQiNlIQgEI5REmW4ThfKOllPnX8HwncMQsLO0Xyrshy5kxHuoZVeVzViTVkDBDBBY 9eeUC6L80VmYHbnz3QMsROdaA1jxxgDY4C2PZR1UYhMEbrRhtnaTQPDcZb5/GkeF61 LtqSBzIhdwzBhSdZuA+XwaITVCEWhz5BVgnoM9Y4=
Message-Id: <6.2.5.6.2.20250622110548.09092518@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 22 Jun 2025 11:24:08 -0700
To: Michael Richardson <mcr+ietf@sandelman.ca>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Comments on draft-richardson-in-memorium-00
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Message-ID-Hash: CYPJC5WELY2OKBDXZQZVO3LZY6H2XQ3K
X-Message-ID-Hash: CYPJC5WELY2OKBDXZQZVO3LZY6H2XQ3K
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/7qIH-L_hSj-ZcXU7UdHlfd886Po>
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 Michael,

Thanks for writing draft-richardson-in-memorium-00 [1].

I like what you wrote in Section 3 (privacy considerations).

RFC 6890 states that the IETF occasionally reserves an address block 
for a special purpose in order to support new protocols or 
practices.  I'll leave it to other people to discuss whether the 
requests in Section 5 fit within protocols or practices.

Regards,
S. Moonesamy

1. https://www.ietf.org/archive/id/draft-richardson-in-memorium-00.html

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